Solved Random BSOD - error 1E

[tgmorris99]

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]

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

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

 

[tgmorris99]

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]

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

 

[tgmorris99]

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]

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]

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

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

 

[tgmorris99]

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]

Here's what the dumps say

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

gdrv
start             end                 module name
fffff880`1891b000 fffff880`18924000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\[COLOR=red]C:\Windows\gdrv.sys[/COLOR]
    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]

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.

 

[essenbe]

Sounds great. I hope your luck continues. If you would, let us know when you feel like the problem is resolved.

 

[tgmorris99]

Well I spoke too soon as I went to wake the computer up this morning and it promptly blue screened with a 5c code.

I'm still pretty sure the HW is OK based on prior testing and a new sfc /scannow passed w/no errors so I'm running with driver verifier enabled as I post this. I've yet to install the Renasas drivers but I did add a Logitech mouse along with their drivers.

I've attached the latest crash logs.

 

[essenbe]

Are you overclocking your system? Are there any settings in bios that affect hibernate? I'm noy familiar with Gigabyte bios, but I know there are sone settings in an Asus bios which will affect hibernation. The debugger won't tell us a lot, but I noticed a side comment about trying to unlock the CMOS lock. It's blamed on not being able to wake up the CPU.

nt!PopHandleNextState+12a
fffff800`01ec2cb9 8be8            mov     ebp,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt!PopHandleNextState+12a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
IMAGE_VERSION:  6.1.7601.18409
FAILURE_BUCKET_ID:  X64_0x5C_HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a
BUCKET_ID:  X64_0x5C_[COLOR=red]HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a[/COLOR]
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x5c_hal_failed_to_restart_processor_after_sleep_nt!pophandlenextstate+12a
FAILURE_ID_HASH:  {a3f9a84b-3b7e-1e59-ab8e-459ed3091bc2}
Followup: MachineOwner

 

[essenbe]

What the dump technicallt blames is IaStor, but I doubt that is correct

hiber_iaStorA
start             end                 module name
fffff880`1b41e000 fffff880`1b6e1000   hiber_iaStorA T (no symbols)           
    Loaded symbol image file: hiber_iaStorA.sys
    Image path: \SystemRoot\System32\Drivers\hiber_iaStorA.sys
    Image name: [COLOR=red]hiber_iaStorA.sys[/COLOR]
    Timestamp:        Thu Apr 03 18:00:05 2014 (533DE7F5)
    CheckSum:         000ABC34
    ImageSize:        002C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver created to provide disk access during crash dump file generation. I suspect that these are generated for crashes that occur during hibernation/sleep transitions

 

[tgmorris99]

I'm not overclocking at all even though the G3258 and mobo are able to to so.

I'll do a bunch of sleep/wakeup testing today to see if I can aggravate it.

ETA: It had a BSOD the first time I tried but was fine several times after that. I've attached the dump.

 

[essenbe]

If your bios has a setting, Asus calls it Internal PLL overvoltage, enabled will disable sleep and hibernate. Whether Gigabyte has that or calls it something different, I don't know.

Another thing to try, if you use hibernate, which you shouldn't need with an SSD, open an elevated command prompt (click start, type cmd in the search box, Right click the entry that appears and select run as administrator) in the command prompt copy/paste this and see powercfg -h on

 

[tgmorris99]

I looked but didn't see anything like that. Not sure what the next step will be.

I don't have hibernate configured, just sleep mode so my system backups can happen unattended to my WHS overnight.

 

[essenbe]

OK, just look at your CPU settings and make sure your S states are enabled.

 

[tgmorris99]

I managed to go about 3 days w/o a BSOD. That includes 1 1/2 days running with the verifier enabled and no problems and my unattended backups have been working fine. I was simply browsing the internet when I got another 0x1E from fltmgr.sys and the dump is attached.

 

[essenbe]

Check your SSD and make sure your Firmware is up to date also run Seatools for DOS (SeaTools for DOS | Seagate) on your other hard drives. Please make sure your Windows Updates are Current. Look at installed updates and see if there have been any Failures.