Solved BSOD on fresh install Windows 7

[pavey12]

Hey guys,
I built my PC from all new parts about 3-4 months ago, but from the get go it would intermittently blue screen, it settled down a month or two later but not sure why. Two days ago I wiped and formatted my drive and did a clean install of 7 as I was having unrelated issues I couldn't resolve. But now the blue screens are back. I thought it might be mobo driver issues but I finished updating the drivers and it's still happening.
System specs:
Windows 7 Professional 64x
Gigabyte ga-870fxa-ud5
AMD Phenom x6
AMD Radeon HD6870 1gb
two 4g G-Skill Ripjaw f3-12800cl9d-8gbxl RAM

Attached is the minidump and health report.
Thanks for any help!

 

[JMH]

> Your crash was related to AODDriver2.sys AMD OverDrive Service Driver from Advanced Micro Devices.
Remove > at least to test.

> Please run the update readiness tool and then update to SP-1

Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

> I suggest you download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[pavey12]

Thanks for the quick reply.
I have used the update readiness tool and updated to SP-1.
I should have mentioned that I posted this after my first BSOD since enabling dump files. There have been numerous crashes with a variety of errors. I have attached the updated dump files for viewing.

Thanks

 

[pavey12]

bump

 

[zigzag3143]

bump

I know BSOD's are frustrating but bumping after 3 hours is a bit over the top.

Your Crashes have several apparent causes but nothing definative. Please run the two tests below to help us narrow our focus.

ALSO please remove this driver as it has known problems with win 7 on some systems

AODDriver2.sys AMD OverDrive Service Driver from Advanced Micro Devices




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

* If you have raid update its Driver.



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



Driver verifier

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.

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

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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

 

[pavey12]

Sorry, I've only just started browsing these forums and from experience in other online forums once a thread falls to the second page its as good as gone. I work from this computer and have no secondary so you could say the frustration did get to me! Haha. Won't happen again, thanks for the heads up.

I will run the above tests and remove AODDriver2.sys and report back.http://www.runscanner.net/file/AODDriver2.sys.html

 

[JMH]

Sorry, I've only just started browsing these forums and from experience in other online forums once a thread falls to the second page its as good as gone. I work from this computer and have no secondary so you could say the frustration did get to me! Haha. Won't happen again, thanks for the heads up.

I will run the above tests and remove AODDriver2.sys and report back.

Noted.
We are both subscribed to your thread so will be aware when you next post.

 

[pavey12]

No worries.
Ok so I've run memtest86 and had no errors after nearly 8 passes, I then used verifier and got some consecutive crashes related to HIDCLASS.SYS which I have attached the minidumps of.

 

[Dave76]

Did you do this step as mentioned by zigzag3143 above?

Then select all drivers NOT provided by Microsoft and click "Next"

 

[pavey12]

Yep, checked all non microsoft drivers.

 

[Dave76]

Please upload all of the requested files.
Blue Screen of Death (BSOD) Posting Instructions
When posting any crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

What were the unrelated issues you couldn't resolve before the re-installation?

Did you install the motherboard drivers from the Gigabyte website?

Your crashes:
Two of these, both the same.

PAGE_FAULT_IN_NONPAGED_AREA (50) - Invalid system memory was referenced.
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Could not read faulting driver name
PROCESS_NAME:  LWEMon.exe
IMAGE_NAME:  win32k.sys

Three of these, all the same.

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) - The IO manager has caught a misbehaving driver.
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b
Resource @ nt!PiEngineLock (0xfffff8000328eb80)    Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
IMAGE_NAME:  HIDCLASS.SYS - Windows Hid Class Library

These crashes are similar and all are naming Windows drivers.
Can you check that no microsoft drivers are included in the Driver Verifier?


Out of date or problematic drivers:

gdrv.sys     Fri Mar 13 11:22:29 2009 - Gigabyte Easy Saver - mobo power utility driver
GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes

Un-install all Gigabyte utilities, for testing, they are known to cause crashes in Windows 7.
Un-install iTunes, for testing, it is known to cause crashes in Windows 7.

 

[pavey12]

I included a system health report in my first post but can run it again and upload if necessary. I was having mouse issues where I would need to press ctrl alt del and then press cancel in the options screen just to be able to click on the start bar on boot up and it would intermitantly reoccur every time I would switch between programs. I believed it was a driver issue but couldn't resolve it after many attempts and gave up. But the problem still occurred even after formatting my drive and during the windows install I found myself unable to check boxes without pressing ctrl alt del. So now I'm assuming it's a hardware issue but am yet to test on another pc or try a different mouse.

Motherboard drivers were updated with latest gigabyte drivers immediately after windows installed.

I am currently posting from my phone, when I get to my pc I will clear my minidump folder and run verifier again so as to not accidentally upload files from before the test runs. I will also uninstall gigabyte utilities as well as iTunes and see how we go.

 

[pavey12]

I've attached the latest minidump files since re-running verifier

 

[Dave76]

Upload all of the requested files.
Blue Screen of Death (BSOD) Posting Instructions
When posting any crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.


First thing you should do is test your system with a different mouse and/or keyboard.
Keyboard and mouse hardware faults can cause havoc with a large range of Stop codes and errors.

All three crashes are the same, DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9), and inconclusive.

Upload the other requested information files.

 

[pavey12]

I found a cheap Microsoft laser mouse laying around which works fine. Keyboard is a Logitech g510 and is only a few days old. I've possibly found the cause and solution. There are reports of incompatibility between ddr3 1600mhz RAM and AMD chipsets, I have manually adjusted the memory speed and timing and am currently testing the new configuration. If it successfully runs without crashing I'll consider this solved, else I will upload requested files.

 

[Dave76]

You are right, there are a lot of people with the 1600MHz/AMD issue.

Run it at 1333MHz, test it for a while.
If your still having issues, manually set the first four timings (use the info on the CPUZ SPD tab) Command Rate to 2T, bump the CPU NB VID control +0.05v, the DRAM from 1.50v to 1.55v.
This should run stable, if not you can post back with your settings.

 

[pavey12]

Two days and still no crash. I'm gonna go ahead an called this solved. Thanks everyone for your time and help.

For anyone coming across this in future with same problem, here's the guide I followed.
AMD CPU + G.Skill DDR3-1600 - GSKILL TECH FORUM

Cheers

 

[Dave76]

You're welcome.
Glad to hear you solved it, congrats.

It is a common practice to get your system stable before OC'ing, it can possibly be very difficult to get a stable OC if the system is not stable to start with. In your case it worked.
There are steps to follow when OC'ing, like find the max CPU frequency at stock voltage, then increase the CPU frequency and adjust the voltage to find the lowest voltage that your system will run stable at, the key is to keep the voltage as low as possible so it will run cooler.
Follow similar steps to OC the RAM, etc.
Sometimes plugging in numbers will work but, getting the system stable and cool as possible is the key.

Let us know if you have any more issues.