New
#1
bsod windows 7
Windows 7
64
Original OEM version
Purchased in October 2010
No new install
So far the BSOD has occured when opening Firefox and wordpad. I am working from afghanistan, so internet is slow.
Attachment 121510
Windows 7
64
Original OEM version
Purchased in October 2010
No new install
So far the BSOD has occured when opening Firefox and wordpad. I am working from afghanistan, so internet is slow.
Attachment 121510
Hello,
The only third-party driver mentioned was k11.sys, a Kaspersky driver. Please remove Kaspersky, following these directions: Removal tool for Kaspersky Lab products | Kaspersky Lab United States
Replace it with MSE: http://www.microsoft.com/security_essentials
I also recommend a hard drive test, based on the looks of the first dumps. Here is DataLifeguard Tools: WD Support / Downloads / SATA & SAS / WD Caviar Black
...Summary of the dumps:
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 3 09:53:53.826 2010 (UTC - 5:00) System Uptime: 0 days 4:12:21.418 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+22304 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x50_win32k+22304 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Dec 3 00:11:30.824 2010 (UTC - 5:00) System Uptime: 0 days 0:10:49.400 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+22304 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x50_win32k+22304 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 23:58:59.594 2010 (UTC - 5:00) System Uptime: 0 days 0:03:09.155 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+193f1 ) BUGCHECK_STR: 0x19_20 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x19_20_win32k+193f1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 23:54:59.664 2010 (UTC - 5:00) System Uptime: 0 days 0:03:15.240 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+193f1 ) BUGCHECK_STR: 0x19_20 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x19_20_win32k+193f1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 08:27:09.132 2010 (UTC - 5:00) System Uptime: 0 days 0:19:09.319 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+22304 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x50_win32k+22304 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 08:04:28.413 2010 (UTC - 5:00) System Uptime: 0 days 0:04:29.615 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+193f1 ) BUGCHECK_STR: 0x19_20 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x19_20_win32k+193f1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 05:55:08.194 2010 (UTC - 5:00) System Uptime: 0 days 0:01:31.770 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+193f1 ) BUGCHECK_STR: 0x19_20 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x19_20_win32k+193f1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Dec 2 05:50:20.084 2010 (UTC - 5:00) System Uptime: 0 days 0:02:35.676 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : win32k.sys ( win32k+193f1 ) BUGCHECK_STR: 0x19_20 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x19_20_win32k+193f1 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Nov 28 12:39:44.974 2010 (UTC - 5:00) System Uptime: 0 days 0:27:21.551 *** WARNING: Unable to verify timestamp for kl1.sys *** ERROR: Module load completed but symbols could not be loaded for kl1.sys Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 ) BUGCHECK_STR: 0x19_3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
I did both.
Crash still occurs as before. For my physical Drive data LifeGuard says it passed.
Any other thoughts???
The next step is to enable driver verifier: Driver Verifier - Enable and Disable
When Verifier has caused a few BSODs, could you upload a new BSOD report?
https://www.sevenforums.com/crashes-d...tructions.html
I was finally able to run the verifier... but the verifier itself did not cause any BSODs. The only way I was able to get some more BSODs was:
Open Firefox
Open a text document
and I believe there was one random BSOD that occured the other day, not during verifier though
Attachment 123083
As far as network components go, I see some older NIC drivers. Please install the drivers from the links to the right:I don't know what the "Samsung Kernel Driver" is:Code:athrx.sys Mon Dec 14 15:46:53 2009 (4B26A43D) - http://org.downloadcenter.samsung.co..._8.0.0.351.zip yk62x64.sys Mon Sep 28 04:19:31 2009 (4AC07193) - http://extranet.marvell.com/drivers/I suspect it belongs to either the Samsung Display Manager or the Samsung Network Manager.Code:SABI.sys Thu May 28 02:38:02 2009 (4A1E314A)
Could you do a RAM test?
RAM - Test with Memtest86+
Also, try a system files check....Summary of the dumps:JK said:
Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Dec 11 13:30:06.120 2010 (UTC - 5:00) System Uptime: 0 days 1:37:50.680 Probably caused by : win32k.sys ( win32k!sfac_GetLongGlyphIDs+84 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe FAILURE_BUCKET_ID: X64_0x50_win32k!sfac_GetLongGlyphIDs+84 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Memmtest86 seemed to produce no errors. System files scan showed no errors/missing files.
I checked firefox, it still causes the BSOD
I attempted SeaTools to test my drive. The only drive that shows up is
Seriel: WD-WXF1A60F6370
Model: WDC
Is this my main hard drive? How can I tell? It was the only drive that showed up... it did pass the seatools test
That seems like the right drive.
Did you install those updated NIC drivers?
Also, how long was driver verifier running before you determined it didn't cause any BSODs?
Downloading the NIC drivers... I skipped over that portion.
I ran driver verifier for approximately 4 hours