Solved BSOD - Recovered From Unexpected Shutdown - Waking From Sleep

[Steve Sr]

Hello,

New computer installation issue has been ongoing since installation. Seems to always occur upon waking from deep sleep i.e. mouse is off and you have to hit the keyboard to wake up the PC. After hitting keyboard the system either crashes immediately or soon thereafter. As long as you keep the computer awake it appears to be stable.

The last instance I seem to recall the PC waking up but things were not right with Chrome. A few windows/tabs had the like there was no internet connection and then a crash. The pages were there before the computer went to sleep.

I did a little reading and have the DM log collector files. Unfortunately, I don't see the BC codes in there on first glance. Is there an easy way to gather these from a log file somewhere?

Thanks,
Steve

 

[axe0]

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Steve Sr]

Axe0,

More information:

Found the BugCheck codes 0x1E, 0x1A, 0x0A, 0x1A, 0x3B, 0x4E, 0x4E...seemingly random.

7 search SUCKS! Doesn't appear to do anything about half the time. Tried to find SFV because I couldn't get it to run where it should have been! Found it by manual searching. What a WASTE of time!

SFV /scannow <--- Doesn't work! Not a valid Program! How could MS break this!
SFV.exe /scannow <--- Works!

Good news... Found NO ISSUES!

MICROSOFT UPDATE ISSUES:

Found between 6-12 FAILED MS security and other updates. Don't know if this could be related or not. Haven't been able to figure out how to fix this either.

GIGABYTE ISSUES:

This PC was built in February 2017. At the time I went to the Gigabyte web site and downloaded and installed the latest driver I could find fro this MB. I DID NOT use the MB supplied CD.

This morning I get a notification from GB that there are 17 updates available! Started to install them but GB update crashed and burned about half way through. When it got to the hardware drivers they nearly ALL failed the download process. I suspect that their servers are overloaded.

On a few of the updates that succeeded the dates on some of the NFO files were BEFORE 2/2017 so I can't tell if I am being updated or downgraded! :banghead:

NEXT STEP(S)?

It would appear that further troubleshooting would be pointless until the 7 hardware drivers are updated? successfully.

I think I should have bought a MAC! This new 7 box has been a GIGANTIC frustration and WASTE of time! :banghead:

Anything else I should be doing?

 

[axe0]

Upload a new zip.

 

[Steve Sr]

Again, wasted most of the day messing with this and other failed update issues.

Finally got through to Gigabyte and they said that App Center update that I received was NOT intended for my system, Win 7 OR motherboard... Thanks Gigabyte! :banghead:

I tried to undo most of what the Updates did. At Gigabytes suggestion I completely deleted the App Center and ALL of the Gigabyte utilities that went with it. I do think that the update may have changed/updated a few drivers. One in particular was the USB driver. A lot of the others that failed to download/install were already current according to the Gigabyte website. A few I couldn't determine as the revision levels were waaaay different from what I already had. I suspect that these were intended for a different motherboard or different version of Windows.

Anyway, I have uploaded a current version of the ZIP file.

What's next wait for it to crash again to see if the problem still exists?


Thanks,
Steve

 

[axe0]

Reinstall or update all drivers from Gigabyte support page, do this manually.

I would recommend to not ever use software, even from the manufacturer, for driver updates. Always do this manually.

 

[Steve Sr]

Reinstall or update all drivers from Gigabyte support page, do this manually.

This may take some time as this is now my main work PC. Any chance that this could be short-cut by comparing the different versions of the drivers in the Drivers.txt file in the old and current ZIP files?

The MB was already 2 years old when the system was built in February. I pulled the drivers from Gigabytes web site at that time. Before the recent App Center fiasco there was only one Intel driver (or something) updated via MS Windows Update.

What is your biggest concern... having drivers that were downgraded by App Center's update or old drivers from Gigabyte's web site?


Thanks,
Steve

 

[axe0]

Best to not attempt to do this in shortcuts, this takes time once in a while but it is definitely worth it.

 

[Steve Sr]

I went ahead and removed the Gigabyte Supplied APP Center Malware and all of the attached utilities. One of these HCloud.exe was shown to be troublesome in the Reliability Monitor and is now gone with the rest of the garbage.

As far as drivers go I have reinstalled everything that appears to have been changed. However, in looking at the driver details it appears that some of the changed/updated INF files have AMD64 in the file name - but this is an Intel motherboard with a Z97X Intel chipset. These are from the correct motherboard link on the GB website. Does this sound correct/make any sense?

The good news is that the system hasn't crashed since I removed the Gigabyte Malware. So where do we go from here? Wait a while to see if the problem repeats?

 

[axe0]

AMD64 = 64-bit edition for both AMD and Intel processors.
i386 = 32-bits.

Yep to your last question.