Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Three BSODs in the last year. No activity connection.

27 Apr 2012   #1
Simon Fix

Windows 7 Home Premium x64
Three BSODs in the last year. No activity connection.

In the last year, I've had three BSODs at various times. Once, it happened while I was playing a game, and I assumed the problem was with either my graphics drivers, my graphics hardware, or with the game itself. The second one, however, came while I was using Writer, and the third happened this morning, when I was browsing the internet. (I think I have those first two right. I might be wrong, and the .dmp files might show it. After all, it's been a while, and I'm old and my memory is faulty. *chuckles*)

I know three BSODs might not sound like a lot, but I'm moderately concerned, and have no idea how to read .dmp files. I've attached the files, in case that helps, all in one handy .zip.

Thank you, in advance, for your assistance.

My System SpecsSystem Spec
27 Apr 2012   #2

Win 8 Release candidate 8400

Three different dates (Sept, Nov, and now) and three different causes. The only one relevant is the most recent and it was caused by memory management (probably a driver).

The first was hardware, the second inconclusive, and now memory management. These might all be one offs and the cure might be worse than the disease.

If you want to follow through these tests will help you find out which 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!!!

* If you have a Raid update its Driver.

*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

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/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"
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.
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)
My System SpecsSystem Spec

 Three BSODs in the last year. No activity connection.

Thread Tools

Similar help and support threads for2: Three BSODs in the last year. No activity connection.
Thread Forum
BSODs constantly regardless of current computer activity. BSOD Help and Support
Solved Multiple BSODs, no common activity BSOD Help and Support
I am here again... same issue like 1 year ago every day... bsods !!! BSOD Help and Support
Random BSoDs on one year old laptop BSOD Help and Support
Frequent, random BSoDs for over a year BSOD Help and Support
Solved Consistent BSODs for over a year. BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:54 PM.
Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App