Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD while away from PC

23 Mar 2012   #1

Windows 7 Ultimate x64
 
 
Random BSOD while away from PC

Code:
Is Windows 7 . . . 
- x64 
- Original OS - full retail version    
- What is the age of system (hardware)? < 8 months on the oldest piece 
- What is the age of OS installation ~ 1 month
System specs are in.... my system specs.
Basically 3 times now that I've came home or came to my computer after being asleep and I see that it had experienced a BSOD. Don't know what caused it and am just looking for a little help.

I'm running an SSD boot drive and the computer doesn't sleep/hibernate, it just turns off the monitor after 10-15 minutes.

My System SpecsSystem Spec
.

23 Mar 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Not Available	USB\VID_0CF3&PID_3000\6&DF2EE03&0&7	The drivers for this device are not installed.

System Security: ??? Recommend one of these:

Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\Shook\Windows_NT6_BSOD_jcgriff2\032312-22479-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`03097e70 Debug session time: Fri Mar 23 05:56:46.795 2012 (UTC - 6:00) System Uptime: 3 days 1:42:53.700 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffffffffffff5, 1, fffff80002eed0be, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+118 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffffffffffff5, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80002eed0be, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031020e0 fffffffffffffff5 FAULTING_IP: nt!RtlFindClearBits+ce fffff800`02eed0be 4983f8ff cmp r8,0FFFFFFFFFFFFFFFFh MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880087facd0 -- (.trap 0xfffff880087facd0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000201 rdx=fffff70000000048 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002eed0be rsp=fffff880087fae60 rbp=0000000000008000 r8=fffffffffffffff5 r9=fffff70000000ff8 r10=0000000000007fff r11=0000000000007fff r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!RtlFindClearBits+0xce: fffff800`02eed0be 4983f8ff cmp r8,0FFFFFFFFFFFFFFFFh Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002f4adf4 to fffff80002eca5c0 STACK_TEXT: fffff880`087fab68 fffff800`02f4adf4 : 00000000`00000050 ffffffff`fffffff5 00000000`00000001 fffff880`087facd0 : nt!KeBugCheckEx fffff880`087fab70 fffff800`02ec86ae : 00000000`00000001 00000000`00000001 fffff900`c4672000 00000000`01b00016 : nt! ?? ::FNODOBFM::`string'+0x426f7 fffff880`087facd0 fffff800`02eed0be : fffffa80`0f8007d0 00000000`00001000 fffff880`087faf68 fffff700`01080034 : nt!KiPageFault+0x16e fffff880`087fae60 fffff800`031dc507 : fffff900`c31398f8 fffff900`00000000 fffff880`00000040 00000000`00000001 : nt!RtlFindClearBits+0xce fffff880`087faea0 fffff800`031c9534 : ffffffff`ffffffff ffffffff`ffffffff fffff880`087fb1b0 00000000`00003000 : nt!MiFindEmptyAddressRange+0xe7 fffff880`087faf10 fffff800`02ec9813 : ffffffff`ffffffff fffff880`087fb360 00000000`00000001 fffff880`087fb350 : nt!NtAllocateVirtualMemory+0x724 fffff880`087fb0c0 fffff800`02ec5db0 : fffff960`00155b70 fffffa80`0f484060 fffff880`087fb4a0 00000000`02a87e98 : nt!KiSystemServiceCopyEnd+0x13 fffff880`087fb2c8 fffff960`00155b70 : fffffa80`0f484060 fffff880`087fb4a0 00000000`02a87e98 00000000`00000000 : nt!KiServiceLinkage fffff880`087fb2d0 fffff800`02ec9813 : 00000000`54010f06 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x118 fffff880`087fb3b0 000007fe`fd453e9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02a87e78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd453e9a STACK_COMMAND: kb FOLLOWUP_IP: win32k!NtGdiCreateDIBSection+118 fffff960`00155b70 898424f8000000 mov dword ptr [rsp+0F8h],eax SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: win32k!NtGdiCreateDIBSection+118 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f10fe35 FAILURE_BUCKET_ID: X64_0x50_win32k!NtGdiCreateDIBSection+118 BUCKET_ID: X64_0x50_win32k!NtGdiCreateDIBSection+118 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\Shook\Windows_NT6_BSOD_jcgriff2\032012-14554-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce70 Debug session time: Tue Mar 20 04:12:29.462 2012 (UTC - 6:00) System Uptime: 0 days 0:01:25.368 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff96000237fe8, fffff88009c245f0, 0} Probably caused by : hardware ( win32k!DEVLOCKBLTOBJ::bLock+1b4 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c000001d, Exception code that caused the bugcheck Arg2: fffff96000237fe8, Address of the instruction which caused the bugcheck Arg3: fffff88009c245f0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: win32k!DEVLOCKBLTOBJ::bLock+1b4 fffff960`00237fe8 000f add byte ptr [rdi],cl CONTEXT: fffff88009c245f0 -- (.cxr 0xfffff88009c245f0) rax=00000000244c8ffd rbx=fffff88009c25140 rcx=fffff900c00b9010 rdx=0000000000000010 rsi=0000000000000001 rdi=0000000000000001 rip=fffff96000237fe8 rsp=fffff88009c24fc0 rbp=0000000000000001 r8=fffff900c227a010 r9=fffff900c39e3630 r10=fffff900c39e3780 r11=fffff88009c24cf0 r12=fffff88009c250f0 r13=fffff88009c250d8 r14=fffff88009c25190 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 win32k!DEVLOCKBLTOBJ::bLock+0x1b4: fffff960`00237fe8 000f add byte ptr [rdi],cl ds:002b:00000000`00000001=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: TVersity.exe CURRENT_IRQL: 0 MISALIGNED_IP: win32k!DEVLOCKBLTOBJ::bLock+1b4 fffff960`00237fe8 000f add byte ptr [rdi],cl LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff96000237fe8 STACK_TEXT: fffff880`09c24fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DEVLOCKBLTOBJ::bLock+0x1b4 FOLLOWUP_IP: win32k!DEVLOCKBLTOBJ::bLock+1b4 fffff960`00237fe8 000f add byte ptr [rdi],cl SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!DEVLOCKBLTOBJ::bLock+1b4 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff88009c245f0 ; kb MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\Shook\Windows_NT6_BSOD_jcgriff2\032012-23540-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe70 Debug session time: Tue Mar 20 04:09:13.015 2012 (UTC - 6:00) System Uptime: 7 days 10:07:24.779 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ............................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff88002fd5180, 3} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002fd5180, The PRCB address of the hung processor. Arg4: 0000000000000003, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: sidebar.exe CURRENT_IRQL: d STACK_TEXT: fffff880`087672b8 fffff800`02e80463 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx fffff880`087672c0 fffff800`02edac87 : 00000000`00000000 fffff800`00000003 00000000`000030d4 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e fffff880`08767350 fffff800`02e23895 : fffff800`02e48460 fffff880`08767500 fffff800`02e48460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`08767450 fffff800`02eceab3 : 00000000`6bff1c99 fffff800`0304ce80 fffff800`0304ce80 fffff680`000f75f8 : hal!HalpHpetClockInterrupt+0x8d fffff880`08767480 fffff800`02f03619 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`08767610 fffff800`02f13fba : 00000000`00000000 00000000`1eebffff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x7d0 fffff880`087677d0 fffff800`02ed1813 : ffffffff`ffffffff fffff880`08767a90 fffff880`08767a98 fffff880`00008000 : nt!NtFreeVirtualMemory+0x5ca fffff880`087678c0 fffff800`02ecddb0 : fffff800`0315ef7f fffffa80`0f25b060 fffffa80`126631b0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 fffff880`08767a58 fffff800`0315ef7f : fffffa80`0f25b060 fffffa80`126631b0 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage fffff880`08767a60 fffff800`031b490a : 00000000`1ee40000 00000000`00000000 00000000`00000000 fffffa80`0eab4c90 : nt!RtlFreeUserStack+0x27 fffff880`08767a90 fffff800`031b83ed : 00000000`00000000 fffff800`031e5400 000007ff`fffd4000 00000000`00000000 : nt!PspExitThread+0x7ae fffff880`08767b50 fffff800`031b8635 : fffffa80`126631b0 00000000`00000000 fffffa80`126631b0 00000000`03ce4300 : nt!PspTerminateThreadByPointer+0x4d fffff880`08767ba0 fffff800`02ed1813 : fffffa80`126631b0 fffff880`08767c60 00000000`773c5270 fffffa80`0ea56f10 : nt!NtTerminateThread+0x45 fffff880`08767be0 00000000`7730fbea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`1eebf668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7730fbea STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
All point to a hardware fault. I am wondering if it is related to your SSD.
  • Is your SSD firmware up to date?

  • Is your BIOS up to date?

  • Are your hard disk controller drivers and chipset drivers up to date?


I would also recommend reading through STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg


Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
My System SpecsSystem Spec
23 Mar 2012   #3

Windows 7 Ultimate x64
 
 

All point to a hardware fault. I am wondering if it is related to your SSD.
  • Is your SSD firmware up to date?-- Yes
  • Is your BIOS up to date? -- No. Updating after i finish this post....
  • Are your hard disk controller drivers and chipset drivers up to date? -- Yes


Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs. -- Done


I guess I'll just update the BIOS and let it go a couple days. See what happens. Thanks writhziden for taking your time to help.
My System SpecsSystem Spec
.


23 Mar 2012   #4

Windows 7 Home Premium 64 Bit
 
 

You're welcome. Best wishes the BIOS update does the trick.
My System SpecsSystem Spec
Reply

 Random BSOD while away from PC




Thread Tools



Similar help and support threads for2: Random BSOD while away from PC
Thread Forum
BSOD doing random things (Google Chrome, minecraft, random times) BSOD Help and Support
Solved Random freeze, random BSOD, no signal to screen BSOD Help and Support
BSOD at random times doing random things BSOD Help and Support
Random BSOD during Random times, error 0x8000000000000002 BSOD Help and Support
Random BSOD errors happening at random times BSOD Help and Support
Random BSOD's with random error messages after a new setup BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:45 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33