BSOD, changing error codes, usually after hibernation

darkwhite · 25 Jan 2017

Sorry... but I am back and still with issues occurring when starting from hibernation: Where before the PC showed BSODs the screen now stays dark and then restarts. This all happens right after turning the PC on again, before showing the flying Windows screen.

So far I only had two BSODs during operations but frequently the "stay-dark-and-restart" thingy I do not know how to handle.

Could you please look into it again? I already ran the tool for the log files: Attachment 118514

Thank you very much in advance.

Ztruker · 25 Jan 2017

Two of the dumps indicate memory_corruption:

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: 0000000000000bbd, physical page number
Arg3: 0000000002326050, zero
Arg4: ffffaa009f34b000, zero

You have four, 4GB memory DIMMS. You can run memtest86+ to test them or you can remove half and test for a week or so then swap memory and test again. Any failure under any of these test points to ram that needs to be replaced.

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

RAM will accept and keep random patterns of data sent to it
There are no errors when different parts of memory try to interact
There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

darkwhite · 26 Jan 2017

Thank you.

I ran memtest when I first posted here and had no errors even after multiple runs. Strange that the error comes up in the new logs. I will rerun the tests and let you know.

Ztruker · 26 Jan 2017

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.

darkwhite · 27 Jan 2017

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

Ztruker · 28 Jan 2017

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

darkwhite · 11 Feb 2017

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.

Ztruker · 11 Feb 2017

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.

darkwhite · 04 Mar 2017

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...

Ztruker · 04 Mar 2017

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