Bluescreens after regular 2 week periods of no crashes

Gingermadman said:

Hi, This is my third post here I believe regarding the problems of blue screens.

My computer is a year and a half old and has always suffered from blue screens, I've replaced all the hardware / reinstalled windows and it will work fine after each changeover for about 2 weeks before beginning to crash and or blue screen.

I have a detailed history of my experience posted here : Bluescreens, constant startup cycle and freezing for a year and a half : techsupport


This has the progression of me returning my parts, my hardware list and the problems I encounter. This current crop of crashes is simply blue screens and a black screen when entering windows.

THis blackscreen will allow me to move around my cursor but happens after each blue screen and takes a while to revert to normal desktop.

Again, this problem randomly started up while I was playing a game, something which the crashes haven't been mutually exclusive too over the past year. I've included the 4 minidumps that actually saved over the past 3 days, the rest do not save and instead get to 65% saving and freeze up.

I plan to test prime95, memtest + and a hard drive tester soon, this is just to see if anything sticks out from the minidumps as I've yet to see a correlation between them (I'm not adept at reading them at all though)

Ran CHKDSK and it found and fixed errors, let's see if it actually worked. Edit. Fixing the errors on the disk did not work, still blue screening. Running Prime 95 just now, Not entirely sure how to run so just running torture test and the default settings.

Prime 95 been running for 5 hours with the default settings, nothing found so far and not blue screened. Computers are the worst things.

All of these are memory exceptions caused by a bad driver. I would as you said above run memtest and driver verifier to test the ram and find the d river.


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.



Driver verifier

I'd suggest that you first backup your stuff 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.

Gingermadman said:

Not blue screening at all with Driver Verifier on at all, any idea why that is?

Or Should I keep going on a bit longer, the problem is I can't view streams or stream video while verifier as running as for some reason it interrupts loading of the data.

In the verifier instructions it says it may take as long as 36 hours (an estimate) but you can do whatever it was you were doing the last time it crashed.

It should have no effect on viewing streams.