Mass BSoD's 400+ instances, IRQL_NOT_LESS_OR_EQUAL/MEMORY_MANAGEMENT

[Ky0l]

Hello all,

I have been experiencing mass BSoD's and think it is related to [FONT=&quot]KB3121212, KB312400 and, or KB3124001.
IRQL_NOT_LESS_OR_EQUAL - is the most common.
MEMORY_MANAGEMENT - the second most common.
KERNAL_MODE_EXCEPTION_NOT_HANDLED - is quite common.
[/FONT]BAD_POOL_CALLER - quite uncommon.

Has anyone heard of these updates causing an issue?

Many thanks in advance.

 

[axe0]

Hi Ky0I,

Welcome to the 7forums

Please check HP for BIOS updates

BIOS Version:              Hewlett-Packard J01 v02.24, 20/09/[COLOR="red"]2013[/COLOR]

Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial
The logs only indicate 2 crashes in a few weeks.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

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.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {c55dcd68, 0, 0, 82ef49ca}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiDeleteVirtualAddresses+194 )

Followup: MachineOwner
---------

 

[Ky0l]

Afternoon axe0,

Thank you for replying so quickly. I have maybe 40 Toshiba ST-A20's having the issue, 40 HP desktop PC's. Mostly Windows 7 Pro - 32 bit, some Win XP and I understand both OS's just got the MRT updated.

Ran SFC /Scannow and some say there's courpt files, some don't.
Ran Memtest86+ for 14 hours with no problems found.

Unfortunately due to domain group policy I cannot change the minidump type.

The actual function call the kernel uses blew up on was MiDeleveVirtualAddresses – deleting something from virtual memory.


I very much doubt it's BIOS related as some of the machines effected where brand new from HP direct.

Hope that helps. Kind regards.

 

[axe0]

I understand that I saw the logs of 1 pc while there are many more having problems? That would explain about the missing dumps.

Virtual memory isn't the physical memory, only from the physical memory are dumps created.

How many passes have completed with MemTest86+? It is not about the hours but the passes, because a minimum of 8 passes is required to completely test the memory and it depends mostly on the amount of memory how long that takes, 8-10h usually with 8GB but it could also take 16-20h for the same amount of memory.

Updating the BIOS often helps improving system stability and/or fixes problems like bluescreens, however I couldn't find updates for the computer where I saw the logs from.

 

[Ky0l]

Thanks again axe0,

I would really rule out a memory problem, I realistically don't see 80+ machines all getting RAM problems over the course of 2 days.

Most/All of these machines do not have a BIOS update avaliable.

I can attach a snapshot of details for some of the machines. Maybe it will help?

 

[Ky0l]

[Too long and format didn't paste correctly.]

 

[axe0]

Please note that my suggestion was specific to the computer where the logs came from, for the others it can be something entirely different.

 

[Ky0l]

Sorry to bother you again axe0, maybe I missed the point, but what was the suggestion?

 

[axe0]

Shorty,

• Check for BIOS updates,
• SFC scan,
• MemTest86+,
• Be sure the configuration of the memory dumps are proper.

I have ignored your statement that you have done a few things, because I don't know if you have done them on the computer where the logs are coming from or another computer.