BSOD, changing error codes, usually after hibernation

darkwhite · 05 Mar 2017

Thank you.
Output of dm_log_collector: Attachment 123805

Ztruker · 05 Mar 2017

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

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.

darkwhite · 11 Apr 2017

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.

Ztruker · 11 Apr 2017

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

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.

darkwhite · 07 May 2017

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?

Ztruker · 07 May 2017

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.

darkwhite · 05 Jun 2017

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.

Ztruker · 05 Jun 2017

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