Windows 7: Random BSOD on startup (even safe mode)

takitoes · 06 Mar 2010

Hey guys,

I'll start at the beginning.

I recently switched out my graphics card and replaced it with a 2nd hand 275GTX. I should note, i (and the previous owner) have used the card without issues for a fairly long period of time. It was only problems with my monitor loosing signal while playing Modern Warfare 2 and (i think) driver crashes that caused me to look deeper, and has led to a range of problems. I'm not sure if they were there before, but they have only recently come to surface.

The machine then started to do weird things in games, which I traced back to drivers with the Event Log. So I finally got around to formatting my PC and starting fresh with drivers and new hardware.

Since then i have been having random BSOD errors on startup. Sometimes i boot and run fine, sometimes i cant get past the Windows loading screen with crashing and other times it will load windows then crash after 5-10secs.

Instantly i thought that it was a GPU problem, so i switched it out with a spare 6600GT i have, and the same thing continues to happen. Sometimes the PC will BSOD before or just after windows startup and other-times i can boot up fine and never notice anything was wrong.

If the machine does crash with a BSOD it will continually loop. Crashing, then restart then load up and BSOD again ect ect. If i turn the whole PC off at the PSU then it has its normal "chance" of loading normally. Trying to boot into Safe mode doesn't seem to help, it simply changes the BSOD error.

If i try to boot normally into windows i get one of two BSOD messages:

If i try to boot into safe mode i usually get this message:

Sometimes randomly i get the message on startup, briefly before it crashes:

I am not 100% that those errors only occur in those circumstances, but that seems to be what i have noticed.

I have tried the following fixes:

- All current windows updates
- Boot into Memtest86+ and run overnight = no errors recorded
- Stress tested CPU with Linpack and Prime95
- Removed all overclocks and reset BIOS
- Updated to latest BIOS version
- Stress tested GPU with Furmark, nothing wrong after over 12 hours
- Running the GPU with the previous 5 driver versions and the current Beta
- Running the GPU with default Windows 7 Drivers

The only thought i have had, could it possibley be a problem with the GPU seating? i have tested it, but at the moment the Motherboard is lying flat and the GPU is not attached to anything.

Im seriously stumped

Any help is really appreciated!

Thankyou

usasma · 06 Mar 2010

18 memory dumps from 02 Mar 10 to 06 Mar 10
1 STOP 0xA - More info about this error here: BSOD Index
2 STOP 0x19 - More info about this error here: BSOD Index
4 STOP 0x1E - More info about this error here: BSOD Index
8 STOP 0x3B - More info about this error here: BSOD Index
3 STOP 0x7E - More info about this error here: BSOD Index
6 of them blame ntkrnlmp.exe; 2 blame Pool_Corruption; 4 blame memory_corruption; 1 blames NETIO.SYS; 3 blame ndis.sys; 1 blames ctaud2k.sys; 1 blames AgileVpn.sys

It's most likely this is a hardware issue. Since you've run MemTest and Furmark, that would seem to rule out the memory and the video card. As such, I'd try this free diagnostic: HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, try this free stress test:

Quote:

Link: Free Software - GIMPS

Quote:

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar  1 18:25:43.805 2010 (GMT-5)
System Uptime: 0 days 0:00:26.852
BugCheck 1E, {ffffffffc0000005, fffff88003360030, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar  1 18:27:47.743 2010 (GMT-5)
System Uptime: 0 days 0:00:17.774
BugCheck 3B, {c0000005, fffff80002c90b0c, fffff88009917f30, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoAcquireRemoveLockEx+24 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  RazerTray.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 07:59:49.937 2010 (GMT-5)
System Uptime: 0 days 0:00:10.968
BugCheck 19, {3, fffffa80054664a0, fffffa80054664a0, fdfffa80054664a0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:40:22.711 2010 (GMT-5)
System Uptime: 0 days 0:00:20.743
BugCheck 3B, {c0000005, fffff80002fa6fb9, fffff88008ec7df0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+51 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CTxfispi.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:46:59.071 2010 (GMT-5)
System Uptime: 0 days 0:00:17.102
BugCheck 1E, {ffffffffc0000005, fffff88008de3080, 0, 0}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : NETIO.SYS ( NETIO!NetioInitializeNetBufferListContext+4a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:41:39.680 2010 (GMT-5)
System Uptime: 0 days 0:00:16.711
BugCheck 3B, {c0000005, fffff80002c72063, fffff880068520a0, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpFindGuidEntryByGuid+73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:42:31.118 2010 (GMT-5)
System Uptime: 0 days 0:00:18.149
BugCheck A, {28, 2, 0, fffff80002ccc090}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnetwk.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:45:50.718 2010 (GMT-5)
System Uptime: 0 days 0:00:11.750
BugCheck 1000007E, {ffffffffc0000005, fffff88001494358, fffff8800337dfe8, fffff8800337d840}
Probably caused by : ndis.sys ( ndis!ndisSetupWmiNode+8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 23:50:26.744 2010 (GMT-5)
System Uptime: 0 days 0:00:27.900
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1E, {ffffffffc0000005, fffff8800313bcf0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 07:07:01.727 2010 (GMT-5)
System Uptime: 0 days 0:00:34.758
BugCheck 1E, {ffffffffc0000005, fffff80002ca7c62, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerFileObjectContext+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmplayer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:14:51.580 2010 (GMT-5)
System Uptime: 0 days 0:00:24.611
BugCheck 3B, {c0000005, fffff880016c2b8e, fffff880077aa840, 0}
Probably caused by : ndis.sys ( ndis!ndisNsiGetInterfaceRodEnumObject+22e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:20:44.906 2010 (GMT-5)
System Uptime: 0 days 0:00:09.937
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
BugCheck 1000007E, {ffffffffc0000005, fffff8800441e3f8, fffff88003377588, fffff88003376de0}
Probably caused by : ctaud2k.sys ( ctaud2k+3f8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:13:51.378 2010 (GMT-5)
System Uptime: 0 days 0:00:36.410
BugCheck 3B, {c0000005, fffff80002fc1163, fffff8800a7b9f40, 0}
Probably caused by : memory_corruption ( nt!MmCreateSection+3b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:12:40.322 2010 (GMT-5)
System Uptime: 0 days 0:00:30.353
BugCheck 3B, {c0000005, fffff80002cb946d, fffff88007ccc440, 0}
Probably caused by : memory_corruption ( nt!MiPromoteNode+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:18:49.000 2010 (GMT-5)
System Uptime: 0 days 0:00:06.156
BugCheck 19, {3, fffffa8005c684a0, fffffa8005c684a0, fdfffa8005c684a0}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+75b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar  3 19:15:59.470 2010 (GMT-5)
System Uptime: 0 days 0:00:31.501
BugCheck 3B, {c0000005, fffff88001668b8e, fffff88009594840, 0}
Probably caused by : ndis.sys ( ndis!ndisNsiGetInterfaceRodEnumObject+22e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmpnetwk.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar  5 11:18:37.809 2010 (GMT-5)
System Uptime: 0 days 0:00:23.856
BugCheck 3B, {c0000005, fffff80002d0b52c, fffff8800835ae90, 0}
Probably caused by : memory_corruption ( nt!MiGetWsAndInsertVad+cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  taskhost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar  5 20:30:29.921 2010 (GMT-5)
System Uptime: 0 days 0:00:10.968
BugCheck 1000007E, {ffffffffc0000005, fffff80002e0190d, fffff88003361bb8, fffff88003361410}
Probably caused by : AgileVpn.sys ( AgileVpn!DriverEntry+1f7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

takitoes · 06 Mar 2010

Quote: Originally Posted by usasma

It's most likely this is a hardware issue. Since you've run MemTest and Furmark, that would seem to rule out the memory and the video card. As such, I'd try this free diagnostic: HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Thanks Usasma,

Ill run those HD diag's and the malware scan to help cancel that out.

I have completed runs of Linpack with 30+ test in a row, so i am positive it is not the CPU being faulty/unstable, so we can cross that one off the list.

Will get back to you with results.

takitoes · 06 Mar 2010

Update:

I completed the Intel SSD diagnostic with no errors recorded.

The Western Digital diagnostic didnt not work for me, i think the .iso may not be complete? but i have removed the 2 western digital drives as they are only for storage.

I also completed Panda, Kaspersky, Avast and Bitdefender scans on the SSD and only received a notice on one file i know is not a virus/trojan ect.

I also have prime95 running in the background at the moment with no errors reported.

I'm beginning to think maybe the Motherboard? I am fairly sure the PSU is fine, as it has never given me problems even with much higher work loads.

What do you think about the graphics card seating i mentioned in the first post? could that be causing problems like this?

Thanks again for your time!

takitoes · 08 Mar 2010

Bump,
Sorry i don't want to be rude. Im still looking for advise and idea's if anyone has them.

Thanks.

Windows 7: Random BSOD on startup (even safe mode)

Random BSOD on startup (even safe mode) problems?