Constant BSODs and program instability

[robotech420]

Hello,

I've had these issues since I built this computer in about February last year. Programs are unstable or freeze (SC2, Skyrim, even firefox). I get seemingly random BSODs. I can't really define a pattern of when they occur, but it is at least daily.

I have reinstalled the OS (win7 home premium 64 bit, full retail version) multiple times in an attempts to resolve. I have 2 HDDs in addition to my SSD. OS is currently on SSD. I had tried installing the OS on the HDDs as part of troubleshooting but ran into the same issues. I wiped the HDDs with Deriks Boot n Nuke before using them as storage.

I can run Furmark with no issues. I have run memtest86 with no reported errors. I've run Driver Genius Pro to keep everything there up to date.

I believe that is all relevant information. Please let me know if there is any further information required. I have been looking for a definitive conclusion for a long time. Thank you in advance for any help! I greatly appreciate it!

-Peter

 

[zigzag3143]

Hello,

I've had these issues since I built this computer in about February last year. Programs are unstable or freeze (SC2, Skyrim, even firefox). I get seemingly random BSODs. I can't really define a pattern of when they occur, but it is at least daily.

I have reinstalled the OS (win7 home premium 64 bit, full retail version) multiple times in an attempts to resolve. I have 2 HDDs in addition to my SSD. OS is currently on SSD. I had tried installing the OS on the HDDs as part of troubleshooting but ran into the same issues. I wiped the HDDs with Deriks Boot n Nuke before using them as storage.

I can run Furmark with no issues. I have run memtest86 with no reported errors. I've run Driver Genius Pro to keep everything there up to date.

I believe that is all relevant information. Please let me know if there is any further information required. I have been looking for a definitive conclusion for a long time. Thank you in advance for any help! I greatly appreciate it!

-Peter

You uploaded the application instead of the date please try this method.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[robotech420]

Well thats sort of embarrassing. I've removed the incorrect files and re-uploaded.

Also I've placed them on:
http://dl.dropbox.com/u/1531191/ActualDumpFiles.zip
Just in case.

 

[zigzag3143]

Well thats sort of embarrassing. I've removed the incorrect files and re-uploaded.

Also I've placed them on:
http://dl.dropbox.com/u/1531191/ActualDumpFiles.zip
Just in case.

No worries, happens all the time. Your crashes have many apparent causes but I suspect RAM or a driver.


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

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users