BSOD in ntoskrnl.exe at random times

ChadGW · 19 Oct 2015

I have Windows 7 Home Premium 64 bit which has blue screened three times today. I am attaching the dumps.

I ran chkdsk /R and Windows memory diagnostic and they found nothing. I also ran sfc /scannow, a full virus check using Microsoft Security Essentials, and made sure everything was installed with Windows Update. I appreciate any and all insight.

Thanks,
Chad

**axe0** · 19 Oct 2015

Hi ChadGW,

Welcome to the 7forums.

I have only taken a look at the most recent crashes which are the crashes of this month.
The crashes are mostly leading to memory problems as there is a 0x1A(MEMORY_MANAGEMENT) which leads to memory problems and a 0xC2(BAD_POOL_CALLER) with

Code:

DEBUG_FLR_IMAGE_TIMESTAMP:  5609efa0

IMAGE_VERSION:  6.1.7601.19018

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xc2_7_nt!MiProcessDereferenceList+131

BUCKET_ID:  X64_0xc2_7_nt!MiProcessDereferenceList+131

There is also a 0x3B(SYSTEM_SERVICE_EXCEPTION) caused by graphics drivers, most likely due to memory problems.
Please test 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.

ChadGW · 20 Oct 2015

I ran the memory test ten times with no reported errors.

**axe0** · 20 Oct 2015

I don't know how many memory sticks you have and what the sizes are, but you can't run MemTest86+ 8 complete passes 10 times in such a short period.

ChadGW · 20 Oct 2015

3 2Gb sticks and it ran for about 12 hours.

**axe0** · 20 Oct 2015

How many passes?
It is not really about the hours, but about the completed passes.

ChadGW · 20 Oct 2015

I believe it was 10 passes.

**axe0** · 20 Oct 2015

Alright,
Please check inside the case for dust and remove it if there is any.

Lets test the drivers

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.