different BSOD everytime

Joined
Nov 6, 2011
Messages
1
Reaction score
0
Hi, I keep getting BSODS periodically while using windows, everytime I get a different message, it seems like I've gotten all of them.
Have used memtest for one cycle, should I use it for more?
Attatched are my minidumps. I don't know how to analyze them so help would be greatly appreciated, thanks.
 

Attachments

Nibiru2012

Quick Scotty, beam me up!
Joined
Oct 27, 2009
Messages
4,955
Reaction score
1,302
Run Memtest for a minimum of 6 cycles, then any littles quirks will probably show up by then.

Sounds like you have some wrong RAM memory or BIOS settings going on here. I'm not a BSOD expert by any stretch of the imagination, but I would look to your motherboard's BIOS settings first. After that you may have either bad RAM or wrong settings and timings affecting the RAM.
 

zigzag3143

Wanikiya
Microsoft MVP
Joined
Sep 22, 2010
Messages
268
Reaction score
110
Hi, I keep getting BSODS periodically while using windows, everytime I get a different message, it seems like I've gotten all of them.
Have used memtest for one cycle, should I use it for more?
Attatched are my minidumps. I don't know how to analyze them so help would be greatly appreciated, thanks.
As my esteemed colleague suggested you have at least 10 various causes which does point to hardware (memory? perhaps)

Most are memory exceptions caused by either memory or a corrupt driver.

These crashes were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.


*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*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



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top