BSOD On Startup

SteelEye · 11 Jun 2010

Typically when I start my machine from a cold start it takes about 5-10 minutes for the computer to BSOD and restart. Once it restarts I can run for days and not get it to BSOD. I've had a few occasions where it would reboot with a BSOD screen, but that didn't seem to happen very often. It has been happening to me for sometime and I have not been able to figure it out. Hopefully your team can make sense of what I'm missing.... :)

Thanks.

zigzag3143 · 11 Jun 2010

SteelEye said:

Typically when I start my machine from a cold start it takes about 5-10 minutes for the computer to BSOD and restart. Once it restarts I can run for days and not get it to BSOD. I've had a few occasions where it would reboot with a BSOD screen, but that didn't seem to happen very often. It has been happening to me for sometime and I have not been able to figure it out. Hopefully your team can make sense of what I'm missing.... :)

Thanks.

50 Crashes might take a while doing them now.

Ken

**Capt.Jack Sparrow** · 11 Jun 2010

SteelEye said:

Typically when I start my machine from a cold start it takes about 5-10 minutes for the computer to BSOD and restart. Once it restarts I can run for days and not get it to BSOD. I've had a few occasions where it would reboot with a BSOD screen, but that didn't seem to happen very often. It has been happening to me for sometime and I have not been able to figure it out. Hopefully your team can make sense of what I'm missing.... :)

Thanks.

Hello !! Welcome to SF !!

I guess it might your Antivirus / Firewall might be casuing this. It's a wild guess because there was a service excpetion on svchost.exe usually caused by that. So first thing i would recommend to uninstall it protection completely and also use the Cleanup Tool (Check this thread for the links AV Uninstallers)

Hardware Diagostic: Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Post us back the results

Hope this helps,
Captain

Jonathan_King · 11 Jun 2010

I wonder if your Yukon Ethernet Controller drivers are causing the issue. Please uninstall them, and install a fresh copy.

I agree with Captain- a memory test is in order. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 11 18:40:53.148 2010 (GMT-4)
System Uptime: 0 days 0:04:44.272
BugCheck 7F, {8, 80050033, 6f8, fffff88001863e58}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 10 20:35:16.967 2010 (GMT-4)
System Uptime: 0 days 0:06:53.091
BugCheck D1, {5e, 2, 0, fffff88001873157}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  9 20:54:12.811 2010 (GMT-4)
System Uptime: 0 days 0:07:29.935
BugCheck 1E, {ffffffffc0000005, fffff8800170e1cf, 0, ffffffffffffffff}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  8 21:40:13.615 2010 (GMT-4)
System Uptime: 0 days 0:07:15.739
BugCheck 1E, {ffffffffc0000005, fffffa800caa2a4c, 1, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 23:55:44.939 2010 (GMT-4)
System Uptime: 0 days 0:10:15.893
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+247 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 03:17:25.105 2010 (GMT-4)
System Uptime: 0 days 0:04:28.798
BugCheck 1000007E, {ffffffffc0000005, fffff8800185c357, fffff880033697f8, fffff88003369060}
Probably caused by : tcpip.sys ( tcpip!IppDeliverListToProtocol+27 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 21:36:18.181 2010 (GMT-4)
System Uptime: 0 days 0:08:31.305
BugCheck D1, {0, 2, 1, fffff8800171fe6d}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 18:32:24.571 2010 (GMT-4)
System Uptime: 0 days 0:02:20.695
BugCheck D1, {1a, 2, 0, fffff8800185de91}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 21:43:19.221 2010 (GMT-4)
System Uptime: 0 days 0:05:59.345
BugCheck 109, {a3a039d89cdeb508, b3b7465eef5b86fe, fffff8000300ae40, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 21:10:06.969 2010 (GMT-4)
System Uptime: 0 days 0:06:39.982
BugCheck D1, {f, 2, 0, fffff8800184314c}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

SteelEye · 11 Jun 2010

I've run the Memtest that Windows 7 64bit Ultimate has for at least 20 passes while I was asleep one night. It came back clean. So, I couldn't blame ram. (I don't know were the files saves itself to once you boot back into windows or its possible I neglected to save it if there was a chance to)

I had Sophos Anti-Virus installed, but removed that thinking that was causing the issue at one point. Since then I have not reinstalled it. Firewall for windows is disabled.

For the network ports I have done exactly that. I uninstalled the driver and let win7 install a fresh version. I've switched network ports as my board has two network jacks on it. I went to Asus and downloaded the latest drivers for the network ports as a separate test.

I ran the Windows Resource Protection and it did not find any integrity violations.

The only things thats been bugging me about it is if my 850 watt power supply is somehow causing it to do that... but like I said it only does it to me one time usually and is fine after the reboot. Ohh Sometimes the video does not come back up right away or it requires an additional reboot using the power button. I can hear sound when shutting down so I'm not harming my computer in any way.

Programs I do use for clean ups are CCleaner and MalwareBtyes and common sense :P

Jonathan_King · 11 Jun 2010

Please use Memtestx86 to test. The built-in diagnostic is not very accurate!

For the purposes of troubleshooting please remove your anti-virus and replace it with MSE: http://www.microsoft.com/security_essentials

SteelEye · 12 Jun 2010

I ran the Memtest for 5 passes and it stated nothing was wrong. I looked for a report function so I could show it said that, but I could not find anything. It ran pretty much all night since yesterday after my last post.

I downloaded/installed Microsoft Security Essentials and ran the scan on that and it came back clean for the initial run. So I have it currently running a full scan right now.

SteelEye · 12 Jun 2010

Finished running the Full system scan. It came back with nothing. :/

zigzag3143 · 12 Jun 2010

SteelEye said:

Finished running the Full system scan. It came back with nothing. :/

Just a thought but since it is only on cold boot have you tried a chkdsk??

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Jonathan_King · 12 Jun 2010

Try increasing your RAM voltage slightly.