New build! Keep getting random BSOD!

[Random Thoughts]

I recently build a new computer and installed windows 7. I keep getting random BSOD though. I have reinstalled windows already and ran a memory test. I also tried using driver verifier but whenever I enable it windows automatically gets a BSOD. I have no idea what to do after that so I just restore to an earlier point. I would appreciate help with this thank you!

Specs:
Windows 7 Prof upgrade 64 bit with clean install from xp.
AMD Phenom XII 565
MSI Motherboard 880GM-E43
1TB Hitachi hard drive
4GB Kingston Value Ram

 

[MvdB]

Hello Random Toughts,

Please give us some more to go on. I don't mean to be rude or anything but we get loads of people who think they know what they are doing with their own build and then, when trouble comes, post limited info and think we can help. A lot of times we can... but we need ALL the info on the build. That is a lot more than what you provided. Please fill in ALL system spec's. All Components and any info, even if you think irrelevant that you encountered in the build. Sometimes it takes a week just to fin out someone put his Graphics card in the wrong slot, or put in the wrong RAM timings/voltages etc.

So, again, please, for us to help as best we can, be complete and specific.
see post nr 4: http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html#post256049

 

[Thorsen]

Driver verifier BsoD's when you have a driver problem this is the way it is supposed to work. So I would look at that first. Make sure all your drivers are up to date and if not get the newest drivers from the MFG websites.

More info is definitely needed.

Did you install drivers from CD's that came with the components? or updated drivers from the MFG websites or from Microsofts WHQL?



If drivers all look fine, then there is probably a problem with one of the componenets.

Have you checked Temps? Are all fans spinning?

When you installed the pieces in the Case did you use an antistatic strap or touch PSU to ground yourself while installing? If not, ESD might have caused a problem



First things that are easy to try are:

Re-seat RAM,

Verify all power connectors are attached correctly,

Take off Heatsink and thermal paste, re-seat CPU, reapply thermal paste and Heatsink


Since you didn't list the PSU, make sure it isn't a crappy PSU as these are usually bundled with bare-bones kits (in case this is what you purchased).
(If you purchased your own PSU and it is high power, high quality: good Job! )

If you can get a hold of a multimeter, test the power output as described in the PSU documentation. The voltages are also listed on the side of the PSU.

 

[Thorsen]

Another piece of info that would be good is if you had installed windows from a self-burned disc. Sometimes, burning windows to a disc causes errors and a slower burn speed is needed to prevent any issues with installation.

If you dl'd windows from the Microsoft site as an ISO then it would need to be burned to a disc (or a bootable flash-drive)

 

[Random Thoughts]

MvDB: Ahhh I'm sorry I'm new to this sort of things. The build is about 2 weeks old.

Specs:
Windows 7 Prof upgrade 64 bit with clean install from xp.
AMD Phenom XII 565
MSI Motherboard 880GM-E43
1TB Hitachi hard drive
4GB Kingston Value Ram
ATI Radeon HD 4250 (Built In)
Realtek High Definition Audio (Built In)
Thermaltake TR2 500W Power supply

Is there anything else I should add?

Thorsen: I ran Driver Scanner and the only driver that was not updated was the Realtek family controller driver but I do not know if that was a problem. And yes I did install the drivers from the components so all the drivers are basically updated as far as I know. Temp seems fine at around 25-27C with normal use such as surfing the web. But okay thanks for the advice I'll check everything and see if any more problems arises. And yes I did download Windows 7 from Microsoft so that might also be an issue so I will try to reinstall and see if any errors occur.

Thanks for the advice guys

 

[MvdB]

Ok, you have a good choice for a board and your PSU should be sufficient.
However, a common mistake with the capabilities of that board is that people immediately OC without having checked basic default stability.

So, in addition to Thorsens' advice, please try:

1. Make very sure the board is in default settings, no OC.
2. Boot in Safemode w/networking for a longer period of time and see if it runs (more) stable: Safe Mode - Windows 7 Forums
3. If Safemode is also NOT stable then please upload that dump, it will tell us much more and start testing memory:
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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The thing about this test is that it has its own simple boot and only tests HW, nothing to do with W7.

 

[Random Thoughts]

Okay I will run in safe mode and let you know how that goes. Also I already used Memtest86 and I did 7 passes with no errors. But I'll run it again just to make sure. Thanks!

 

[Random Thoughts]

Also recently I got a BSOD that said Driver IRQL Not Less Or Equal. Should I be concerned about this?

 

[MvdB]

Also recently I got a BSOD that said Driver IRQL Not Less Or Equal. Should I be concerned about this?

don't know, can you upload the dump please?

 

[Random Thoughts]

Okay here they are.

 

[MvdB]

You've got so many different type of error codes that it is difficult to pinpoint what to do first.

After mem testing lets do CPU:
Try this free stress test: Free Software - GIMPS

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.

 

[Random Thoughts]

I did a memtest no errors but I did the stress test and it said hardware error. I attached the results.

 

[Random Thoughts]

Also error happened about 20 seconds after running test.

 

[MvdB]

I did a memtest no errors but I did the stress test and it said hardware error. I attached the results.

Did you find the stress.txt file this refers to? If so, can you post that? This is only the log, not the result.
Even if you can't find it, seem your mobo or CPU has a prob. Before thinking the worstcase scenarios, I would perform a couple of careful steps to check:
1. Check all connections carefully especially power.
2. set BIOS to factory defaults
3. check all component compatibility - assume you did that before the build... but was there anything that was a risk?
4. If testing still shows errors, the only thing I can think of now is that I would replace all items , one by one, for checked/safe items as a test. i.e. CPU that has proven to be ok in other board, test, still problems? the same for Graphics card etc...