Windows 7 My BSOD issue

[ayhan]

I have attached the requested information (zipped) on my issue. Essentially when I try to put my comp. to sleep it enters the BSOD, when i used verifier.exe it went into BSOD as well.

Any help would be much appreciated

Thank you
-A

 

[Trouble]

You have something messing with your network. Apparently
HssDrv.sys 9/2/2010 HotSpot Shield Free VPN for iPhone, Android, Mac and Windows for secure and private browsing, accessing blocked sites and unblocking Facebook and Youtube - Hotspot Shield would recommend completely uninstalling it for testing
Additionally update your Realtek Audio Driver RTKVHD64.sys 7/28/2010 from here Link Removed

BugCheck D1, {10, 2, 0, fffff88001511c83}
Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000][U][B]HssDrv.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B][U][COLOR=#ff0000]HssDrv.sys[/COLOR][/U][/B]
*** ERROR: Module load completed but symbols could not be loaded for [B][U][COLOR=#ff0000]HssDrv.sys[/COLOR][/U][/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=#ff0000][U][B]Probably caused by : HssDrv.sys ( HssDrv+188e )[/B][/U][/COLOR]
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.  [U][B]This is usually
caused by drivers using improper addresses.[/B][/U]
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001511c83, address which referenced memory
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800022fb100
 0000000000000010 
CURRENT_IRQL:  2
FAULTING_IP: 
ndis!NdisReturnPackets+73
fffff880`01511c83 488b7910        mov     rdi,qword ptr [rcx+10h]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff88006feaa00 -- (.trap 0xfffff88006feaa00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000098 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001511c83 rsp=fffff88006feab90 rbp=0000000000000001
 r8=fffffa800194c200  r9=0000000000000000 r10=fffffa800194c020
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!NdisReturnPackets+0x73:
fffff880`01511c83 488b7910        mov     rdi,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800020cb769 to fffff800020cc1c0
STACK_TEXT:  
fffff880`06fea8b8 fffff800`020cb769 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fea8c0 fffff800`020ca3e0 : fffffa80`02d061a0 00000000`00000002 00000000`00000001 fffffa80`0194d6f0 : nt!KiBugCheckDispatch+0x69
fffff880`06feaa00 fffff880`01511c83 : fffffa80`0194c000 fffff880`0145da7d fffffa80`0194c640 fffff880`03c25880 : nt!KiPageFault+0x260
fffff880`06feab90 fffff880`0249b88e : fffffa80`03ebf010 00000000`00000000 fffffa80`0194c640 00000000`00000000 : ndis!NdisReturnPackets+0x73
fffff880`06feabe0 fffffa80`03ebf010 : 00000000`00000000 fffffa80`0194c640 00000000`00000000 fffffa80`0194c6b0 : [COLOR=#ff0000][U][B]HssDrv+0x188e[/B][/U][/COLOR]
fffff880`06feabe8 00000000`00000000 : fffffa80`0194c640 00000000`00000000 fffffa80`0194c6b0 fffff880`0151af1f : 0xfffffa80`03ebf010
STACK_COMMAND:  kb
FOLLOWUP_IP: 
[COLOR=#ff0000][U][B]HssDrv[/B][/U][/COLOR]+188e
fffff880`0249b88e ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME: [COLOR=#ff0000][U][B] HssDrv[/B][/U][/COLOR]+188e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]HssDrv[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]HssDrv.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe308
FAILURE_BUCKET_ID:  X64_0xD1[COLOR=#ff0000][U][B]_HssDrv[/B][/U][/COLOR]+188e
BUCKET_ID:  X64_0xD1_[B][U][COLOR=#ff0000]HssDrv[/COLOR][/U][/B]+188e

and

BugCheck D5, {fffff9800a150d60, 0, fffff880044da7ea, 0}
Unable to load image \SystemRoot\system32\drivers\[COLOR=#ff0000][U][B]RTKVHD64.sys,[/B][/U][/COLOR] Win32 error 0n2
*** WARNING: Unable to verify timestamp for[COLOR=#ff0000][U][B] RTKVHD64.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]RTKVHD64.sys[/B][/U][/COLOR]
Could not read faulting driver name
[U][B]Probably caused by : RTKVHD64.sys ( RTKVHD64+d97ea )[/B][/U]
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9800a150d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880044da7ea, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800022c8100
 fffff9800a150d60 
FAULTING_IP: 
[COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]+d97ea
fffff880`044da7ea 8b4630          mov     eax,dword ptr [rsi+30h]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff880055592a0 -- (.trap 0xfffff880055592a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880055594c8
rdx=fffff88005559430 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044da7ea rsp=fffff88005559430 rbp=0000000000000002
 r8=0000000000000000  r9=fffff880044da7ea r10=0000000000000100
r11=fffff8000220be80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
[COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]+0xd97ea:
fffff880`044da7ea 8b4630          mov     eax,dword ptr [rsi+30h] ds:be80:00000000`00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff8000204154c to fffff800020991c0
STACK_TEXT:  
fffff880`05559138 fffff800`0204154c : 00000000`00000050 fffff980`0a150d60 00000000`00000000 fffff880`055592a0 : nt!KeBugCheckEx
fffff880`05559140 fffff800`020972ee : 00000000`00000000 fffff980`0a150d60 fffffa80`03347500 fffff8a0`01df0126 : nt! ?? ::FNODOBFM::`string'+0x456df
fffff880`055592a0 fffff880`044da7ea : fffff880`055594c8 00000000`00000000 fffff8a0`01df0126 fffffa80`051449e0 : nt!KiPageFault+0x16e
fffff880`05559430 fffff880`055594c8 : 00000000`00000000 fffff8a0`01df0126 fffffa80`051449e0 00000000`00000000 : [COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]+0xd97ea
fffff880`05559438 00000000`00000000 : fffff8a0`01df0126 fffffa80`051449e0 00000000`00000000 fffff800`00000000 : 0xfffff880`055594c8
STACK_COMMAND:  kb
FOLLOWUP_IP: 
[U][B][COLOR=#ff0000]RTKVHD64[/COLOR][/B][/U]+d97ea
fffff880`044da7ea 8b4630          mov     eax,dword ptr [rsi+30h]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  [U][B][COLOR=#ff0000]RTKVHD64[/COLOR][/B][/U]+d97ea
MODULE_NAME: [COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]RTKVHD64.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4c500000
FAILURE_BUCKET_ID:  X64_0xD5_VRF_[COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]+d97ea
BUCKET_ID:  X64_0xD5_VRF_[COLOR=#ff0000][U][B]RTKVHD64[/B][/U][/COLOR]+d97ea

 

[ayhan]

Hi . I did as isntructed, and not getting the BSoD anymore when I put it to sleep . But i still get a BSoD when i try to put it to sleep and boot it later.

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 4105


Additional information about the problem:

BCCode: 9f

BCP1: 0000000000000003

BCP2: FFFFFA8001F12060

BCP3: FFFFF80001EBA518

BCP4: FFFFFA8003163010

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1


Files that help describe the problem:

C:\Windows\Minidump\080312-46254-01.dmp

C:\Users\Ayhan\AppData\Local\Temp\WER-102633-0.sysdata.xml


Read our privacy statement online:


Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:


C:\Windows\system32\en-US\erofflps.txt

 

[ayhan]

Help please.

 

[Trouble]

Update this driver
bcmwl664.sys 6/3/2010 Broadcom 802.11 n NIC (BCM43XX) try here for something a bit more current Link Removed due to 404 Error

 

[ayhan]

I am still getting the same issue. Usually happens when I try to put the comp. to sleep the second or third time or so. I dont know but my ethernet also fails at times and I cannot renable it (just keeps processing). I cant find a new driver for this. I tried updating my BIOS as well and it failed. I attached the latest Dump report.

 

[Trouble]

Looks like an issue with your Atheros Network Adapter.

BugCheck 9F, {3, fffffa8001e8fa10, fffff800033f9518, [B]fffffa8001da1010[/B]}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : pci.sys
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8001e8fa10, Physical Device Object of the stack
Arg3: fffff800033f9518, Functional Device Object of the stack
Arg4: [B]fffffa8001da1010[/B], The blocked IRP
DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f59000 pci
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
STACK_TEXT:  
fffff800`033f94c8 fffff800`020f76c2 : 00000000`0000009f 00000000`00000003 fffffa80`01e8fa10 fffff800`033f9518 : nt!KeBugCheckEx
fffff800`033f94d0 fffff800`02097e3c : fffff800`033f9630 fffff800`033f9630 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`033f9570 fffff800`02097cd6 : fffffa80`01d56c58 fffffa80`01d56c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`033f95e0 fffff800`02097bbe : 00000024`b7cf0ec1 fffff800`033f9c58 00000000`000f6cdb fffff800`02203de8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`033f9c30 fffff800`020979a7 : 00000006`149d48c7 00000006`000f6cdb 00000006`149d48b8 00000000`000000db : nt!KiTimerExpiration+0x1be
fffff800`033f9cd0 fffff800`02084eca : fffff800`021ffe80 fffff800`0220dcc0 00000000`00000000 fffff800`0213bae0 : nt!KiRetireDpcList+0x277
fffff800`033f9d80 00000000`00000000 : fffff800`033fa000 fffff800`033f4000 fffff800`033f9d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
[U][B]FAILURE_BUCKET_ID:  X64_0x9F_3_L1C62x64_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_L1C62x64_IMAGE_pci.sys[/B][/U]

Irp is active with 4 stacks 3 is current (= 0xfffffa8001da1170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8002af6050 00000000 fffff800022d1200-fffffa80036fb0d0 Success Error Cancel pending
          Unable to load image \SystemRoot\system32\DRIVERS\L1C62x64.sys, Win32 error 0n2
*** WARNING: [B]Unable to verify timestamp for L1C62x64.sys[/B]
*** ERROR: [B]Module load completed but symbols could not be loaded for L1C62x64.sys[/B]
 \Driver\L1C    nt!PopSystemIrpCompletion
            Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80036fb0d0    

            Args: 00000000 00000000 00000000 00000000

start             end                 module name
fffff880`02361000 fffff880`02376000   L1C62x64 T (no symbols)           
    Loaded symbol image file: L1C62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1C62x64.sys
    Image name: L1C62x64.sys
    Timestamp:        Mon Sep 27 01:36:23 2010 (4CA03B67)
    CheckSum:         0002220E
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

See if the driver located here makes any difference Link Removed
As for the Broadcom driver you might use Internet Explorer and try the newest one located here Microsoft Update Catalog and see if it helps.

 

[ayhan]

I have updated (via microsoft catalog) my atheros driver, display driver, and broadcom . Still get a BSoD sometimes during sleep or if battery switches off!!!

Attached latest dump report. I think it is the broacom acting up again.

Thanks for all the help btw.

 

[Trouble]

I think it is the broacom acting up again.

You're correct. At least as best I can determine from the information at hand.

[COLOR=#ff0000][U][B]DRIVER_POWER_STATE_FAILURE (9f)[/B][/U][/COLOR]
[B]A driver is causing an inconsistent power state.[/B]
BugCheck 9F, {3, fffffa8001565060, fffff800037d1518,[COLOR=#ff0000][I][B] fffffa80023d3c60[/B][/I][/COLOR]}
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8001565060, Physical Device Object of the stack
Arg3: fffff800037d1518, Functional Device Object of the stack
[I][B]Arg4: [COLOR=#ff0000]fffffa80023d3c60[/COLOR], The blocked IRP[/B][/I]
DRVPOWERSTATE_SUBCODE:  3
IMAGE_NAME:  pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000ed4000 pci
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
STACK_TEXT:  
fffff800`037d14c8 fffff800`021506c2 : 00000000`0000009f 00000000`00000003 fffffa80`01565060 fffff800`037d1518 : nt!KeBugCheckEx
fffff800`037d14d0 fffff800`020f0e3c : fffff800`037d1600 fffff800`037d1600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`037d1570 fffff800`020f0cd6 : fffff800`020476b8 00000000`002e5e8f 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`037d15e0 fffff800`020f0bbe : 0000006e`608448b1 fffff800`037d1c58 00000000`002e5e8f fffff800`0225c468 : nt!KiProcessExpiredTimerList+0xc6
fffff800`037d1c30 fffff800`020f09a7 : 00000012`473d2fc2 00000012`002e5e8f 00000012`473d2fd9 00000000`0000008f : nt!KiTimerExpiration+0x1be
fffff800`037d1cd0 fffff800`020ddeca : fffff800`02258e80 fffff800`02266cc0 00000000`00000000 fffff880`03646588 : nt!KiRetireDpcList+0x277
fffff800`037d1d80 00000000`00000000 : fffff800`037d2000 fffff800`037cc000 fffff800`037d1d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_3_bcmwl664_IMAGE_pci.sys
BUCKET_ID:  X64_0x9F_3_bcmwl664_IMAGE_pci.sys

Irp is active with 5 stacks 3 is current (= 0xfffffa80023d3dc0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    
            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    
            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa8002b11050 00000000 00000000-00000000    
          [I][B]Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000]bcmwl664.sys[/COLOR][/B][/I], Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
 \Driver\BCM43XX
            Args: 00015500 00000000 00000005 00000003
 [ 16, 2]   0 e1 fffffa8002a4ce20 00000000 fffff8000232a200-fffffa80021c0dc0 Success Error Cancel pending
           \Driver\vwifibus    nt!PopSystemIrpCompletion
            Args: 00015500 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80021c0dc0

You should probably take some steps to confirm that this device is actually at issue.
Is it an addon card that you can simply remove, uninstall any associated software and remove or rename the driver bcmwl664.sys to bcmwl664.OLD.
Or is it integrated on the MoBo, if so perhaps disable in the BIOS, or Device Manager and rename the driver. Easily reversible if it proves to perhaps be something else entirely.
Perhaps substitute for testing, another card from another vendor / mainstream manufacturer that is a bit more current with respect to available drivers for Windows 7?
Regards
Randy

EDIT: Can you do anything in Device Manager under the properties of the offending device, under the power management tab regarding it's behavior relative to how it behaves regarding power schemes. Like uncheck allow computer to turn of device to save power?