Windows 10: BSOD, changing error codes, usually after hibernation

Make sure you run memtext86+ for a minimum of 8 full passes. We've seen may cases where a memory error did not appear until; the later passes.

 

Sure. It just finished after 23 hours. 8 full passes (and another half) but no errors.

 

Not a fix, but how about disabling hibernate? Use a screen saver and sleep instead.

I power my computr on in the morning when I 1st use it and shut it down at night unless I want to run something over night.
Screen saver turns off the display after a set time and computer sleeps when it goes idle after 20 minutes.

From a elevated command prompt: powercfg /h off

 

I tried that, but of course it has the big disadvantage that the computer has to stay connected all the time. I usually switch off power after usage. I am traveling quite often and would feel uncomfortable knowing that the computer is powered while I am away. If there is any way to fix hibernation, I would prefer to use it.

By the way, I noticed more frequent crashes now. The only changes I made are an update of drivers for soundblaster. And I used the computer for watching movies lately. Maybe it is somehow related to graphics drivers and/or usage of VLC?

I got several new log files (the package is becoming larger and larger): Attachment 120747

Would be great if you could have another look at it.

Thank you in advance.

 

Several of the recent dumps have dxggms2 in the thread trace. No indication of an error there but maybe this points to a video driver/hardware problem. You have a AMD Radeon HD 7900 Series. There is a 2/8/17 driver available which is newer than what you now have. I suggest completely uninstalling the display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you card here: Radeon Software Crimson Edition ReLive Graphics Driver Installer for Windows 10 64-Bit

Then do a custom install of only the graphics driver.

See if that gets rid of the problem.

In the 12/6 dump I see a problem with avc3.sys. This belongs to BitDefender which is known to cause BSODs at times. I would suggest uninstalling BitDefender and running with the built-in Windows Defender for awhile, see if that helps.

 

Hello again,

I checked out several things after the clean install of the graphics driver.
With the new driver, everything seemed to work, no BSODs. But then after a session where I watched some DVDs and a BlueRay, I had the BSOD again. Over the last days, I noticed the BSODs almost happen with guarantee after I had either watch a movie, DVD or BlueRay or played one of the computer games. It does not matter which movie, disc or game, but out of 10 times after watching or gaming, the computer crashed out of hibernation roughly 9 times. The only instance it did not was when quite some time passed between watching and hibernation and the other it crashed not at wake-up but during work several minutes later.

I am not sure whether that helps in finding the issue but I feel like we are at least onto the BSODs...

 

Run dm_log_collector again and upload the zip file. See if anything useful shows up.

 

Thank you.
Output of dm_log_collector: Attachment 123805

 

The 3/2 sump indicates a problem with gzfile.sys:
Code: BugCheck 3B, {c0000005, fffff8064472d646, ffffa00050434130, 0} *** WARNING: Unable to verify timestamp for gzflt.sys *** ERROR: Module load completed but symbols could not be loaded for gzflt.sys Probably caused by : memory_corruption[/quote] Gzflt.sys file information

The process known as BitDefender Gonzales FileSystem Driver belongs to software BitDefender Gonzales by BitDefender (Bitdefender - Advanced CyberSecurity & Antivirus Software) or Bitdefender SRL (Bitdefender - Advanced CyberSecurity & Antivirus Software).

Since BitDefender has been known to cause BSODS I would suggest uninstall it.
Make sure Windows Defender and Windows Firewall are enabled.

Run that way for awhile to test, see if that resolves the problem.

 

Hello again.

Unfortunately, I am back again. I removed BitDefender and used the computer for a while. These crashes are still there. I did not yet get a BSOD but after wake-up from hibernation, the Windows logo appears with the waiting animation cursor. Then the screen goes dark and the computer reboots. Sometimes the screen even stays dark directly after wake-up and the next I see is the computer rebooting.

Again I noticed those restarts happen after I had watched a film (DVD, BluRay or file) or ran a game, i.e. applications heavily using the graphics card.

I let the tool collect logs for further analysis: Attachment 129481

Appreciate your help, as always.

 

The latest dump indicates a hardware (memory) problem:
Code: FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000837, physical page number Arg3: 000000000323d3b0, zero Arg4: ffffcd00e6d5a000, zero[/quote] Since you already ran memtest86+ for 8 passes with no error I suggest removing half of your memory and testing that way for awhile, see if a problem occurs. If yes, swap removed and installed memory and test again. It's possible there is defective memory even though memtest86+ did not detect it.

You can also try enabling Driver Verifier, see if that shakes anything out.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

 

Hello again,

swapping around the memory has been fun. I wonder who designed the mainboard to have memory banks be blocked by the CPU cooler???
Anyway, Driver Verifier did not reveal anything. No crashes occurred when Drive Verifier was on.

However, swapping around those memory modules was gold.
All four modules are of the same type and hold the same ID, but they are of a different age. I had BSODs and crashes after hibernation with the two modules of version 3.24, sometimes had crashes after hibernation when I mixed version 3.24 and version 7.x modules and no crashes (so far) when only the newer 7.x versions were installed.

Guess that means I will have to buy a new pair of modules and get rid of the 3.24?

 

Sure sounds like that is the way to go. Good luck.

No hurry getting new memory though. 8GB should work well for as long as need till you can get the new memory.

 

Hello again and greetings to Florida.

Just wanted to give you a short update. I installed the new memory. These modules and the pair of old ones work just fine. No more crashes, freezes or BSODs.

I still cannot believe it that after such a long time the crashes are gone. It is almost like working with a new computer. Without you, I would still have those crashes. Thank you so much for your patience and the support.

 

That is really good to hear. Thanks for letting me know.