Hey all I'm running Vista 32-bit (which I hate) on an ASUS m50SV-A1 and just recently this started happening. Whenever I connect to my internet connection, via router wired OR wireless I will get a Blue Screen after a minute or two. This does NOT happen when connected to any other network, only this one.
The screen will read:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
It will then dump physical cache and require a restart.
I have also noticed that asghost.exe seems to be using up a lot of the CPU I'm not sure if this has anything to do with it.
It's becoming very frustrating and if anyone knows what I should do, it would be greatly appreciated.
Thanks.
Greg
-
Any chance you can upload the minidump file, this can help locate the cause.
C:Windows>Minidump>*******.dmp
If it gives you permission problems, copy the file to another location then upload it. -
Had to attach it as a .zip file since it wouldn't allow me to upload a .dmp file, but there it is.
Attached Files:
-
-
Probable cause: HssDrv.sys. Can't find to much information about this driver apart from it belongs to Hotspot Shield. Have you got this prgram.
Also, this driver came up, but was not a cause: yk60x86.sys. This relates to a Marvell Yukon Ethernet Controller.
First, if you have Hotspot shied, disable this and see if you get the BSOD. Then see if there is an update for your ethernet driver.
When I looked for information about HssDrv.sys, there was not a lot of information at all.
Edit: Debug Results
Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Users\Sam\Documents\Mini020109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8203e000 PsLoadedModuleList = 0x82155c70
Debug session time: Mon Feb 2 00:01:14.316 2009 (GMT+0)
System Uptime: 0 days 1:33:01.405
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4, 2, 1, 8e717dd9}
Unable to load image \SystemRoot\system32\DRIVERS\HssDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HssDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for HssDrv.sys
Unable to load image \SystemRoot\system32\DRIVERS\yk60x86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for yk60x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x86.sys
Probably caused by : HssDrv.sys ( HssDrv+3dd9 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8e717dd9, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82175868
Unable to read MiSystemVaType memory at 82155420
00000004
CURRENT_IRQL: 2
FAULTING_IP:
HssDrv+3dd9
8e717dd9 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: NeroVision.exe
TRAP_FRAME: 8039db0c -- (.trap 0xffffffff8039db0c)
ErrCode = 00000002
eax=00000008 ebx=00000000 ecx=8e720102 edx=00000000 esi=8e7201c0 edi=87331f98
eip=8e717dd9 esp=8039db80 ebp=8039dba4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
HssDrv+0x3dd9:
8e717dd9 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 8e717dd9 to 82098d24
STACK_TEXT:
8039db0c 8e717dd9 badb0d00 00000000 8735b028 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
8039db7c 87331f98 8e7201c0 876a9008 00000001 HssDrv+0x3dd9
8039dba4 8e717930 000001eb 87331f98 000001eb 0x87331f98
8039dbcc 8a771533 876a9008 863af208 c000009a HssDrv+0x3930
8039dc28 8a74b7fa 005e78a8 8039dc48 00000001 ndis!ethFilterDprIndicateReceivePacket+0x2bf
8039dcf8 8a73e858 0239dd10 876ec568 875e7750 ndis!ndisIndicateXlatedPacketsToNdis5Protocols+0xd1
8039de74 8a67f57f 874630e8 876a94c0 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0xf1
8039de90 8a73eaba 874630e8 875e7750 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2c
8039deac 8a67f54a 874630e8 875e7750 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x27
8039dec8 8e677dac 874630e8 875e7750 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x20
8039def0 8e66d70a 876ec000 876ec570 875e7750 yk60x86+0x11dac
8039df28 8e66eac7 606ec000 00000000 875ed5e8 yk60x86+0x770a
8039df40 8a73e11c 876ec000 00000000 00000000 yk60x86+0x8ac7
8039df64 8a67f468 875ed5fc 8e674590 00000000 ndis!ndisMiniportDpc+0x81
8039df88 820f4450 875ed5fc 874630e8 00000000 ndis!ndisInterruptDpc+0xc4
8039dff4 820f2935 aa134d10 00000000 00000000 nt!KiRetireDpcList+0x147
8039dff8 aa134d10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
820f2935 00000000 0000001b 00c7850f bb830000 0xaa134d10
STACK_COMMAND: kb
FOLLOWUP_IP:
HssDrv+3dd9
8e717dd9 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: HssDrv+3dd9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HssDrv
IMAGE_NAME: HssDrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497f5d0c
FAILURE_BUCKET_ID: 0xD1_HssDrv+3dd9
BUCKET_ID: 0xD1_HssDrv+3dd9
Followup: MachineOwner
--------- -
I generally have Hotspot Shield disabled, so I'll just try a full uninstall of it since it isn't really necessary.
Thanks for the tips though, I'll check for an ethernet driver update as well. Burning a DVD atm so once that's done I'll try all of these and post back.
Thanks, once again. -
Uninstalled Hotspot Shield and connected to network, usually would've BSOD'd by now so I'm going to consider it a success until any further problems.
-
Hopefully that was the issue. If there are any more issues, you know where to come
BSOD when connecting to network!
Discussion in 'Networking and Wireless' started by ablm, Feb 1, 2009.