Windows 7: BSOD reoccurs even after fresh install

Mask81 · 18 Apr 2012

HI All,

For more than a year now I have reocuring blues screen of death.
Here is what i did:

Checked memory sticks, I have 2*2 GB >> memory diagnostics everything is fine. Swithched sticks to diferent slots. >> no use

Reinsatlled full system. >> no use

Daemon tools are uninstalled after which I experience less BSOD but still occures. Previously ever day now every 3-4 days.

recently my previous HDD went bust, now I have a new one still issues.

System checks run fine and usually when windows would load up system crashes.

I am really annoyed as I think I have tried a lot of possibilities. Usually it is ntoskrnl.exe or cdd.dll that crash or when they start loading according to bluescreen viewer.

Pagefault in non paged area, boot sector errors are the 2 main reasons usually.

PLease see all minidum dump files and system info attached.

Could you please analyse and tell what youthink. Is it HDD? I am beginning to think that it is the mother board that cannot handle thinkgs correctly...

Thank you very much in advance

zigzag3143 · 18 Apr 2012

Only one DMP file was upload if you have more please upload them so we can spot trends.

Lets eliminate the OS by running a system file check.

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

There are obviously 2 possibiliteis Software, and hardware. The fact that the re-install yieded the same problem seems to point to hardware but we need to run a few tests.

First what memory test did you use (memtest is best, the built in is useless) and for how many passes.

Ram is the most probable hardware, followed by HD, cpu, etc

To test the drivers (software) we need you to run driver verifier

Of note ::::: You might want to update to SP-1 as it eliminates many software issues in the original release

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!!!

* If you have a Raid update its Driver.

Memtest.

Quote:

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

RAM - Test with Memtest86+

Driver Verifer

Quote:

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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/Windows 7 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Thanks to JGriff2 & Usasma.

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

Mask81 · 19 Apr 2012

Thank you very much for answering.

Earlier I ran memtest86 from floppy disk, checked each stick individually and had approx 3-4 cycles without any issues each.

Back to System checking, first I set verifier as described above. After everything set restarted pc. Nothing happend, however I realized that now everything is slower. Free commander, chrome load up slower.

Afterwards, I ran syste file checker from command line, some errors were found and corrected upon restart.

(I did not do anything in the mean time and restarted immediatelly in both cases so nothing installed or used etc)

Upon second restart BSOD happend again, during memory dump I could hear stuttering sound from speaker that I had not experienced before. This time a new error > IRQL_not_less or equal, but again at the same file ntoskrnl.exe.

PLease find dump files of this event attached.

I think verifier crashed this time is there a way to turn it off now as my PC seems to be slower?

I am not overcloking anything actually we are after a very fresh install of windows, did it on Monday. BIOS is at default settings except boot sequence.
No raid

Thank you for analysing these in advance

Mask81 · 19 Apr 2012

So now BSOD happened again because of a driver trying to corrput windows.

Verifier worked

please see Dump files attached. (previously BSOD only happened during win start up)

zigzag3143 · 19 Apr 2012

Quote: Originally Posted by Mask81

So now BSOD happened again because of a driver trying to corrput windows.

Verifier worked

please see Dump files attached. (previously BSOD only happened during win start up)

Verifier points to ntoskrnl.exe which is Highly unlikely. The process running at the time of the crash was ESET. There have been a spate of ESET related crash lately. I would remove and replace at least to test. Yours is from 2011

http://download.eset.com/special/ESETUninstaller.exe

Microsoft Security Essentials - Free Antivirus for Windows

Mask81 · 19 Apr 2012

thanks I will try it

Windows 7: BSOD reoccurs even after fresh install

BSOD reoccurs even after fresh install problems?