Solved Random BSOD - error 1E

[essenbe]

Well, that's how sleep is supposed to do. When it's put to sleep, everything is loaded into ram, which is the fastest thing in your computer. On waking up, everything is loaded from ram and it should be close to instantaneous.

 

[essenbe]

Did you load drivers for the motherboard when you did the install? here are the most current drivers for your board. Just make sure I am right and this is your motherboard GIGABYTE - Motherboard - Socket 1150 - GA-Z97-HD3 (rev. 1.0) Download and install the chipset drivers again and any other drivers that are more current than what you installed. Make sure this is right. There are 2 boards REV1.0 and 2.0, get the one for whichever REV, you have. At the top of the screen next to the name of the board, you can switch between Rev1 and REV. 2.

 

[tgmorris99]

Well, that's how sleep is supposed to do. When it's put to sleep, everything is loaded into ram, which is the fastest thing in your computer. On waking up, everything is loaded from ram and it should be close to instantaneous.

Understood. But it's noticeably faster now than with the other PSU, which is what's odd as I didn't make any SW changes between the two scenarios. However I did plug it back into the UPS and the system knows it via the USB port. It's almost like the other configuration was using a hybrid sleep, which would be 'normal' since it's a desktop, and this version is using pure sleep mode.

Did you load drivers for the motherboard when you did the install? here are the most current drivers for your board. Just make sure I am right and this is your motherboard GIGABYTE - Motherboard - Socket 1150 - GA-Z97-HD3 (rev. 1.0) Download and install the chipset drivers again and any other drivers that are more current than what you installed.

Yes, I DL'd all the drivers from Gigabyte (instead of using the CD that came with the mobo) along with the Intel chipset drivers. When checking the Intel site it says I'm good on the chipset items. I also went to Realtek to get the audio and GBe drivers.

Fingers crossed this fixes it for good.

 

[essenbe]

Good luck, I hope it works for you. It's a possibility that was the problem.

 

[tgmorris99]

I had such high hopes but wound up with a crash tonight. Interestingly, one error in the event log states that the shutdown at 8:32:33 was unexpected. However that would have been about the time that the system would have gone to sleep due to inactivity - though I'm not positive about that.

The other interesting bit was that the system started to wake up when I moved the mouse but then didn't complete. Hitting the power button then produced the dump.

ETA: MSE did download/install an update at 7:24pm

 

[essenbe]

OK, see if this helps, a lot of people use the terms Sleep and Hibernate interchangeably when they are actually 2 different things. In sleep, everything is saved to ram and the ram is still powered but the power is reduced. A mouse movement usually wakes it up. In Hibernate, everything it written from the ram to a special place on the hard drive, the mouse will not wake it up, it takes pressing the power button, but at that time the machine starts up instantly almost reading everything from the drive that was functional at the time it was last used.

Unfortunately, the dump gave us nothing. Have we run Driver Verifier yet? I'd like to run it anyway, but will leave that up to you. I really think the answer may be in the bios somewhere. Some of the options are buried deep in sub menus in the bios. It's simple to turn off Hibernate in the OS, but I'm not sure you wasn't to do that. I do, but I never use hibernate. If that is your problem though, it will solve that one anyway. I will leave bot options up to you. But, if you want to run driver verifier, here are the instructions with links that will help. Do not be surprised if it runs rather sluggish and slow. DV will do that. It puts extra strain on the driver in an attempt to make it BSOD and hopefully catch the offending driver. For that reason, it is important that you create a system restore point before enabling it. In some cases people can't even boot into Windows to turn it off, so a restore point from the recovery environment is the only way back. http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

   Warning

Be sure to create a Systm Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

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 tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. 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, do a System Restore to a point you made earlier.

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

 

[tgmorris99]

I've run the verifier previously but not since this incarnation of the reinstall so I'll give that a go.

I had hibernate turned off (powercfg /hibernnate off) and verified Although I guess it could have entered a hybrid sleep (though we didn't lose power overnight) and with hibernate off not sure what would happen there. For now I've again enabled hibernate but have it set to 'never' in the power settings menu.

I'll keep at it and see what happens but I guess I could have a bad mobo - but it seems odd it would only be at waking up. Interestingly, if I didn't do nightly backups I'd probably never know about this particular problem as I'd just do a shutdown instead of sleep.

 

[essenbe]

For the past couple of years all of the boards have had problems with sleep and Hibernate. I don't know why, but since the P67 boards came out, it has been a constant problem. The strange thing, is some boards don't have problems and some do, even from the same manufacturer and model. It could have something to do with overclocking as the set up to overclock you disable the C states. Some boards seem to have problems even without disabling them. So, I really don't know. The command to disable hibernate is powercfg -h off from an elevated command prompt. The problem most boards have is they will go into sleep or hibernate, but they won't wake up.

 

[tgmorris99]

Ok, I think the original BSOD problem has been resolved so I'm going to mark this as resolved and the original problem was likely a software conflict with Intel Rapid Storage and Samsung Rapid Mode. I'm still dealing with a start-up problem which seems to be related to the "unexpected shutdown" error, which presents during the wake from sleep, but will pursue that separately as it's not really a BSOD even though it produces a dump file.

At the moment I've still got the PC plugged into the UPS but have disconnected the USB cable so the system doesn't know it's on a plugged in battery. It's possible that without hibernate being available that if the UPS throws an error the system thinks power was lost even if it wasn't and thus can't recover since there's no hibernate file to load. If this makes the problem go away at least I'll know what I'm looking at.

The only other strange thing was that I was trying to update the Intel Management Engine stuff but keep getting a Fatal Error error from the Intel SW when trying to uninstall it and it also won't let me do a repair. I've run across a site with some knowledge on IME so I may pursue that there, but it doesn't seem to be impacting anything at the moment.

So thanks for all the help and hopefully the system can be made stable as far as the shutdown problem goes.

 

[essenbe]

I really don't know why IME won't install. Are you sure it isn't already installed? Also, you may try without the UPS and see if that helps. Sometimes UPS can be the problem, especially if batteries are low or something. Sometimes a software problem. But, I'm glad you've resolved part of the problem anyway.

 

[tgmorris99]

IME is installed but there's a newer version and so I was looking to see if that might help with the last issue. When I went to uninstall the current version it had the error and then same error when trying to do a repair.

I did try plugging into the wall directly but it didn't have any impact. However in that case I hadn't unplugged the USB monitoring cable so that may be why. The batteries are in good shape but I do hear it cycle once in a while so if that info gets passed up that may be the cause. Disconnecting the monitoring cable would eliminate that so I've got my fingers crossed. What's odd is that it was never a problem on the original system so it's either a HW issue or I didn't have the On Battery side of the Power Options set the same as the prior system.