BSOD, seemed to correlate with a window update

radiowrench · 30 Sep 2015

Over the past two or three weeks or so I have routinely been getting BSOD sometimes while I am working on my computer during the day and sometimes it happens in the night if I leave my computer on. The problem started after I did a windows update or that is what it seemed to correlate with. At that time my PC would not start properly so windows start up repair utility tried automatically to fix the problem but failed so I had to return the PC to an earlier restore point. By doing this I have been able to use my PC, but it routinely fails to BSOD. I really cannot offer anymore insight than this. See my attached zip file created per the BSOD instructions.

Thanks,
Paul

**axe0** · 30 Sep 2015

Hi radiowrench,

Welcome to the 7forums.

There have recently been a few 0x1a(memory_management) crashes meaning memory problems.
Although sometimes there is a driver flagged, it is more likely to be bad memory.
Please check your memory using MemTest86+

Diagnostic Test

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

radiowrench · 01 Oct 2015

Hello SevenForum,

Per your suggestion I followed the directions for MemTest86 and let it run over night. It ran for 8 passes and there were zero errors. Please see the attached picture of my screen that verifies the 8 passes with zero errors with MemTest86. So it appears that I do not have a RAM memory problem. Do you have any other suggestions?

Sincerely,
Paul,
Davis, CA

radiowrench · 02 Oct 2015

In addition my PC appears to reboot every few hours at least when unattended.

**axe0** · 02 Oct 2015

Please check {windows partition}\windows\minidump\ for dump files to check if the reboots are from crashes.

radiowrench · 02 Oct 2015

I ran a program called BlueScreenView that can open up minidump files (apparently). I have attached a print screen. It looks like that lately I am getting PFN_LIST_CORRUPT caused by driver ntoskrnl.exe at address ntoskrnl.exe+735c0 and bug check error code 0x0000004e. The driver file is part of the NT Kernel & System. The file version is 6.1.7601.18939 (win7sp1_gdr.150722-0600).

What do you think this means?

Appreciate your help.

Paul

**axe0** · 02 Oct 2015

Bluescreenviewer gives enough information for the next step.

The crash usually points to the memory as does the 0x1a.
But, the memory is already tested, so it is likely a 3rd party driver causing this.
The ntoskrnl.exe file is blamed, because it is the last active. Without this file you cannot boot so it is never the cause.

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.