Random BSOD - error 1E

tgmorris99 · 25 Sep 2014

I've got a new build which I originally started out by replacing the mobo and keeping the existing Windows install. However I wound up doing a fresh install but have been encountering what seem like random BSODs. I thought I had it figured out as it was finally stable for a couple of days so I reinstalled a usb 3.0 driver for the 5.25 media dashboard (Renasas driver) and things quickly went south again. I did a system restore to back it out but I'm still getting BSODs.

What I've done to date to verify the HW:

Memtest86+ (5.01) for 9 passes (overnight) w/no errors
Prime95 for 4 hours
I've run the x264 stability test w/no problems
sfc /scannow (no errors)

I'm pretty sure the HW is good at this point and the Intel site says all the chipset drivers are current. I've also updated the realtek network & audio drivers.

The crashes can happen when waking from sleep or just browsing and the attached dump is from a crash that happened overnight during the nightly backup to my WHS. Since all the dumps blame the kernel it's almost got to be a driver related issue but I've yet to run driver verifier.

From a performance standpoint the system is great but I certainly favor stability over speed as it's just an everyday setup. Any help will be appreciated.

essenbe · 25 Sep 2014

I know you said that you ran memtest but this is what the dump file shows.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80001f09c27, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+97 )
Followup: MachineOwner

tgmorris99 · 25 Sep 2014

Hmmm. I'm in the middle of running another sequence that I started this morning and will be through 8 passes in another hour or so.

Is it possible the memory corruption is the result of a bad driver?

essenbe · 25 Sep 2014

I guess it could possibly be, but there are no drivers for ram. But, I guess it's possible.

tgmorris99 · 25 Sep 2014

I guess it could be the PSU but it's the same one I was using with the other mobo and that one was running a 9400GT video card and all the other HW was the same w/no BSODs. The new bits now are the GA-Z97-HD3 mobo, G3258 and the memory. If the memory passes again I guess it could still be the problem when under stress but last night it was just doing a WHS backup of the SSD when it crashed.

I'm open to any suggestions for further testing.

Once the memory tests are done I'll boot back up and run the verifier to see if I can catch anything that way.

essenbe · 25 Sep 2014

If you run verifier, run it this way but, make a restore point first
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

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 are no Restore 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.

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

tgmorris99 · 25 Sep 2014

Here's the results of the latest Memtest86+. Basically, nothing to report.

I'll start driver verifier tonight and see where that leads.

tgmorris99 · 25 Sep 2014

Well, it didn't take long as it never made it to the desktop. I got as far as the "Please Wait" before it crashed and rebooted and crashed again. I had to power cycle it to get it to boot into safe mode. I looked and there are 2 new dumps so hopefully this will point to the culprit.

essenbe · 25 Sep 2014

Here's what the dumps say

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80001f09c27, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+97 )
Followup: MachineOwner

Code:

gdrv
start             end                 module name
fffff880`1891b000 fffff880`18924000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Thu Mar 12 22:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That's the Gigabyte Easy Saver - mobo power utility driver

tgmorris99 · 27 Sep 2014

I managed to get it so gdrv.sys would load and things were running with the verifier still active. However there were still some remnants of the Gigabyte SW hanging around even after uninstalling everything. So I bit the bullet and did a clean install from scratch again without using the CA supplied CD and I think I'm good to go at this point.

I've yet to install the Renasas driver as I want to make sure the system is stable so if anything happens I'll know where to look but, fingers crossed, so far so good.

Thanks for the help.