Windows 10: Windows 10 is unstable, frequent BSOD, but works in Safe Mode

I get BSOD's every 3-5 minutes in normal mode. In Safe Mode, it simply doesn't crash. Please, somebody help me hunt down the responsible driver so I can cut it up into little pieces and send each to the horizon in a different direction.


Minidump folder: https://1drv.ms/u/s!AvxrKCW2qmHng2S9ulp60RHkwSCe

MEMORY.DMP file: https://1drv.ms/u/s!AvxrKCW2qmHng2W15fwHU7lG3yrN

My hardware, in case it helps at all:

MB: ASUS Z10PE-D8 WS

RAM: two Kingston 16GB, 2133 MHz sticks

CPU: two i7-930 2.8GHz LGA 1366

GPU: EVGA GeForce GTX 1080

System drive: Samsung SSD



Many thanks for any help.



WinDbg output looks like this:

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 17763 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff805`6369a000 PsLoadedModuleList = 0xfffff805`63ab9a50
Debug session time: Tue Oct 9 17:36:22.939 2018 (UTC - 7:00)
System Uptime: 0 days 0:04:01.755
Loading Kernel Symbols
.....................................Page 20046ed0f too large to be in the dump file.
Page 20046ed1b too large to be in the dump file.
..........................
...Page 200843ffe too large to be in the dump file.
.............................................................
..................................................
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, ffffd2001d48c120, 0, 0}

Probably caused by : intelppm.sys ( intelppm!MWaitIdle+1f )

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

8: 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
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
Arguments:
Arg1: 0000000000000000
Arg2: ffffd2001d48c120
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME: Z10PE-D8 WS

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3703

BIOS_DATE: 04/13/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z10PE-D8 WS

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd2001d48c120

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x9C_GenuineIntel

CPU_COUNT: 18

CPU_MHZ: 95b

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R) SIG: 3C'00000000 (cache) 3C'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-OB9TOV0

ANALYSIS_SESSION_TIME: 10-09-2018 18:30:25.0093

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

BAD_STACK_POINTER: ffffd2001d48c0e8

LAST_CONTROL_TRANSFER: from fffff80563646f0a to fffff8056384af30

STACK_TEXT:
ffffd200`1d48c0e8 fffff805`63646f0a : 00000000`0000009c 00000000`00000000 ffffd200`1d48c120 00000000`00000000 : nt!KeBugCheckEx
ffffd200`1d48c0f0 fffff805`63647306 : 00000000`00000018 ffffd200`1d48c450 00000000`00000000 00000000`00000018 : hal!HalpMcaReportError+0x10e
ffffd200`1d48c240 fffff805`6364659c : 00000000`00000000 ffffd200`1d48c4d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xb6
ffffd200`1d48c270 fffff805`636475c7 : ffffa70b`152a4580 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffd200`1d48c2a0 fffff805`63926d1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffd200`1d48c2d0 fffff805`6385987a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0xb
ffffd200`1d48c300 fffff805`63859560 : ffffd200`00000000 fffff805`6385949d ffffd200`1d519180 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd200`1d48c440 fffff801`2445136f : fffff801`24451404 00000000`00000000 ffffa70b`1c447100 ffffd200`1d480180 : nt!KiMcheckAbort+0x260
ffffee8a`d108b7a8 fffff801`24451404 : 00000000`00000000 ffffa70b`1c447100 ffffd200`1d480180 ffffa70b`1c447010 : intelppm!MWaitIdle+0x1f
ffffee8a`d108b7b0 fffff805`63714d4b : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`000000a3 : intelppm!AcpiCStateIdleExecute+0x24
ffffee8a`d108b7e0 fffff805`637144ff : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0x6bb
ffffee8a`d108bb00 fffff805`6384e91c : ffffffff`00000000 ffffd200`1d480180 ffffd200`1d490600 ffffaf00`9980f040 : nt!PoIdle+0x33f
ffffee8a`d108bc60 00000000`00000000 : ffffee8a`d108c000 ffffee8a`d1086000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC: c27ae8e3aa1673e2a532a099a1c0ca38f6eee125

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1d6372f98c8231f90e52b814f5d491339e3ded59

THREAD_SHA1_HASH_MOD: 1fac79b8a426d5e706d6aa39f09833571fe2d165

FOLLOWUP_IP:
intelppm!MWaitIdle+1f
fffff801`2445136f 4585c9 test r9d,r9d

FAULT_INSTR_CODE: 75c98545

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: intelppm!MWaitIdle+1f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f330253

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

TARGET_TIME: 2018-10-10T00:36:22.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 9c1

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle

FAILURE_ID_HASH: {d82f1232-e6fd-ac41-d01e-ddeec73b684b}

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

:)

 

Password not accepted in Safe mode

Hi,

Thank you for posting your query on Microsoft Community forum.

Have you tried all the above steps suggested by Sangeeta Sarkar on September 13, 2015.

I would suggest you to provide some information to help you better.

• Are you trying to login the Microsoft account or the Local account in safe mode?
• Did you try with only safe mode or safe mode with networking?
• What is the critical error you are getting?

If you are using Windows 10. To go to safe mode you have to follow the below steps.

If you are able to go to login screen in normal mode try the below steps to go to safe mode with networking.

• 
  At the login screen click on the power symbol.
  
• 
  Hold SHIFT + Click Restart.
  
• 
  After restarting your system, select the Troubleshoot option.
  
• 
  Select advanced options under
  Troubleshoot screen.
  
• 
  Click on Startup Settings.
  
• 
  Click Restart and follow the onscreen steps to go to
  Safe Mode with networking and check if you are able to login.
  

[*]

Please get back with more information, we will be glad to help you further.

 

Windows 10 is not working even in safe mode

Hi All!
Over the past few days the start menu was not working properly and after trying to fiddle with that for a few days, i decided to reinstall windows 10. The problem with this now is that it boots up properly, but all i get is:




And the only buttons i have are "Networks" and "Ease of access" in the bottom right. Nothing else. The current build i have for W10 is 10240

If anyone could give me some insight on how to fix this i would be forever grateful!
Thanks.
mm

Ps. Safe mode works but i want to be able to run it outside of safe mode without it looking like the picture above.

 

Password not working in safe mode, windows 10

Hi Kevin,

Thank you for contacting Microsoft Community.

In order to help you better, could you please confirm a couple of things:

• What happens exactly when you enter the password?
• Are you getting any error message?
• How have you booted your computer into safe mode?
• Are you using local or Microsoft account to login?

I suggest you to force restart your computer and check whether you can get back your computer to normal mode.

You may follow the steps from the below article to place the computer in safe mode and check if it helps.

Start your PC in safe mode in Windows 10

http://windows.microsoft.com/en-in/windows-10/start-your-pc-in-safe-mode

Hope this information is helpful and do let us know if you need further assistance. We will be glad to assist.