Recent BSOD ntoskrnl.exe seems to be the problem?

DigChaos · 12 Apr 2012

So i recently upgraded my system, new Motherboard ( Gigabyte GA-990FXA-UD3 ) 16GB of corsair XMS3 2000MHZ 4x4GB, CPU AMD FX-6100. Put it together about 2 weeks ago. I had planned on reinstalling windows 7, i put in the new hardware, windows installed all the new drivers and whatnot, restarted a few times and it was good to go. I installed all the mother board drivers, new video card drivers. Over clocked it to 4.7ghz and it was fine for about 2 weeks. Every once in a while it would throw me a bluescreen but whatever. About 2 days ago is when it really started giving me problems. Several blue screens every day. I downloaded a program called BlueScreenView and it shows me some info but i don't really know how to read it. The first file on the list is the ntoskrnl.exe, which is why i think it may be the culprit. I thought maybe the Overclocking was the issue, i ran fun under prime95 but i restored it back to defaults anyway. I thought for sure it would stop giving me blue screens. That did not fix anything, it's still doing it. I've attached the dmp files, there is lots of old ones, since it's a pretty old install. I figure you guys are probably going to say just to reinstall windows but if i can avoid that it would be nice. The blue screens from april are the ones i'm concerned about

Windows 7 x64 SP1 retail
besides the stuff i upgraded the rest of the hardware is about 3 years old. 2 GTX 260's in SLI, 300 GB Velociraptor, 750 PSU (corsair). ethernet, soundcard etc are all onboard

Thanks for taking a look

Photo Album - Imgur

zigzag3143 · 12 Apr 2012

Ok First these drivers need to be updated before we can get to the underlying memory corruption issue. I suspect your Directx.

Code:

pcouffin.sys    12/5/2006 10:39:30 AM        
lmimirr.sys    4/10/2007 6:32:45 PM       
RaInfo.sys    1/4/2008 2:57:14 PM       
wdcsam64.sys    4/16/2008 4:39:08 AM        
adfs.SYS    6/26/2008 4:52:37 PM        
LMIRfsDriver.sys    7/14/2008 12:26:56 PM       
ElbyCDIO.sys    2/17/2009 1:11:23 PM       
VClone.sys    5/22/2009 7:08:37 PM

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.php Driver Reference

- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html Drivers and Downloads

JMH · 12 Apr 2012

When you have followed zigzag's directions please do the following...

These crashes were caused by memory corruption/exception (Cx05) 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 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-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 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.

DigChaos · 12 Apr 2012

gonna run memtest overnight, i started it just now and got some errors already imgur: the simple image sharer

zigzag3143 · 12 Apr 2012

DigChaos said:

gonna run memtest overnight, i started it just now and got some errors already imgur: the simple image sharer

Did you do the drivers first?

You seem to have memory problems.

DigChaos · 12 Apr 2012

zigzag3143 said:

DigChaos said:

gonna run memtest overnight, i started it just now and got some errors already imgur: the simple image sharer

Did you do the drivers first?

You seem to have memory problems.

No, i haven't updated those yet, i'm going to look into that when i get home from work today. It was late so i just started running that memtest and went to bed. This is what memtest looked like when i woke up imgur: the simple image sharer What do you suggest? Running this on each stick individually? You don't think ill have to run it overnight for each stick do you? This is 2000MHZ memory, its currently running at like 1066 or something, when i had the system overclocked, i had also overclocked the memory to 1600mhz, do you think overclocking could of done this to the memory?

zigzag3143 · 12 Apr 2012

DigChaos said:

zigzag3143 said:

DigChaos said:

gonna run memtest overnight, i started it just now and got some errors already imgur: the simple image sharer

Did you do the drivers first?

You seem to have memory problems.

No, i haven't updated those yet, i'm going to look into that when i get home from work today. It was late so i just started running that memtest and went to bed. This is what memtest looked like when i woke up imgur: the simple image sharer What do you suggest? Running this on each stick individually? You don't think ill have to run it overnight for each stick do you? This is 2000MHZ memory, its currently running at like 1066 or something, when i had the system overclocked, i had also overclocked the memory to 1600mhz, do you think overclocking could of done this to the memory?

Thats from only two passes. It looks like memory or mobo slot. find a known good stick and test each slot.

As to OC'ing. You are pushing the components past their design limit, so yes. Did it cause it or was it co-incidence? I will never know.