Random BSOD, Stop Code 1a, Hardware appears fine

[chemaddict]

First post here, but I read the rules, so sorry if I miss something

Computer Specs:
Motherboard: Gigabyte UD3H
Processor: Intel i5-2500K (not overclocked)
Graphics: HIS AMD 6870
HD: 1 x Patriot Pyro 60GB SSD (C and 1 x 1TB HD (B (Windows is on SSD, most programs on other HD)
Power Supply: 750W Antec
Operating System: Windows 7 Professional 64 bit SP1


Over the past month, I have BSOD randomly while playing DOTA 2 through Steam, browsing YouTube in Chrome, or other random places. Bottom line is that there isn't a consistent time/event when they occur.

First, I checked out the hardware: Ran Memtest for ~4 hours twice with no errors, used HD Tune to check for bad sectors on the HD, ran a program to test video card memory. There were no errors anywhere. I ran Microsoft Security Essentials and MalwareBytes on both disks to check for viruses/malware, with nothing reported.

Second, I looked into the ntoskrnl.exe reported in every BSOD I've had so far. I ran the verfier.exe according to other posts in this forum, but in setting that up, Windows won't boot past the Welcome screen (not the splash logo, but the one with the blue gradient background). I'm in safe mode at the moment, and everything seems fine (haven't had a BSOD in safe mode yet), so I'm kind of assuming this is a driver-related issue.

Attached you'll find my system dumps and info as this forum requests.

Thanks in advance for taking a look.

 

[chemaddict]

I should also mention that if my Video card drivers are out of date, this is because I reverted them from the most recent to see if that would fix the problem. It didn't, and I have yet to update them again, but this was happening even with the up to date AMD drivers.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1A[/COLOR], {41790, fffffa80039c8d30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

Followup: MachineOwner
---------

According to Carrona.org, STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results, with the subsequent crash dumps, if any.

 

[chemaddict]

I changed a few things -
1) set my RAM freq. back to 1600 instead of 1333 (1600 is not overclocked, it is the advertised speed of this RAM)
2) I uninstalled Gigabyte ON_OFF (applecharger.sys) and Gigabyte DES 2.0 (gdrv.sys) to see if that might help.

I got verifier working by NOT selecting the following drivers
dump_dumpfve.sys, dump_iastor.sys
because from what I could tell they are part of windows.

So now I can boot into Windows with verifier.exe running on all non-Microsoft drivers. It took a few hours, but I finally got a screen-freeze. There was no BSOD, the screen simply froze, mouse and all. It occurred after printing a document and then clicking on a link in Chrome (not reproducible). I waited for a while, but it remained frozen, so I pressed the power button and it turned off immediately, i.e. I didn't have to hold down power for 4 secs. When Windows booted again, I ran the SF_Diagnostic tool and I've attached the latest. Hopefully it has more useful info than the last.

Thanks for any help on the topic.

P.S. I'll run memtest overnight tonight and report back tomorrow.

 

[chemaddict]

Ran Memtest86+ for 10+ hours / 9+ passes and there were 0 errors.

 

[Pauly]

As well as memtest i would run some other hardware tests too as memory problems can be ram, hdd (pagefile) or even video ram
http://www.sevenforums.com/tutorials/433-disk-check.html
Hard Drive Diagnostic Procedure
SeaTools | Seagate
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[Dave76]

Good advice above, hard drive and graphics cards need to be tested.

One of your crashes is blaming des2svr.exe a Gigabyte EnergySaver2 utility, Uninstall all the Gigabyte utilities.

Your last System Event Log is from 2013-01-11.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

From the existing System Event logs:

Event[28464]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-12-30T14:28:51.478
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Bruton_Gaster
  Description: 
Processor 0 in group 0 exposes the following:

3 idle state(s)
19 performance state(s)
[B]8 throttle state(s)[/B]

This is indicating the CPU is overheating.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

From your App Event Log:
A lot of these.

Event[37514]:
  Log Name: Application
  Source: Microsoft-Windows-WMI
  Date: 2013-02-10T18:13:52.000
  Event ID: 10
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Bruton_Gaster
  Description: 
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

This usually indicates CPU issue, normally overheating.

 

[chemaddict]

I've done a stress test with furmark and my comp performed well - no crashes, temperature peaked at 88C

I had previously run an error scan on my hard drives with HD Tune, though I'm not sure how extensive that program is. There were no errors there.

The interesting thing is this:
I uninstalled all of the GIGABYTE programs that came with the motherboard (mostly BIOS-control programs), and I haven't gotten a restart / BSOD yet. In fact, when I tried to uninstall EasyTune with verifier.exe still running, it kept freezing. So, I think I've found the culprit. It was likely the GIGABYTE software interacting strangely.

For now, I think I'll wait a couple of days before marking this solved though, just to make sure. Thanks everyone for the help!

 

[chemaddict]

Duplicate Post, please ignore.

 

[Dave76]

Good news, uninstalling all the motherboard (all brands) utilities can fix stability issues, have seen this successful many times.

You can delete your own posts, use the 'Edit' button.

If you're still stable in 3-4 days you can mark this thread 'Solved'.

 

[chemaddict]

As a final post, here is what happened: While the above fixes did improve stability, the BSOD issue did not go away completely and persisted for a couple months at random times. I got used to it, but eventually it got much worse. I decided to reinstall windows as a last resort, and as I was installing the last 2 drivers I started BSOD'ing again. I deduced that it was one of the two and got rid of the easier one: the driver for my i5-2500K HD3000 graphics. So far, I haven't had any more issues and it appears to be resolved. So my conclusion is that that HD3000 graphics driver was interfering with my Radeon graphics card in some way causing crashes. To solve it I just uninstalled the HD3000 graphics driver completely.

Edit: Mods, feel free to mark this as solved.