New
#1
BSoD when coming out of sleep
I keep getting BSoD when my computer comes out of sleep. This started after I did some over clocking. It's a x64 win7 OS on a top of the line system.
Thanks in advance!
I keep getting BSoD when my computer comes out of sleep. This started after I did some over clocking. It's a x64 win7 OS on a top of the line system.
Thanks in advance!
Hello,
The dumps point to a hard drive problem; I had to go back to April 24 to get anything in Event Logs that supports this though:It may or may not actually be a hard drive problem. You fit the symptoms of the bug described here quite well: You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard diskCode:Event[2396]: Log Name: System Source: Ntfs Date: 2011-04-25T13:26:48.006 Event ID: 55 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Skynet Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.
Install SP1; that will probably do the trick.
Learn how to install Windows 7 Service Pack 1 (SP1)
Also do what the logs says; open a command prompt and enter:Reboot when done.Code:chkdsk /r
Run SeaTools: SeaTools for Windows | Seagate
If neither CHKDSK nor SeaTools finds anything, and BSODs persist after the SP1 installation, run driver verifier: Driver Verifier - Enable and Disable
...Summary of the dumps:
Code:Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Tue Apr 26 13:31:11.598 2011 (UTC - 4:00) System Uptime: 0 days 14:15:33.158 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e ) BUGCHECK_STR: 0x7a_c0000056 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: TurboV_EVO.exe FAILURE_BUCKET_ID: X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+34c0e SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Mon Apr 25 23:14:32.574 2011 (UTC - 4:00) System Uptime: 0 days 3:51:19.510 Probably caused by : hardware_disk PROCESS_NAME: csrss.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xF4_IOERR_C000000E FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Mon Apr 25 14:06:53.761 2011 (UTC - 4:00) System Uptime: 0 days 12:03:13.698 Probably caused by : csrss.exe PROCESS_NAME: csrss.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xF4_C0000005 FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sun Apr 24 23:56:46.605 2011 (UTC - 4:00) System Uptime: 0 days 4:15:57.166 Probably caused by : hardware_disk PROCESS_NAME: csrss.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xF4_IOERR_C000000E FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sun Apr 24 19:23:38.598 2011 (UTC - 4:00) System Uptime: 0 days 18:36:33.158 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e ) BUGCHECK_STR: 0x7a_c0000056 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+34c0e SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sun Apr 24 00:46:01.598 2011 (UTC - 4:00) System Uptime: 0 days 4:01:08.534 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e ) BUGCHECK_STR: 0x7a_c00000c0 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MOM.exe FAILURE_BUCKET_ID: X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+34c0e SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Apr 23 02:16:24.100 2011 (UTC - 4:00) System Uptime: 0 days 0:03:17.052 Probably caused by : hardware BUGCHECK_STR: 0x124_GenuineIntel DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: linpack_xeon64 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Apr 23 02:02:31.562 2011 (UTC - 4:00) System Uptime: 0 days 0:04:06.483 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: linpack_xeon64 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Apr 23 01:56:51.365 2011 (UTC - 4:00) System Uptime: 0 days 0:03:42.286 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sat Apr 23 01:50:51.631 2011 (UTC - 4:00) System Uptime: 0 days 0:06:10.553 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SetPoint.exe FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Fri Apr 22 19:20:20.504 2011 (UTC - 4:00) System Uptime: 0 days 15:02:55.628 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e ) BUGCHECK_STR: 0x7a_c0000056 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: httpd.exe FAILURE_BUCKET_ID: X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+34c0e SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
I tried running chkdisk and installed sp1, but no luck. What exacly am I supposed to do with the driver verifier?
Could the start of the problem be from all the crashes during overclocking? Maybe the multiple crashes caused something to get corrupted?
Here's the latest dump.
Last edited by zinsco; 27 Apr 2011 at 19:16.
What were the results of chkdsk?
Try installing this hotfix: You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard disk
Remember to test the HD with SeaTools: SeaTools for Windows | Seagate
As for driver verifier, just enable it according to the directions, and then let it go. You can work with it running in the background if you wish.
As far as chkdisk, I didn't see any errors. Just ran through pretty fast. When I rebooted it said briefly said it was clean.
The hotfix didn't work it said, "The update is not applicable to your computer."
I did run the SeaTools and it said, "Passed."
Help and Support
Did you tick the second box?
I'm thinking this Hotfix is in the SP1 package.
I found the problem. I've been trying to think what I might have done besides overclocking that might be an issue. How about updating my intel rst drivers? lol.....bingo! I updated to 10.5.0.1015 from 10.1.2.1004. Went back to the 1004 and now it comes out of sleep just fine. I than found out that intel has another update to 1022 so I tried that and it crashes coming out of sleep, also. Went back to the 1004 again and all is right with the world. I think it has to do with my ssd's and maybe more so since they are in raid 0.
Thank you so much for your help. Hopefully this will help someone else with similar problems.