Windows 10: BSOD

Hello, I have been experiencing BSOD Machine Check Excepetion 9c for too long. I have completed a Windows reinstall. Can someone please help me decipher the kernel dump?


Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.





************* Path validation summary **************

Response Time ms Location

Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 19041 MP 8 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff806`39200000 PsLoadedModuleList = 0xfffff806`39e2a390

Debug session time: Thu Feb 25 16:20:44.156 2021 UTC - 8:00

System Uptime: 0 days 0:22:29.806

Loading Kernel Symbols

...............................................................

....Page fe7d1c not present in the dump file. Type ".hh dbgerr004" for details

............................................................

................................................................

..........

Loading User Symbols



Loading unloaded module list

.......

For analysis of this file, run !analyze -v

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



MACHINE_CHECK_EXCEPTION 9c

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available For example Intel

Pentium, the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available For example Intel

Pentium Pro, the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors If Param 1 is < 0x80000000

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

AMD64 Processors If Param 1 is > 0x80000000

1 - Failure Type

VALUES:

0x80000001: Spurious MCE

2 - Address of MCA_EXCEPTION structure

0x80000002: Rendezvous failure

2 - Address of MCA_EXCEPTION structure

END_VALUES

Arguments:

Arg1: 0000000080000001

Arg2: fffff8063d698b30

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 2



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on IJ-I7



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 5



Key : Analysis.Memory.CommitPeak.Mb

Value: 72



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 9c



BUGCHECK_P1: 80000001



BUGCHECK_P2: fffff8063d698b30



BUGCHECK_P3: 0



BUGCHECK_P4: 0



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



PROCESS_NAME: System



BAD_STACK_POINTER: fffff8063d698ae8



STACK_TEXT:

fffff806`3d698ae8 fffff806`396b5369 : 00000000`0000009c 00000000`80000001 fffff806`3d698b30 00000000`00000000 : nt!KeBugCheckEx

fffff806`3d698af0 fffff806`396b57c4 : 00000000`00000008 fffff806`3d698e70 00000000`00000000 00000000`00000008 : nt!HalpMcaReportError+0x149

fffff806`3d698c60 fffff806`396b49db : 00000000`00000000 00000000`80000001 fffff806`3d698ef0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0x11c

fffff806`3d698c90 fffff806`396b7225 : ffff8007`cc2beb30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f

fffff806`3d698cc0 fffff806`3970c959 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35

fffff806`3d698cf0 fffff806`39604bfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9

fffff806`3d698d20 fffff806`396048b7 : 00000000`00000000 fffff806`396047ec 00000000`00000001 00000000`00000000 : nt!KxMcheckAbort+0x7a

fffff806`3d698e60 fffff806`41f4138f : fffff806`41f41424 00000000`00000000 00000477`61d88ef0 00000000`00000000 : nt!KiMcheckAbort+0x277

fffff806`3d66d5b8 fffff806`41f41424 : 00000000`00000000 00000477`61d88ef0 00000000`00000000 00000000`0000008b : intelppm!MWaitIdle+0x1f

fffff806`3d66d5c0 fffff806`39471396 : 00000000`0000de1b fffff806`0000007f 00000000`00000000 00000000`00000000 : intelppm!AcpiCStateIdleExecute+0x24

fffff806`3d66d5f0 fffff806`39470154 : 00000000`00000000 00001fa0`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x10c6

fffff806`3d66d9f0 fffff806`395f95a4 : 00000000`00000000 fffff806`39f27600 ffff8007`d3830040 00000000`00000364 : nt!PoIdle+0x374

fffff806`3d66db60 00000000`00000000 : fffff806`3d66e000 fffff806`3d667000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54





SYMBOL_NAME: intelppm!MWaitIdle+1f



MODULE_NAME: intelppm



IMAGE_NAME: intelppm.sys



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 1f



FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {1e3f83d3-dcec-5c94-4c1c-54ecb2a7abc1}



Followup: MachineOwner

---------



0: kd> !blackboxbsd

Version: 176

Version check failure.

0: kd> !blackboxntfs



NTFS Blackbox Data



0 Slow I/O Timeout Records Found

0 Oplock Break Timeout Records Found

0: kd> !blackboxpnp

PnpActivityId : {00000000-0000-0000-0000-000000000000}

PnpActivityTime : 132587713024592396

PnpEventInformation: 3

PnpEventInProgress : 0

PnpProblemCode : 24

PnpVetoType : 0

DeviceId : SWD\DAFWSDProvider\urn:uuid:1c852a4d-b800-1f08-abcd-38eaa753b4f0

VetoString :



0: kd> lmvm intelppm

Browse full module list

start end module name

fffff806`41f40000 fffff806`41f80000 intelppm pdb symbols c:\symbols\intelppm.pdb\056C8B29DA3A94F94CB6E74FC4E34A161\intelppm.pdb

Loaded symbol image file: intelppm.sys

Image path: \SystemRoot\System32\drivers\intelppm.sys

Image name: intelppm.sys

Browse all global symbols functions data

Image was built with /Brepro flag.

Timestamp: 7EBD22FD This is a reproducible build file hash, not a timestamp

CheckSum: 0004204F

ImageSize: 00040000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Information from resource tables:

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT