New PC, getting multiple BSOD

[zzenigmaxzz]

· OS - Windows 8.1, 8, 7, Vista ? windows 10
· x86 (32-bit) or x64 ? 64 bit
· What OS was originaly installed on the system? windows 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? volume license upgrade from employer
· Age of system (hardware) 1 week
· Age of OS installation - have you re-installed the OS? 1 week
· CPU model 6600k
· Video Card model EVGA Geforce 970
· MotherBoard - (if NOT a laptop) Asus z170-a
· Power Supply - brand & wattage (if laptop, skip this) EVGA supernova g2 550w
· System Manufacturer Custom
· Exact model number (if OEM or laptop) n/a
· Laptop or Desktop Desktop

 

Ok so first time building a new system from scratch and have been getting multiple BSOD, most recent was a machine check failure, and have also been getting system service check failures, following instructions in the posting instructions thread i have uploaded the files requested to mega

 

https://mega.nz/#!3o91CCTR!qT8WJOzdt8ozeHjk7s9RTw3UQqhIM-pnALjsd82i99k

 

any help would be appreciated

[SImoHayha]

Have you tried updating everything yes? And making sure you have the drivers for windows 10 and not for your previous OS ?

[Maximun]

i see you overclocked your cpu, im almost 65% sure thats the cause, it was bsoding me when i built my new pc like 3 weeks ago

[Jacles1]

Been getting a lot of BSOD on windows 10 too

[zzenigmaxzz]

i have removed the overclock and am still getting errors and yes i have updated all drivers and windows 10 has downloaded all updates

[Lethal Seraph]

Have you tried loading/reseting all values on the bios settings to default?

[zzenigmaxzz]

the only thing that is not at default is my memory which i used the prebuilt xmp profile

[Agazed]

Try resetting your BIOS.

[Astralify]

Could be bad memory controller on the CPU which can't handle the XMP memory profile. Also there are currently reports that z170 has many RAM compatibility issues. There should be bios updates that will fix these problems in the future. My suggestion is to try running the RAM at 2133MHz.

[zzenigmaxzz]

reset bios to default for now just a matter of waiting to see if it happens again would really like to know what exactly is causing the problems

[ionbasa]

· OS - Windows 8.1, 8, 7, Vista ? windows 10

· x86 (32-bit) or x64 ? 64 bit

· What OS was originaly installed on the system? windows 10

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? volume license upgrade from employer

· Age of system (hardware) 1 week

· Age of OS installation - have you re-installed the OS? 1 week

· CPU model 6600k

· Video Card model EVGA Geforce 970

· MotherBoard - (if NOT a laptop) Asus z170-a

· Power Supply - brand & wattage (if laptop, skip this) EVGA supernova g2 550w

· System Manufacturer Custom

· Exact model number (if OEM or laptop) n/a

· Laptop or Desktop Desktop

 

Ok so first time building a new system from scratch and have been getting multiple BSOD, most recent was a machine check failure, and have also been getting system service check failures, following instructions in the posting instructions thread i have uploaded the files requested to mega

 

https://mega.nz/#!3o91CCTR!qT8WJOzdt8ozeHjk7s9RTw3UQqhIM-pnALjsd82i99k

 

any help would be appreciated

Here is the WinDBG output for that dump file:

 

The crash was caused by "intelppm.sys". That component is a Microsoft provided driver for Intel CPUs. You mentioned you stopped overclocking. This most likely isn't a memory issue. What were your overclock settings? Include voltages multiplies, Base clock. What are your current settings? WHat voltage are you running at? Do you have XMP enabled?

 

Also, since this is a new build: Did you install the latest Intel .inf Chipset drivers? 

Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff803`da81c000 PsLoadedModuleList = 0xfffff803`dab41030Debug session time: Sun Aug 23 09:26:44.860 2015 (UTC - 4:00)System Uptime: 0 days 0:16:33.477********************************************************************************                                                                             **                        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 errorArguments:Arg1: 0000000000000000Arg2: ffffd001e356a760Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x9C_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fLAST_CONTROL_TRANSFER:  from fffff803db0a3ee1 to fffff803da969d00STACK_TEXT:  ffffd001`e356a728 fffff803`db0a3ee1 : 00000000`0000009c 00000000`00000000 ffffd001`e356a760 00000000`00000000 : nt!KeBugCheckExffffd001`e356a730 fffff803`db0a4323 : 00000000`00000004 ffffd001`e356aa30 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5ffffd001`e356a880 fffff803`db0a4450 : ffffe000`fb59a710 ffffd001`e356aab0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12bffffd001`e356a8b0 fffff803`da97367b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`e356a8e0 fffff803`da973431 : 00000000`00000000 fffff803`da9733b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`e356aa20 fffff800`750b2778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd001`e358b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_IP: intelppm!MWaitIdle+18fffff800`750b2778 c3              retSYMBOL_STACK_INDEX:  6SYMBOL_NAME:  intelppm!MWaitIdle+18FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: intelppmIMAGE_NAME:  intelppm.sysDEBUG_FLR_IMAGE_TIMESTAMP:  559f383bFAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm!MWaitIdle+18BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm!MWaitIdle+18Followup: MachineOwner 

[zzenigmaxzz]

i didnt touch the voltage, only raised the multiplier to 46 left the bclk at 100, i reset everything to stock so right now running at .767 voltsat idle 1.22 when at 3.9 ghz (turbo boost) and i have disabled xmp memory is running at 2133 mhz 15 15 15 35

 

and how would i install the intel update, i downloaded intel driver update utility, ran a scan and it said it found no drivers guess that means theres nothing to update?

[ionbasa]

i didnt touch the voltage, only raised the multiplier to 46 left the bclk at 100, i reset everything to stock so right now running at .767 voltsat idle 1.22 when at 3.9 ghz (turbo boost) and i have disabled xmp memory is running at 2133 mhz 15 15 15 35

 

and how would i install the intel update, i downloaded intel driver update utility, ran a scan and it said it found no drivers guess that means theres nothing to update?

Here is the link to the latest Intel INF chipset drivers: https://downloadcenter.intel.com/download/20775/Intel-Chipset-Device-Software-INF-Update-Utility-

[zzenigmaxzz]

Here is the link to the latest Intel INF chipset drivers: https://downloadcenter.intel.com/download/20775/Intel-Chipset-Device-Software-INF-Update-Utility-

its saying i have a newer version already and asking if i want to downgrade

[ionbasa]

its saying i have a newer version already and asking if i want to downgrade

Strange.  Intel always should have the latest INF versions on their site. I'm not quite sure where you may have gotten a newer version than what Intel currently has published.

[ionbasa]

its saying i have a newer version already and asking if i want to downgrade

Also, while you're at it. Mind running a stress test with AIDA64 and checking CPU temps? 

 

If it's not chipset related, then there is definitely something wrong with a hardware configurations. 0X9C stop codes usually point to CPU fault. By running AIDA64 we can test that the CPU isn't failing under load and that the temps aren't getting too toasty. 

[zzenigmaxzz]

Also, while you're at it. Mind running a stress test with AIDA64 and checking CPU temps? 

 

If it's not chipset related, then there is definitely something wrong with a hardware configurations. 0X9C stop codes usually point to CPU fault. By running AIDA64 we can test that the CPU isn't failing under load and that the temps aren't getting too toasty. 

 

running at stock 3.5 its highest temp is around 46c on hottest core after running for about 5 minutes, when i had it ocd i ran prime 95 and got no errors and max temp got to like 60 after 2 hours

[ionbasa]

running at stock 3.5 its highest temp is around 46c on hottest core after running for about 5 minutes, when i had it ocd i ran prime 95 and got no errors and max temp got to like 60 after 2 hours

Do me a favor and repair install windows per this guide: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

You'l keep all programs and documents. Activation will be kept. Settings will be reset, but this will ensure that Windows files aren't corrupt.

[misplacedsocks]

Hey guys, same issue here. Figured I'd join in on this thread instead of creating a new one.

 

· OS - Windows 8.1, 8, 7, Vista ? Windows 8.1 Pro
· x86 (32-bit) or x64 ? 64 bit
· What OS was originaly installed on the system? Windows 8.1 Pro

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? Full retail version (MSDNAA)
· Age of system (hardware) 1 week
· Age of OS installation - have you re-installed the OS? 1 week - Yes 3 days ago
· CPU model 6700k
· Video Card model Palit Jetstream 980Ti 
· MotherBoard - (if NOT a laptop) Asus Z170-A
· Power Supply - brand & wattage (if laptop, skip this) Corsair RM750i 750W
· System Manufacturer Custom
· Exact model number (if OEM or laptop) N/A
· Laptop or Desktop Desktop

 

I can share the rest of the specs if need be. Looking at zzenigmaxzz's specs, the only components we share are motherboard, SSD (850 EVO 1tb) and CPU (6700k).

 

I've run into the random restarts on Windows 7, 8.1 and 10, having unsuccessfully tried to pin it down to a variant of Windows in particular.

 

The requested files can be found here : https://dl.dropboxusercontent.com/u/27439435/BSOD/BSOD-Z170A.7z

 

No overclock on the CPU on my machine, I'm running the XMP Preset for RAM (2666 MHz which the kit is advertised for), but I've found that it's just as unstable with or without the RAM speed being changed.

 

Drivers are all from the manufacturers' sites, fairly sure they're all up to date but after wrestling with it for a week I'm open to any ideas.

 

Seeing similar things to zzenigmaxzz. The BSOD shows a mix of MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED, DPC_WATCHDOG_VIOLATION,  and IRQL_NOT_LESS_OR_EQUAL.

 

Many thanks for your time and help!

[zzenigmaxzz]

yep pretty much the same set of errors im getting, ive gone through 2 clean installs and still having issues

[ionbasa]

Hey guys, same issue here. Figured I'd join in on this thread instead of creating a new one.

 

· OS - Windows 8.1, 8, 7, Vista ? Windows 8.1 Pro

· x86 (32-bit) or x64 ? 64 bit

· What OS was originaly installed on the system? Windows 8.1 Pro

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)? Full retail version (MSDNAA)

· Age of system (hardware) 1 week

· Age of OS installation - have you re-installed the OS? 1 week - Yes 3 days ago

· CPU model 6700k

· Video Card model Palit Jetstream 980Ti 

· MotherBoard - (if NOT a laptop) Asus Z170-A

· Power Supply - brand & wattage (if laptop, skip this) Corsair RM750i 750W

· System Manufacturer Custom

· Exact model number (if OEM or laptop) N/A

· Laptop or Desktop Desktop

 

I can share the rest of the specs if need be. Looking at zzenigmaxzz's specs, the only components we share are motherboard, SSD (850 EVO 1tb) and CPU (6700k).

 

I've run into the random restarts on Windows 7, 8.1 and 10, having unsuccessfully tried to pin it down to a variant of Windows in particular.

 

The requested files can be found here : https://dl.dropboxusercontent.com/u/27439435/BSOD/BSOD-Z170A.7z

 

No overclock on the CPU on my machine, I'm running the XMP Preset for RAM (2666 MHz which the kit is advertised for), but I've found that it's just as unstable with or without the RAM speed being changed.

 

Drivers are all from the manufacturers' sites, fairly sure they're all up to date but after wrestling with it for a week I'm open to any ideas.

 

Seeing similar things to zzenigmaxzz. The BSOD shows a mix of MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED, DPC_WATCHDOG_VIOLATION,  and IRQL_NOT_LESS_OR_EQUAL.

 

Many thanks for your time and help!

Please start a new thread. and tag me by using "@ionbasa" without quotes.

 

yep pretty much the same set of errors im getting, ive gone through 2 clean installs and still having issues

How are you still having issues. You never replied back or posted more dump files, so I assumed it was solved. Feel free to post more dump files and I'll take a look at them through the Windows Debugger. The more dump files, the merrier. 

[zzenigmaxzz]

Please start a new thread. and tag me by using "@ionbasa" without quotes.

 

 

 

How are you still having issues. You never replied back or posted more dump files, so I assumed it was solved. Feel free to post more dump files and I'll take a look at them through the Windows Debugger. The more dump files, the merrier. 

ok heres the next set, hopefully it tells you something new

 

https://mega.nz/#!nxdgwThL!X9u-UQZunn_fF024ueQrKj3m3_MXHhC0pSP4lzQHzNg

[ionbasa]

ok heres the next set, hopefully it tells you something new

 

https://mega.nz/#!nxdgwThL!X9u-UQZunn_fF024ueQrKj3m3_MXHhC0pSP4lzQHzNg

Well, this is the exact same one as before? Delete the previous folder and zip and try running the tool again. I don't think it'll override files if the folder already exists.

[zzenigmaxzz]

ok how about this one?

 

https://mega.nz/#!C59Q2LKT!zoWBJaHBtyeaooOuRSdIqHzokt8Kl72sQTc6Rb3ku_k

[ionbasa]

ok how about this one?

 

https://mega.nz/#!C59Q2LKT!zoWBJaHBtyeaooOuRSdIqHzokt8Kl72sQTc6Rb3ku_k

Ok, there were four new dump files.

 

Okay, so this time it was much better. There seems to be some memory corruption issues going on. Also, an NVIDIA component seems to be causing trouble. That component is "NvStreamNetwork" which is part of Nvidia Game Streaming. Of note, is that you also had a BSOD related to the network stack, which is probably being caused by the Nvidia Network Streaming service. It seems that an issue present in the networking stack is causing the Windows' kernel to panic.

 

• So, by chance do you actually use Nvidia Game Stream?
• What GPU drivers are you running?
• And have you ran at least a 6 hour pass using Memtest86+ http://www.memtest.org/?

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Downloads\Documents1\SysnativeFileCollectionApp\082315-8718-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff803`da81c000 PsLoadedModuleList = 0xfffff803`dab41030Debug session time: Sun Aug 23 06:26:44.860 2015 (UTC - 7:00)System Uptime: 0 days 0:16:33.477Loading Kernel Symbols.................................................................................................................................................................................Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 9C, {0, ffffd001e356a760, 0, 0}Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )Followup: MachineOwner---------1: 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 errorArguments:Arg1: 0000000000000000Arg2: ffffd001e356a760Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------BUGCHECK_STR:  0x9C_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff803db0a3ee1 to fffff803da969d00STACK_TEXT:  ffffd001`e356a728 fffff803`db0a3ee1 : 00000000`0000009c 00000000`00000000 ffffd001`e356a760 00000000`00000000 : nt!KeBugCheckExffffd001`e356a730 fffff803`db0a4323 : 00000000`00000004 ffffd001`e356aa30 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5ffffd001`e356a880 fffff803`db0a4450 : ffffe000`fb59a710 ffffd001`e356aab0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12bffffd001`e356a8b0 fffff803`da97367b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`e356a8e0 fffff803`da973431 : 00000000`00000000 fffff803`da9733b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`e356aa20 fffff800`750b2778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd001`e358b758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_IP: intelppm!MWaitIdle+18fffff800`750b2778 c3              retSYMBOL_STACK_INDEX:  6SYMBOL_NAME:  intelppm!MWaitIdle+18FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: intelppmIMAGE_NAME:  intelppm.sysDEBUG_FLR_IMAGE_TIMESTAMP:  559f383bIMAGE_VERSION:  10.0.10240.16384BUCKET_ID_FUNC_OFFSET:  18FAILURE_BUCKET_ID:  0x9C_GenuineIntel_intelppm!MWaitIdleBUCKET_ID:  0x9C_GenuineIntel_intelppm!MWaitIdleANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x9c_genuineintel_intelppm!mwaitidleFAILURE_ID_HASH:  {b437bf01-d2c2-2e2f-fa19-a64dea7afbde}Followup: MachineOwner---------1: kd> lmvm intelppmstart             end                 module namefffff800`750b0000 fffff800`750d9000   intelppm   (pdb symbols)          c:\symbols\intelppm.pdb\89FABBD09556447FB6B157B5A3A81CD91\intelppm.pdb    Loaded symbol image file: intelppm.sys    Mapped memory image file: c:\symbols\intelppm.sys\559F383B29000\intelppm.sys    Image path: \SystemRoot\System32\drivers\intelppm.sys    Image name: intelppm.sys    Timestamp:        Thu Jul 09 20:12:59 2015 (559F383B)    CheckSum:         0001FAC6    ImageSize:        00029000    File version:     10.0.10240.16384    Product version:  10.0.10240.16384    File flags:       0 (Mask 3F)    File OS:          40004 NT Win32    File type:        3.7 Driver    File date:        00000000.00000000    Translations:     0409.04b0    CompanyName:      Microsoft Corporation    ProductName:      Microsoft® Windows® Operating System    InternalName:     intelppm.sys    OriginalFilename: intelppm.sys    ProductVersion:   10.0.10240.16384    FileVersion:      10.0.10240.16384 (th1.150709-1700)    FileDescription:  Processor Device Driver    LegalCopyright:   © Microsoft Corporation. All rights reserved. 

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Downloads\Documents1\SysnativeFileCollectionApp\082515-11062-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff800`ba80f000 PsLoadedModuleList = 0xfffff800`bab34030Debug session time: Tue Aug 25 17:29:43.909 2015 (UTC - 7:00)System Uptime: 2 days 4:33:39.530Loading Kernel Symbols..................................................................................................................................................................................Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck D1, {2c, 2, 0, fffff801004e1fd1}*** WARNING: Unable to verify timestamp for e1d65x64.sys*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sysProbably caused by : NETIO.SYS ( NETIO!KfdClassify2+111 )Followup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 000000000000002c, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff801004e1fd1, address which referenced memoryDebugging Details:------------------READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes 000000000000002c CURRENT_IRQL:  2FAULTING_IP: NETIO!KfdClassify2+111fffff801`004e1fd1 448b402c        mov     r8d,dword ptr [rax+2Ch]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freTRAP_FRAME:  ffffd00160b56100 -- (.trap 0xffffd00160b56100)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffe00065f2dd30 rbx=0000000000000000 rcx=ffffe0005ed95010rdx=ffffd00160b56740 rsi=0000000000000000 rdi=0000000000000000rip=fffff801004e1fd1 rsp=ffffd00160b56290 rbp=ffffd00160b562f9 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000r11=fffff801002b13d7 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl zr na po ncNETIO!KfdClassify2+0x111:fffff801`004e1fd1 448b402c        mov     r8d,dword ptr [rax+2Ch] ds:ffffe000`65f2dd5c=????????Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff800ba9676a9 to fffff800ba95cd00STACK_TEXT:  ffffd001`60b55fb8 fffff800`ba9676a9 : 00000000`0000000a 00000000`0000002c 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd001`60b55fc0 fffff800`ba965ec8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffd001`60b56100 fffff801`004e1fd1 : ffffe000`65f576ef ffffe000`648d4624 ffffe000`000096cb ffffd001`60b56470 : nt!KiPageFault+0x248ffffd001`60b56290 fffff801`00207b6b : 00000000`00000002 ffffe000`65a2c040 00000000`00000000 00000000`00000000 : NETIO!KfdClassify2+0x111ffffd001`60b56360 fffff801`00208ee1 : 00000000`00000010 ffffe000`65bca8f0 00000000`00000592 00000000`00000000 : tcpip!WfpProcessInTransportStackIndication+0x8cbffffd001`60b567c0 fffff801`002293d5 : ffff0000`00000592 ffffd001`60b56ab8 ffffe000`64936590 ffffe000`6492da01 : tcpip!InetInspectReceiveDatagram+0x281ffffd001`60b56900 fffff801`00228f8a : 00000000`00000000 ffffe000`b3f5ab40 00000000`00000000 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x75ffffd001`60b56ab0 fffff801`002286b1 : ffffe000`65a2c040 ffffe000`00000000 ffffd001`00000001 ffffd001`60b56ce0 : tcpip!UdpDeliverDatagrams+0xfaffffd001`60b56c50 fffff801`0024e27e : ffffe000`5020c741 ffffe000`648b9301 ffffe000`64868de0 ffffe000`6b22e1d0 : tcpip!UdpReceiveDatagrams+0x261ffffd001`60b56ff0 fffff801`00272b21 : ffffe000`64a26120 00000000`00000000 ffffff02`00000011 ffffe000`00000506 : tcpip!IpFlcReceivePreValidatedPackets+0x88effffd001`60b571b0 fffff800`ba88b1f5 : 00000000`00000002 00000000`00000000 ffffe000`5f995040 fffff801`002729d0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x151ffffd001`60b572e0 fffff801`00263cf6 : ffffe000`5fb17df0 00000000`00000000 ffffe000`5fb18080 ffffe000`6378e700 : nt!KeExpandKernelStackAndCalloutInternal+0x85ffffd001`60b57330 fffff800`ffec95d3 : 00000000`00000000 ffffd001`60b57430 ffffe000`00000003 fffff800`ffeccf67 : tcpip!FlReceiveNetBufferListChain+0xb6ffffd001`60b573b0 fffff800`ffec930d : 00000000`00000001 ffffe000`647d0000 00000000`00000000 fffff801`00000003 : ndis!ndisMIndicateNetBufferListsToOpen+0x133ffffd001`60b57470 fffff800`ffeccc33 : ffffe000`6472a1a0 ffffd001`00000000 fffff800`ffec90e0 fffff800`bab75780 : ndis!ndisMTopReceiveNetBufferLists+0x22dffffd001`60b57570 fffff800`ffec2929 : ffffe000`6472a102 ffffd001`60b576c0 00000000`00000801 00000000`00000000 : ndis!ndisCallReceiveHandler+0x43ffffd001`60b575c0 fffff801`04245422 : ffffe000`6378e760 ffffe000`6494e030 ffffe000`639dae80 ffffe000`64868be0 : ndis!NdisMIndicateReceiveNetBufferLists+0x479ffffd001`60b57730 ffffe000`6378e760 : ffffe000`6494e030 ffffe000`639dae80 ffffe000`64868be0 00000000`00000801 : e1d65x64+0x15422ffffd001`60b57738 ffffe000`6494e030 : ffffe000`639dae80 ffffe000`64868be0 00000000`00000801 ffffd001`60b57978 : 0xffffe000`6378e760ffffd001`60b57740 ffffe000`639dae80 : ffffe000`64868be0 00000000`00000801 ffffd001`60b57978 ffffe000`6378e760 : 0xffffe000`6494e030ffffd001`60b57748 ffffe000`64868be0 : 00000000`00000801 ffffd001`60b57978 ffffe000`6378e760 ffffe000`64868c70 : 0xffffe000`639dae80ffffd001`60b57750 00000000`00000801 : ffffd001`60b57978 ffffe000`6378e760 ffffe000`64868c70 00000000`00000000 : 0xffffe000`64868be0ffffd001`60b57758 ffffd001`60b57978 : ffffe000`6378e760 ffffe000`64868c70 00000000`00000000 ffffd001`60b57978 : 0x801ffffd001`60b57760 ffffe000`6378e760 : ffffe000`64868c70 00000000`00000000 ffffd001`60b57978 ffffe000`639da000 : 0xffffd001`60b57978ffffd001`60b57768 ffffe000`64868c70 : 00000000`00000000 ffffd001`60b57978 ffffe000`639da000 fffff801`04246705 : 0xffffe000`6378e760ffffd001`60b57770 00000000`00000000 : ffffd001`60b57978 ffffe000`639da000 fffff801`04246705 ffffe000`64868c00 : 0xffffe000`64868c70STACK_COMMAND:  kbFOLLOWUP_IP: NETIO!KfdClassify2+111fffff801`004e1fd1 448b402c        mov     r8d,dword ptr [rax+2Ch]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  NETIO!KfdClassify2+111FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: NETIOIMAGE_NAME:  NETIO.SYSDEBUG_FLR_IMAGE_TIMESTAMP:  559f3890IMAGE_VERSION:  10.0.10240.16384BUCKET_ID_FUNC_OFFSET:  111FAILURE_BUCKET_ID:  AV_NETIO!KfdClassify2BUCKET_ID:  AV_NETIO!KfdClassify2ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:av_netio!kfdclassify2FAILURE_ID_HASH:  {d028e81d-b709-5bf5-8b2a-0b362a9b15d1}Followup: MachineOwner---------0: kd> lmvm NETIOstart             end                 module namefffff801`004d0000 fffff801`00546000   NETIO      (pdb symbols)          c:\symbols\netio.pdb\83A43DFAD7724A6E8C2E4B003B6E492D1\netio.pdb    Loaded symbol image file: NETIO.SYS    Mapped memory image file: c:\symbols\NETIO.SYS\559F389076000\NETIO.SYS    Image path: \SystemRoot\system32\drivers\NETIO.SYS    Image name: NETIO.SYS    Timestamp:        Thu Jul 09 20:14:24 2015 (559F3890)    CheckSum:         00075780    ImageSize:        00076000    File version:     10.0.10240.16384    Product version:  10.0.10240.16384    File flags:       0 (Mask 3F)    File OS:          40004 NT Win32    File type:        3.6 Driver    File date:        00000000.00000000    Translations:     0409.04b0    CompanyName:      Microsoft Corporation    ProductName:      Microsoft® Windows® Operating System    InternalName:     netio.sys    OriginalFilename: netio.sys    ProductVersion:   10.0.10240.16384    FileVersion:      10.0.10240.16384 (th1.150709-1700)    FileDescription:  Network I/O Subsystem    LegalCopyright:   © Microsoft Corporation. All rights reserved. 

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Downloads\Documents1\SysnativeFileCollectionApp\082615-9546-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff803`c3806000 PsLoadedModuleList = 0xfffff803`c3b2b030Debug session time: Wed Aug 26 02:01:54.038 2015 (UTC - 7:00)System Uptime: 0 days 8:30:31.659Loading Kernel Symbols.................................................................................................................................................................................Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 139, {3, ffffd0002287c560, ffffd0002287c4b8, 0}Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )Followup: MachineOwner---------2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE (139)A kernel component has corrupted a critical data structure.  The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).Arg2: ffffd0002287c560, Address of the trap frame for the exception that caused the bugcheckArg3: ffffd0002287c4b8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------TRAP_FRAME:  ffffd0002287c560 -- (.trap 0xffffd0002287c560)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=fffff803c3b6f730 rbx=0000000000000000 rcx=0000000000000003rdx=ffffe001105de158 rsi=0000000000000000 rdi=0000000000000000rip=fffff803c397e9b7 rsp=ffffd0002287c6f0 rbp=0000000000000001 r8=fffff803c3b6f730  r9=ffffe001105de158 r10=0000000000000000r11=0000000000000001 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz ac pe cynt! ?? ::FNODOBFM::`string'+0x1c0b7:fffff803`c397e9b7 cd29            int     29hResetting default scopeEXCEPTION_RECORD:  ffffd0002287c4b8 -- (.exr 0xffffd0002287c4b8)ExceptionAddress: fffff803c397e9b7 (nt! ?? ::FNODOBFM::`string'+0x000000000001c0b7)   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)  ExceptionFlags: 00000001NumberParameters: 1   Parameter[0]: 0000000000000003CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPTBUGCHECK_STR:  0x139PROCESS_NAME:  NvStreamNetworCURRENT_IRQL:  2ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_PARAMETER1:  0000000000000003ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freEXCEPTION_STR:  0x0LAST_CONTROL_TRANSFER:  from fffff803c395e6a9 to fffff803c3953d00STACK_TEXT:  ffffd000`2287c238 fffff803`c395e6a9 : 00000000`00000139 00000000`00000003 ffffd000`2287c560 ffffd000`2287c4b8 : nt!KeBugCheckExffffd000`2287c240 fffff803`c395e9d0 : 00000004`bdde6b92 fffff803`c3b69180 00000000`00000000 fffff803`c380ecaf : nt!KiBugCheckDispatch+0x69ffffd000`2287c380 fffff803`c395dbf4 : 149dfc97`01bf8651 fffff803`c3846e0f ffffe001`54ff9580 ffffe001`54ff9580 : nt!KiFastFailDispatch+0xd0ffffd000`2287c560 fffff803`c397e9b7 : 00000000`00000000 fffff803`c3c341bb 00000000`00000000 ffffd000`2287ca80 : nt!KiRaiseSecurityCheckFailure+0xf4ffffd000`2287c6f0 fffff803`c384b700 : 00000020`0000000a 00000000`ffffffff ffffd000`339db180 fffff803`00000020 : nt! ?? ::FNODOBFM::`string'+0x1c0b7ffffd000`2287c750 fffff803`c384b059 : ffffe001`103cd080 00000000`00000000 00000088`423cebd0 00000088`423cebb8 : nt!KiSearchForNewThread+0x30ffffd000`2287c7a0 fffff803`c384aae8 : ffffe001`103cd080 fffff803`c3b6c780 00000000`00000000 fffff803`c380ecaf : nt!KiSwapThread+0xe9ffffd000`2287c850 fffff803`c384cd35 : 7fffffff`ffffffff 00000000`00000000 00000000`000000d8 00000000`00000001 : nt!KiCommitThreadWait+0x148ffffd000`2287c8e0 fffff803`c3c28512 : ffffe001`103d6da0 00000000`00000006 00000000`00000001 fffff803`c3958701 : nt!KeWaitForSingleObject+0x385ffffd000`2287c990 fffff803`c395e363 : ffffe001`103cd080 00000088`41557980 ffffd000`2287c9d8 ffffe001`103d6da0 : nt!NtWaitForSingleObject+0xf2ffffd000`2287ca00 00007ffd`3f9a353a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000088`423cea38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`3f9a353aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiFastFailDispatch+d0fffff803`c395e9d0 c644242000      mov     byte ptr [rsp+20h],0SYMBOL_STACK_INDEX:  2SYMBOL_NAME:  nt!KiFastFailDispatch+d0FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6IMAGE_VERSION:  10.0.10240.16431BUCKET_ID_FUNC_OFFSET:  d0FAILURE_BUCKET_ID:  0x139_3_nt!KiFastFailDispatchBUCKET_ID:  0x139_3_nt!KiFastFailDispatchANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x139_3_nt!kifastfaildispatchFAILURE_ID_HASH:  {36173680-6f08-995f-065a-3d368c996911}Followup: MachineOwner--------- 

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Downloads\Documents1\SysnativeFileCollectionApp\082715-7984-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 10240 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 10240.16431.amd64fre.th1.150810-2333Machine Name:Kernel base = 0xfffff803`3808f000 PsLoadedModuleList = 0xfffff803`383b4030Debug session time: Wed Aug 26 23:26:24.706 2015 (UTC - 7:00)System Uptime: 0 days 0:00:14.328Loading Kernel Symbols..............................................................................................................................................................................Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 7A, {1, ffffffffc0000005, ffffe001db5f1840, fffff6bffaee1000}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+27097 )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************KERNEL_DATA_INPAGE_ERROR (7a)The requested page of kernel data could not be read in.  Typically caused bya bad block in the paging file or disk controller error. Also seeKERNEL_STACK_INPAGE_ERROR.If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,it means the disk subsystem has experienced a failure.If the error status is 0xC000009A, then it means the request failed becausea filesystem failed to make forward progress.Arguments:Arg1: 0000000000000001, lock type that was held (value 1,2,3, or PTE address)Arg2: ffffffffc0000005, error status (normally i/o status code)Arg3: ffffe001db5f1840, current process (virtual address for lock type 3, or PTE)Arg4: fffff6bffaee1000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)Debugging Details:------------------ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.BUGCHECK_STR:  0x7a_c0000005CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  conhost.exeCURRENT_IRQL:  0ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff80338212997 to fffff803381dcd00STACK_TEXT:  ffffd000`23193138 fffff803`38212997 : 00000000`0000007a 00000000`00000001 ffffffff`c0000005 ffffe001`db5f1840 : nt!KeBugCheckExffffd000`23193140 fffff803`380f26aa : fffff6fb`5ffd7708 fffff6be`faffa000 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x27097ffffd000`231931a0 fffff803`380e3f6e : fffff6bf`faff9ff8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextPageTable+0x21affffd000`23193250 fffff803`380bbdf0 : ffffe001`d938cd80 ffffd000`23193519 ffffe001`db5f1d38 ffffe001`db5b3eb0 : nt!MiDeleteVirtualAddresses+0x12effffd000`23193450 fffff803`38550cb7 : ffffe001`db5b3eb0 ffffe001`db5b3eb0 ffffe001`db74e840 ffffe001`db5f1840 : nt!MiDeleteVad+0x4b0ffffd000`23193580 fffff803`38550a13 : 00000000`00040000 ffffd000`23193818 00000000`00000000 ffffe001`db5f1840 : nt!MmCleanProcessAddressSpace+0xefffffd000`231935e0 fffff803`3854961b : ffffe001`db5f1840 ffffc000`d16769b0 ffffd000`23193818 00000000`00000000 : nt!PspRundownSingleProcess+0x12bffffd000`23193670 fffff803`385ad318 : ffffe001`00000000 ffffd000`23193a01 00007ff7`68b0c000 ffffe001`db5f1840 : nt!PspExitThread+0x5fbffffd000`23193770 fffff803`385ad2ff : 00000000`00000000 ffffd000`23193a01 00000000`00000101 ffffe001`db5e6da0 : nt!PsExitCurrentUserThread+0x18ffffd000`231937a0 fffff803`380d0712 : 00000000`00000000 00000000`00000010 ffffe001`db5e6e18 ffffe001`db5e6e30 : nt!KiSchedulerApcTerminate+0x1fffffd000`231937d0 fffff803`381e0030 : 00000012`dfd86a40 ffffd000`23193850 fffff803`3813bc98 00000000`00000000 : nt!KiDeliverApc+0x2f2ffffd000`23193850 fffff803`381e740a : 00000000`7ffe03b0 00000000`00000000 00000000`00000000 fffff803`384ba4ac : nt!KiInitiateUserApc+0x70ffffd000`23193990 00007ffd`c457505a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f00000012`dff7fb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`c457505aSTACK_COMMAND:  kbFOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+27097fffff803`38212997 cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+27097FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  55c9bcb6IMAGE_VERSION:  10.0.10240.16431BUCKET_ID_FUNC_OFFSET:  27097FAILURE_BUCKET_ID:  0x7a_c0000005_nt!_??_::FNODOBFM::_string_BUCKET_ID:  0x7a_c0000005_nt!_??_::FNODOBFM::_string_ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x7a_c0000005_nt!_??_::fnodobfm::_string_FAILURE_ID_HASH:  {4c5ebb2c-9f68-2f7e-2390-a60667b5bd6f}Followup: MachineOwner