BSOD out of nowhere and still happening on fresh install

CovertDeath · May 3, 2011

hi guys,

as the title states i started having BSOD's yesterday, they started out of nowhere then were about an hour apart for a few then became more and more frequent after each reboot, down to about 5 minutes before it would crash with me doing absolutely nothing.

this morning i installed a fresh copy of win7 after formating my HDD and about 2 hours into it i get another BSOD. i was able to install MSE, nvidia drivers, and wireless adapter drivers and that is all. i have attached the dump from the BSOD that occured during the fresh install. as i get more i will upload them as well.

all the BSOD's error messages have been different, some complain about memory management, some point to a .sys file.

please help me out as it is dead week on my university and i have projects that i NEED to finish this week that i must have my computer working for such as rendering CAD projects.

thank you,
Jimmy

EDIT: i had SP1 installed before i wiped everything, i was completely up to date. the dump you will see is of a fresh install so it is not SP1 yet

CovertDeath · May 4, 2011

Bump:

Had another bsod last bight but no dump was created, it happened on shut down and the error at the top was memory management.

Any help is much appreciated as this is a fairly new system.

OS: genuine windows 7 ultimate x64
Mobo: AsRock Extreme 3
CPU: AMD Phenom x4 955 (3.2Ghz)
Ram: 6gb (3x 2Gb) corsair 1600)
Gfx: GTX460 EVGA (latest drivers)
HDD: 500GB WD Caviar Blue
PSU: TX-750W Corsair silver certified 80 plus psu

I also have only my keyboard and mouse hooked up, no other devices are attached.

Sent from my HTC EVO 4g using Tapatalk

CovertDeath · May 4, 2011

i put in the install disc for win7 and ran windows memory diagnostics a few times with no errors.

then i went under options and changed the test mix to extended and made the pass count 5 and almost immediately (within the first 10% of pass 1 ) got a message saying "hardware problems were detected. to identify and repair these problems, you will need to contact the computer manufacturer."

does this mean it is a ram issue that has been causing my BSOD's???

could there still be another issue making the memory diagnostics tool tell me that but not actually be the memory?

CovertDeath · May 4, 2011

2nd Bump.

would really appreciate some input :/ i need to finish school projects and don't know how to get around this

Jonathan_King · May 5, 2011

Hello,

I can only think of two main causes for those memory errors: bad RAM, and a bad motherboard. By far, bad RAM is more common.

You might get a second opinion with Memtest86: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Also try the Blend Prime95 test: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

...Summary of the dumps:

Code:

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue May  3 19:17:05.519 2011 (UTC - 4:00)
System Uptime: 0 days 2:17:25.846
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3690c )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  drvinst.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+3690c
BiosReleaseDate = 09/14/2010
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

CovertDeath · May 5, 2011

i have ran memtest86+ booted from a flash driver over night will all my RAM in my rig and so far no errors after 14 passes and 23 hours of running.

the windows memory diagnostic still reads an error though so if its not the RAM then would it not be the CPU since the memory controller is now located on the CPU itself and not the NB?

Jonathan_King · May 5, 2011

It's possible the memory controller is at fault, but I'd expect to see some confirmation from something other than the Windows Memory Diagnostic, which has a reputation for the opposite behavior: passing bad RAM. Run each of the three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

CovertDeath · May 5, 2011

been running prime 95 for about an hour on the blended test actually and so far so good on that, ill move to the other two now and post back.

thanks for your replies, i appreciate the help and really hope you can help me get this figured out, its a pain in the ass having to do all my rendering on campus lol.

CovertDeath · May 6, 2011

okay so I ran prime95 all three tests over the course of the night and no errors what so ever, system running at good temps too, only got to 54*C

i have not had any more BSOD's over the past 36 hours either... I am now wondering if it could have somehow been a bad connection to the RAM or CPU as the ONLY thing i have done since the onslaught of BSOD's is reinstall win7 and remove the ram and CPU so i could test the RAM and then put it back in.

what are your thoughts?

Jonathan_King · May 8, 2011

Sorry about the delay...I'm getting caught up on my threads!

That seems plausible; I have seen a bad connection cause BSODs before. Let's hope the BSODs stop!

CovertDeath · May 8, 2011

so far so good still. the only thing of significance that has happened was yesterday. my computer had itunes up just playing music and all the sudden sound dropped and i lost the AEro theme. i think it somehow lost the drivers for everything as that is the only thing i could see to explain losing sound and aero theme. it was weird but besides that, everything is fine

CovertDeath · May 10, 2011

BSOD's are back... so far two today. nothing has changed on the system though. i have not installed a single program. one happened while system was idle around noon today and the other just happened while watching a video on ch131.

both read the memory management error uptop... here are the dumps.

Jonathan_King · May 10, 2011

This is obviously hardware-related; diagnosing which component will be tricky though, as the hardware tests we like have come up clean.

Run SeaTools: SeaTools for Windows | Seagate

Also, run chkdsk /r from a command prompt; note the results and post here.

Aside from that, we are down to actually swapping out components. You might start with the RAM, as that's the part that goes the most often. Try removing 1 or 2 sticks of RAM and running with the rest of them. If you get BSODs still, try a different stick, until you've confirmed the BSODs occur on all RAM sticks.

If you can test with a different PSU, that would be great. You've got a good one now, but PSUs can fail.

One other thing you may try is running the Extended Windows Memory Diagnostic again. Consistency will be our friend -- if it fails again, we may be seeing something...

...Summary of the dumps:

Code:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 10 21:24:21.819 2011 (UTC - 4:00)
System Uptime: 0 days 1:42:53.458
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
BiosReleaseDate = 09/14/2010
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 10 13:19:45.148 2011 (UTC - 4:00)
System Uptime: 0 days 4:54:55.787
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aa99 )
BUGCHECK_STR:  0x1a_5001
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+2aa99
BiosReleaseDate = 09/14/2010
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

CovertDeath · May 11, 2011

will do, I will update the thread as I complete more tests. as for the first BSOD sidebar.exe killing the system i actually witnessed the sidebar go all wonky on me then give me a force close message followed by a BSOD about 30 minutes later... there was quiet sometime in between though.

TESTS:
SeaTools: ALL test come up clean.
Prime95: ran blended test for ~3 Hours, cycled through many tests, all passed.
chkdsk /r (implies /f): not yet performed.
PSU: testing with a different PSU will be a problem as this is the only desktop i have access to :/ is there a way to test the PSU within the system?
Extended Windows Memory Diagnostic: not yet performed.
Isolating RAM sticks: not yet performed.

CovertDeath · May 11, 2011

just ran chkdsk /r d: since my install of win7 is on d and it seemed to come out clear. i took a picture of the results so you could look over yourself since i honestly do not know what all of it means. the picture is attached to this post.

i am running windows memory diagnostics extended right now. i have it set to run 5 passes... im 60% through pass 1 with no errors but i am going to let it finish all 4 passes and will update that test with its results in the morning. i am running this test will ALL sticks of ram (3x2gb) inside the machine. after this i will run each individual stick with memtest for a few hours.

thank you again for your continued support, i really hope to diagnose the problem here and fix it.

CovertDeath · May 11, 2011

running extended windows diagnostics over night came up with no errors after 8 passes. i have uploaded a screenshot of it as well. something interesting though. after i booted up, a .nfo file was place in my startup folder titled debug, BUT my system can not open the file. im not sure if it is normal to not be able to open NFO's or not but i have uploaded it here as well.

Jonathan_King · May 11, 2011

The NFO file is readable with Notepad; right-click > Open With. I don't know what created it, and I really can't take anything from the log.

Is there any chance you could pull out the nVidia for now, and use the onboard graphics? That would definitely lower the tax on the PSU, and just might help us. There are some PSU testers out there, but I don't really trust them. Replacement is by far the superior method.

CovertDeath · May 12, 2011

okay so now i am unable to recreate the BSOD or ANY error for that matter...

anyway idea on what could be causing all of this? it seems like one week it is fine then out of no where i get invaded by BSOD's then its good in a couple days

Jonathan_King · May 12, 2011

I'm thinking "far out" now...

If it was crunch week at your Uni, and many students were all running resource-intensive programs on their power-hungry desktops, the power circuit might have been at the outer limits of what it could support stably. If the wattage dropped below your system's requirements, even for a moment, you would have likely seen a reboot or BSOD. Better PSUs can handle more of a drop, but at some point, no PSU can supply the power.

If this was indeed the case, a UPS might help, as it can store enough charge to make the drop unnoticeable by your computer. It might also help to move the computer to a different circuit, one that has less of a load.

Then again, we're just speculating...nothing is assuring us this is power-related at all. I'm guessing you'll be going home for summer break soon? If so, you'll get to try a different circuit out. If you're staying on campus, you'll have little competition on the circuits in the mostly-empty dorms.

Keep us posted! If the problems persist, and we can rule out a power issue, we can keep plugging away at this.

CovertDeath · May 12, 2011

yea i will defiantly keep you updated, i am HOPING that i have seen the last of them. i actually live in apartments though, BUT i believe that we are tied into the university power grid so your theory is completely possible.

when you say UPS do you mean one of those power supply batteries ? if so i have actually looked into getting one and might have one here soon.

anyway i thank you again for all of your help. if things stay clear then i will post back in a week or so to report all systems go, else i will be posting back with errors lol

BSOD out of nowhere and still happening on fresh install

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer