Hello all, I've just gotten this new computer and this is the only problem with it. Occasionally, it will BSOD after returning from sleep. I've looked at the hotfix, but that was for a large, 1TB or larger HD. Mine is 750GB. I will also post the minidump.
Welcome!
Try updating your hard disk controller and chipset drivers. You may also try updating your USB drivers.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_041410-18486-01.zip\041410-18486-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500? Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50 Debug session time: Thu Apr 15 00:11:23.815 2010 (GMT-4) System Uptime: 0 days 19:53:24.939 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list .................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8008207590, fffff80000b9c518, fffffa8008376a00} Probably caused by : usbccgp.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffffa8008207590, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa8008376a00, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8008376a00 DEVICE_OBJECT: fffffa8008207590 DRIVER_OBJECT: fffffa8007d649e0 IMAGE_NAME: usbccgp.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15 MODULE_NAME: usbccgp FAULTING_MODULE: fffff88002a9e000 usbccgp CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b41e23 to fffff80002ad2f00 STACK_TEXT: fffff800`00b9c4c8 fffff800`02b41e23 : 00000000`0000009f 00000000`00000003 fffffa80`08207590 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02adefa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`02ade326 : fffff800`02c81700 00000000`004609ce 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02adee7e : 000000a6`b7deaeb6 fffff800`00b9cc58 00000000`004609ce fffff800`02c4fc48 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02ade697 : 0000002d`b0887cc1 0000002d`004609ce 0000002d`b0887ce7 00000000`000000ce : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02adb6fa : fffff800`02c4be80 fffff800`02c59c40 00000000`00000000 fffff880`0fe9fea0 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_usbccgp.sys BUCKET_ID: X64_0x9F_IMAGE_usbccgp.sys Followup: MachineOwner ---------
usbccgp.sys is a Windows file - as such it's not likely to be the actual cause of the problem.
What USB devices do you have connected to the computer?
What's the exact make and model of the computer so we can figure out if there's any built-in USB stuff?
Please run Driver Verifier according to these directions. It may help to reveal the problem device/driver:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Where is exactly is the memory dump for driver verifier? I also have another question, I can't seem to find where I can update my hard disk controllers. My HD is a Seagate.
The dmps for Driver Verifier will be in the normal place, C:\Windows\Minidump.
To update your hard disk controller, visit the computer manufacturer's site (e.g. Dell, Acer, etc), and check in the downloads section.
Here is the verifier results. I couldn't get the BSOD this time, it really happens occasionally, but enough to make me annoyed.
This is pretty straight forward. the dirctx portion of your video driver (dxgkrnl.sys). I would download the removal tool from them and remove all the remnants of the current driver. I would then just install the driver and not the rest of the junk.
Good Luck and Let us know if you need help
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\041510-23088-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50 Debug session time: Thu Apr 15 09:46:37.142 2010 (GMT-4) System Uptime: 0 days 0:00:10.282 Loading Kernel Symbols ............................................................... ...................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 0, fffff80002a94183} Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : dxgkrnl.sys ( dxgkrnl+892a0 ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002a94183, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cac0e0 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+ae3 fffff800`02a94183 488b09 mov rcx,qword ptr [rcx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: ffffffffffffff89 TRAP_FRAME: fffff8800335a5f0 -- (.trap 0xfffff8800335a5f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800335af80 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a94183 rsp=fffff8800335a780 rbp=fffff8800335a8d0 r8=fffff8800335a888 r9=fffff8800335a880 r10=0000000000000002 r11=fffff80002a936a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!IopCompleteRequest+0xae3: fffff800`02a94183 488b09 mov rcx,qword ptr [rcx] ds:a830:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a73b69 to fffff80002a74600 STACK_TEXT: fffff880`0335a4a8 fffff800`02a73b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0335a4b0 fffff800`02a727e0 : 00000000`00000000 fffff980`02624ee0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0335a5f0 fffff800`02a94183 : 00000000`00000007 fffff8a0`00000001 fffff880`0335b6a0 fffff880`00000000 : nt!KiPageFault+0x260 fffff880`0335a780 fffff800`02a50fcf : 00000000`00000001 fffff880`0335a9d0 000018ad`00001800 fffff800`00000000 : nt!IopCompleteRequest+0xae3 fffff880`0335a850 fffff800`02a51387 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`0335a8d0 fffff800`02a14ac9 : 00000000`00000000 00000000`00000000 fffffa80`06057498 00000000`00000000 : nt!KiApcInterrupt+0xd7 fffff880`0335aa60 fffff800`02a1493f : fffffa80`06057498 fffff880`00000011 fffff980`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x169 fffff880`0335b100 fffff800`02b37b6b : 00000000`00000003 fffffa80`06057498 00000000`00000000 fffff800`00000000 : nt!RtlWalkFrameChain+0x73 fffff880`0335b130 fffff800`02f0b02c : fffffa80`06057480 00000000`00000118 00000000`00000080 fffff800`02efedcc : nt!RtlCaptureStackBackTrace+0x4b fffff880`0335b160 fffff800`02f0d33a : fffff880`03356000 fffff880`0335c000 00000000`00000080 00000000`00000118 : nt!ViPoolLogStackCallout+0x1c fffff880`0335b190 fffff800`02f10026 : 00000000`00000000 00000000`00000028 fffff800`02ce1e5f fffff800`02d8b3b4 : nt!ViPoolLogStackTrace+0x8a fffff880`0335b1c0 fffff800`02f10160 : fffffa80`07161060 fffff800`02ce1e5f 00000000`2b707249 fffffa80`056c3898 : nt!VeAllocatePoolWithTagPriority+0x2b6 fffff880`0335b230 fffff800`02f193a8 : 00000000`00000001 fffff800`02f0b02c fffffa80`056c3880 fffff800`02ce1e5f : nt!ViIrpAllocate+0x40 fffff880`0335b270 fffff800`02f194c3 : fffffa80`07161060 fffff800`02ce1e5f fffffa80`056c3898 fffff8a0`0049fe20 : nt!ViIrpAllocateLockedPacket+0x28 fffff880`0335b2b0 fffff800`02f19a92 : fffffa80`07161060 fffffa80`056c3898 fffff8a0`0049fe20 00000000`00000030 : nt!VfIoAllocateIrp1+0x23 fffff880`0335b2e0 fffff800`02a698d6 : fffffa80`07161060 fffff880`042338c0 00000000`00000030 00000000`00000082 : nt!IovAllocateIrp+0x52 fffff880`0335b330 fffff800`02ce1e5f : fffffa80`07161060 fffff880`0335b4a8 00000000`00000030 fffffa80`0811b5d0 : nt!IoBuildAsynchronousFsdRequest+0x36 fffff880`0335b380 fffff880`042a52a0 : ffffffff`c0000034 fffff880`0429c2ba fffffa80`0811b5d0 ffffffff`c0000034 : nt!IoBuildSynchronousFsdRequest+0x1f fffff880`0335b3c0 ffffffff`c0000034 : fffff880`0429c2ba fffffa80`0811b5d0 ffffffff`c0000034 00000000`00000000 : dxgkrnl+0x892a0 fffff880`0335b3c8 fffff880`0429c2ba : fffffa80`0811b5d0 ffffffff`c0000034 00000000`00000000 fffff880`0335b418 : 0xffffffff`c0000034 fffff880`0335b3d0 fffffa80`0811b5d0 : ffffffff`c0000034 00000000`00000000 fffff880`0335b418 fffff880`0335b408 : dxgkrnl+0x802ba fffff880`0335b3d8 ffffffff`c0000034 : 00000000`00000000 fffff880`0335b418 fffff880`0335b408 fffff880`0335b458 : 0xfffffa80`0811b5d0 fffff880`0335b3e0 00000000`00000000 : fffff880`0335b418 fffff880`0335b408 fffff880`0335b458 ffffffff`80000110 : 0xffffffff`c0000034 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl+892a0 fffff880`042a52a0 ?? ??? SYMBOL_STACK_INDEX: 12 SYMBOL_NAME: dxgkrnl+892a0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e FAILURE_BUCKET_ID: X64_0xA_VRF_dxgkrnl+892a0 BUCKET_ID: X64_0xA_VRF_dxgkrnl+892a0 Followup: MachineOwner ---------
I'll do just that. I'll update this is the problem occurs again. Thank you all for your help.
Hello all,
I recently created a thread about my BDOS after sleep. Getting rid of Directx and reinstalling the latest graphics driver seemed to work, but only for 3 days. Now, it's back.
Quote