Windows 10: Multiple BDOS in the last few days, all different error messages.

Hello guys, these past couple weeks ive had frequent BSOD, 0-2 a day.
The thing with these BSOD is that the last couple that I had, all had different error messages.
Here are some of the most recent ones below.

IRQL_NOT_LESS_OR_EQUAL
ATTEMPTED_WRITE_TO_READONLY_MEMORY
IRQL_GT_ZERO_AT_SYSTEM_SERVICE
MEMORY_MANAGEMENT
PFN_LIST_CORRUPT

Ive been thinking about just taking my computer apart and rebuild it and then do a fresh install of Windows wiping everything. Hoping that it might fix the problem, but before going to that length I thought id seek help to see if i can resolve this issue without doing that. So here I am.
Any help are very much appreciated.

:)

 

Multiple BSOD errors in the last few days

These 2 were related to our 2014 Malwarebytes. I would remove it and install the newest version available.

Other old drivers

lmimirr.sys 4/10/2007 6:32:45 PM

LMIRfsDriver.sys 7/14/2008 12:26:56 PM

ISCTD64.sys 11/27/2012 3:52:34 PM

RaInfo.sys 1/11/2013 8:19:28 AM

ScpVBus.sys 5/5/2013 5:31:26 PM

mwac.sys 6/17/2014 10:07:00 PM

TeeDriverx64.sys 9/23/2014 4:01:14 PM

How To Find Drivers:



Do not use device manager it may tell you the device is up to date but will not tell you if it is corrupt



Search Google for the name of the driver, or go to the computer makers site.

Compare the Google results with what's installed on your system to figure out which device/program it belongs to

Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).

If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

The most common drivers are listed on these pages:

Driver Reference Table (DRT)

Driver Reference Table (DRT)

Driver manufacturer links are on this page: http://www.carrona.org

 

Multiple BSOD errors in the last few days

Hello,

I cannot seem to pinpoint what is causing this to happen and it happens during random activities, not like when I am only trying to play games or only when I am running any certain program. There is a just constant stream of bad pool header errors and they
are becoming more and more frequent. I attached a link to the zip with my latest three DMPs and system info. Anyone who can point me in the correct direction, thank you!

110316-25125-01.zip

 

Hi krislin,

Welcome to the 10forums *Smile

Different error codes usually suggest hardware problems, sometimes specifically the RAM.

Please update the BIOS to version 3103
MAXIMUS VII HERO | Motherboards | ASUS Global

 

ive ran a memtest on both my ram and foud out one of them had errors so im using just 1 8gb stick atm. Haven't had a BSOD yet. I'll keep this updated if i do encounter a BSOD.

 

What memory test did you ran?

 

Well the bad ram was definitely causing me BSOD, but now im back to my old BSOD problems. problems that ive had since i first build my pc. the one i just got was whea_uncorrectable_error which is one i've seen plenty of times before. These BSOD arent like frequent. maybe like once a month, once a week, at worst maybe couple times a week. But over the 2 years its gotten to the point where when i get a BSOD , im just like meh, another blue screen. wait for it to restart and wonder how long it'll be for the next BSOD.

Not sure if you can help, but if you can that be great.

 

this was the minidump analyst

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00163148028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.


Debugging Details:
------------------




BUGCHECK_STR: 0x124_GenuineIntel


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


PROCESS_NAME: Overwatch.exe


CURRENT_IRQL: f


ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre


STACK_TEXT:
fffff800`d0f21a38 fffff800`cf811f1f : 00000000`00000124 00000000`00000000 ffffe001`63148028 00000000`be000000 : nt!KeBugCheckEx
fffff800`d0f21a40 fffff800`cf2228bc : ffffe001`63148028 ffffe001`631b7c00 ffffe001`631b7c00 ffffe001`631b7c00 : hal!HalBugCheckSystem+0xcf
fffff800`d0f21a80 fffff800`cf81240c : 00000000`00000728 00000000`00000000 fffff800`d0f21e70 00000000`00000000 : nt!WheaReportHwError+0x258
fffff800`d0f21ae0 fffff800`cf812764 : ffffe001`00000010 ffffe001`631b7c00 fffff800`d0f21c88 ffffe001`631b7c00 : hal!HalpMcaReportError+0x50
fffff800`d0f21c30 fffff800`cf81264e : ffffe001`622d7b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
fffff800`d0f21c80 fffff800`cf81288e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
fffff800`d0f21cc0 fffff800`cf812a10 : ffffe001`622d7b40 fffff800`d0f21ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff800`d0f21cf0 fffff800`cf15e47b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`d0f21d20 fffff800`cf15e231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff800`d0f21e60 fffff800`cf0e4a45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`4023ca50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x45




STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME: GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP: 0


IMAGE_VERSION:


FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE: KM


FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

 

It only says that there was a problem in executing something, but nothing else. Basically useless because this analysis is the same with all 0x124 CPU type crashes.

You need to provide a dump using the DM Log Collector so it can be analyzed further.

 

I would recommend to update the BIOS to the newest version 3103.
MAXIMUS VII HERO | Motherboards | ASUS Global


The only thing the dump shows is that because of a delay in execution, as we can see below, a hardware error occured.
Before the crash occurs, the system attempts to handle the error unsuccessfully whereafter the WHEA provides the report (shown in the second code) to the CPU which calls the bugcheck function.
As I mentioned, a 0x124 doesn't reveal much. I don't know if it is possible to find the instructions of the function calling KeDelayExecutionThread to find out a little more, but I doubt it.
Code: STACK_TEXT: fffff800`d0f21a38 fffff800`cf811f1f : 00000000`00000124 00000000`00000000 ffffe001`63148028 00000000`be000000 : nt!KeBugCheckEx fffff800`d0f21a40 fffff800`cf2228bc : ffffe001`63148028 ffffe001`631b7c00 ffffe001`631b7c00 ffffe001`631b7c00 : hal!HalBugCheckSystem+0xcf fffff800`d0f21a80 fffff800`cf81240c : 00000000`00000728 00000000`00000000 fffff800`d0f21e70 00000000`00000000 : nt!WheaReportHwError+0x258 fffff800`d0f21ae0 fffff800`cf812764 : ffffe001`00000010 ffffe001`631b7c00 fffff800`d0f21c88 ffffe001`631b7c00 : hal!HalpMcaReportError+0x50 fffff800`d0f21c30 fffff800`cf81264e : ffffe001`622d7b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8 fffff800`d0f21c80 fffff800`cf81288e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda fffff800`d0f21cc0 fffff800`cf812a10 : ffffe001`622d7b40 fffff800`d0f21ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce fffff800`d0f21cf0 fffff800`cf15e47b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff800`d0f21d20 fffff800`cf15e231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b fffff800`d0f21e60 fffff800`cf0e4a45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171 ffffd000`4023ca50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x45[/quote] Code: 0: kd> !errrec ffffe00163148028 =============================================================================== Common Platform Error Record @ ffffe00163148028 ------------------------------------------------------------------------------- Record Id : 01d1fc885ed87b7d Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/30/2016 1:59:22 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001631480a8 Section @ ffffe00163148180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 2 CPU Version : 0x00000000000306c3 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe001631480f0 Section @ ffffe00163148240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : c3 06 03 00 00 08 10 00 - bf fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe00163148240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00163148138 Section @ ffffe001631482c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : GCACHEL2_ERR_ERR (Proc 0 Bank 8) Status : 0xbe0000000100110a Address : 0x00000002039f2840 Misc. : 0x000003100e024086[/quote]

 

man the thread went to the 2nd page and i didnt spot that so i was just checking for 3 days straight even tho you alreayd posted xD.

 

do you have anything clue what would cause a delay in execution? could it be bad hardware?

 

A 0x124 means a hardware error occured, a hardware error could occur for various reasons, the cause is very difficult to tell with a single dump having not much data.

Asking for an execution delay for a thread isn't the problem, that is a thing that is done often.
For proper analysis I would think that the status of the delay would be need to known and if possible also some information about what called it, but I by far know enough of debugging to find that out.

 

seems the bios update fixed the BSOD, i cant believe one such simple thing was such a big issue. ive havent got a BSOD since.
Also thxs so much for the help *Biggrin