Windows 10: Intel Nuc BSOD multiple errors (Now with Dump file)

Hi All

I purchased a new NUC6i3SYK last week. I have installed a 250gb Samsung evo 850 M.2 HD and 1 8gb stick of Corsair PC4-17000 DDR4 Ram.

Windows 10 is a fresh purchase and install downloaded direct from MS.

The Nuc worked fine with both the HD and Ram being recognised and W10 installed fine. I loaded the drivers from the Nuc support page and then updated Windows. Everything still fine. Then I proceeded to install other programs and went to bed.

Next morning the PC had crashed and failed to restart.

After searching the net for possible cause I decided to reinstall Windows 10. This time i didn't load any drivers and the PC was NOT able to connect to the Internet because I thought one of the updates may have cased the crash.

PC was still unstable and crashed often to the point it was in a BSOD loop.

I then reinstalled Windows 10 again and this time I installed the LAN driver only and Windows 10 updated itself.

It stayed on for 12 hours and has now gone into a BSOD loop again.

The BSOD error message changes but the main ones seem to be

Memory_Management
irql_not_less_or_equal
0xc000021a

Throughout this process I have:
Run Memtest86 for approx 20hrs with no errors
Performed a disk check
Installed samsung magician to confirm HD firmware is the current version
Updated the BIOS to current version

Any help would be appreciated

:)

 

BSOD Windows 10 ntoskrnl..exe

I turned on verifier this caused multiple crashes before I had a successful boot. received multiple screens for "preparing automatic repair and diagnosing your pc" I did run memtest for 10 hours with no issues found.

Last lockup did not produce a dump file. One item worth noting after reboot and system trying to repair nortons reported errors 3039 and 65559

Next bsod I will try and upload a dump file.

 

BSOD at random intervals, Windows 10 errors and can display BAD_POOL_HEADER or MEM_MANAGEMENT before restarting

Windows 10 Pro x64

OS Build 10586.494

Intel Core i5-6500 CPU

When using my PC it can crash to a BSOD out of no where, I can either get BAD_POOL_HEADER as an error or MEM_MANAGEMENT. I have run Driver Verifier multiple times and have generated a .DMP file, I did manage to remove one of the drivers that was effecting
my system (Avast! driver (aswVmm.sys)) which was causing BSOD with the error of the driver name, now that I have done that, I only receive DRIVER_VERIFIER_EXCEPTION_VIOLATION when I run Driver Verifier.

The dump file can be downloaded from my OneDrive folder Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

If anyone could debug this and help me out it would be a great help!!

Any questions welcome

Thanks

 

I can't get it to stay on for more than 30 seconds.

Is there any other way to get the dump files etc that you need.

 

The system went into a BSOD loop.

It took 2 attempts to boot from the recovery disk.

I have just done another fresh install (deleted partitions, formatted the drive and re-installed windows)

It currently running updates so I will post the dump files as soon as it crashes again

 

Well it crashed again

Here is the dump file.

I really would love some help with this as currently have a $600 lemon that I cant use.

Thanks

Attachment 59728

 

The dumpfiles ia bugcheck 1 A
Code: [******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {31, ffffe001b7798a60, ffffd0002170e000, ffffc0001c76a18a} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000031, The subtype of the bugcheck. Arg2: ffffe001b7798a60 Arg3: ffffd0002170e000 Arg4: ffffc0001c76a18a Debugging Details: ------------------ BUGCHECK_STR: 0x1a_31 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: systeminfo.exe[/quote] Usual causes: Device driver, memory, kernel



In your loaded driverlist i found this old driver
ITEhidCIR Tue Jul 16 15:04:14 2013
Driver Description: ITE Consumer IR Driver for EC CIR (PMC) device
Driver Update Site: http://www.ite.com.tw/EN/index.aspx
download from supportpage a new windows 10 driver https://downloadcenter.intel.com/pro...-Kit-NUC6i5SYH
Check if there are more new windows 10 drivers versions

 

Hi Lietec

The PC is currently running Memtest86. It's been on for approx 6hrs and has done 4 passes with no errors. As soon as it gets past 8 I will stop it and update the driver you have suggested.

Thank you

 

Hi Lifetec

I finished the Memtest86 with 12 passes and no errors
I updated the driver you pointed out from the Intel Nuc site

I haven't installed any new programs since the log file was sent but I did use internet explorer

It ran fine for about 6 hours and has gone back into a BSOD loop
The errors are changing every time it tries to boot

Page fault in non page area
0xc000021a
Memory management
Irql not less or equal
system thread exception not handled(ACPI.sys)
Bad pool calls

I can't get it to boot long enough to collect the dump file

do you have any suggestions

 

Hi again Lifetec

I was able to start the PC in safe mode and get the dump files.

I hope this helps

 

Dumpfiles are again
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41792, fffff6bffeae99f0, 800000000000, 0} Probably caused by : memory_corruption ( ONE_BIT ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: fffff6bffeae99f0 Arg3: 0000800000000000 Arg4: 0000000000000000 Debugging Details: ------------------ MEMORY_CORRUPTOR: ONE_BIT BUGCHECK_STR: 0x1a_41792 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: consent.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre STACK_TEXT: ffffd000`219ba598 fffff800`a47f9e39 : 00000000`0000001a 00000000`00041792 fffff6bf`feae99f0 00008000`00000000 : nt!KeBugCheckEx ffffd000`219ba5a0 fffff800`a46bd09a : 00007ffd`01401903 fffff800`a4711696 00000000`00000001 00000000`00001064 : nt! ?? ::FNODOBFM::`string'+0x1ed39 ffffd000`219ba7a0 fffff800`a4a5713b : 00000000`00383000 ffffe000`a1ff1860 ffffe000`a1857470 00007ffd`5d150000 : nt!MiDeleteVad+0x4da ffffd000`219ba8e0 fffff800`a4a56bc7 : 000000ae`95e7f000 00007ffd`00000008 ffffe000`9b228290 00007ffd`5d150000 : nt!MiUnmapViewOfSection+0xeb ffffd000`219ba9b0 fffff800`a47d6fa3 : ffffe000`a20e3840 00000000`00000000 ffffe000`a20e3840 ffffe000`a1eb7840 : nt!NtUnmapViewOfSectionEx+0x77 ffffd000`219baa00 00007ffd`679e5324 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 000000ae`95e7f0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`679e5324 STACK_COMMAND: kb SYMBOL_NAME: ONE_BIT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7} Followup: MachineOwner ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {31, ffffe001b7798a60, ffffd0002170e000, ffffc0001c76a18a} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000031, The subtype of the bugcheck. Arg2: ffffe001b7798a60 Arg3: ffffd0002170e000 Arg4: ffffc0001c76a18a Debugging Details: ------------------ BUGCHECK_STR: 0x1a_31 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: systeminfo.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre LAST_CONTROL_TRANSFER: from fffff803e35edc23 to fffff803e31cc770 STACK_TEXT: ffffd000`2275f218 fffff803`e35edc23 : 00000000`0000001a 00000000`00000031 ffffe001`b7798a60 ffffd000`2170e000 : nt!KeBugCheckEx ffffd000`2275f220 fffff803`e34549c0 : ffffc000`1c76a0e4 00000000`0005b000 ffffd000`2170e000 00000000`0019288e : nt! ?? ::NNGAKEGL::`string'+0xd3d3 ffffd000`2275f280 fffff803`e345485e : ffffc000`1c767000 fffff6e8`0010ad70 ffffd000`2170e000 fffff803`e33873c0 : nt!MiPerformFixups+0x70 ffffd000`2275f2e0 fffff803`e30b2ed6 : 00000000`00000000 00000000`00000000 00000000`00000008 40000000`00000000 : nt!MiRelocateImagePfn+0x13e ffffd000`2275f350 fffff803`e34cbc15 : ffffe001`b7798a60 fffff6e8`0010ad70 00000000`00000002 fffff6e8`00000001 : nt!MiValidateImagePages+0x886 ffffd000`2275f4a0 fffff803`e34cb670 : ffffe001`b7798a60 fffff6e8`0010ad70 00000000`00000000 00000000`00000040 : nt!MiSwitchBaseAddress+0x69 ffffd000`2275f4d0 fffff803`e3461e1f : 00000000`6fad0000 00000000`00000000 00000000`6f9f0000 ffffe001`b7230040 : nt!MiRelocateImageAgain+0x1a0 ffffd000`2275f560 fffff803`e3461579 : ffffd000`2275f7b0 ffffd000`2275f870 ffffd000`2275f960 ffffd000`2275f7a8 : nt!MiCreateSection+0x78f ffffd000`2275f740 fffff803`e34c48b9 : ffffc000`2c932c10 ffffc000`174f8630 00000000`00000001 00000002`00000000 : nt!NtCreateSection+0x1c9 ffffd000`2275f7e0 fffff803`e34c43fa : 00000000`00000000 00000000`000001f0 00000000`0000006c fffff803`000000e8 : nt!PfSnGetSectionObject+0x23d ffffd000`2275f910 fffff803`e30f4b79 : fffff803`e341d200 ffffe001`b7230040 ffffe001`b6932a60 fffff803`e341d340 : nt!PfSnPopulateReadList+0x2aa ffffd000`2275fa80 fffff803`e3093125 : ffffe001`b7230040 00000000`00000080 ffffe001`b2427700 ffffe001`b7230040 : nt!ExpWorkerThread+0xe9 ffffd000`2275fb10 fffff803`e31d1916 : fffff803`e33a7180 ffffe001`b7230040 fffff803`e30930e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`2275fb60 00000000`00000000 : ffffd000`22760000 ffffd000`22759000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff803e30f4b43 - nt!ExpWorkerThread+b3 [ 02:00 ] fffff803e31cc80d - nt!KeBugCheckEx+9d (+0xd7cca) [ 0f:0d ] fffff803e352c480 - nt!PfSnAsyncPrefetchWorker+bc [ 0f:0e ] fffff803e36ba576 - nt!PfpPrefetchSharedConflictNotifyStart+16 (+0x18e0f6) [ f0:b0 ] 4 errors : !nt (fffff803e30f4b43-fffff803e36ba576) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT_LARGE FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT_LARGE BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT_LARGE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit_large FAILURE_ID_HASH: {31545515-196b-fab5-2300-9ce714226f43} Followup: memory_corruption ---------[/quote] The dumpfiles keep blaming your memory even with a mention of Hardware, although you have done Memtest 86 with no errors.
Was the memorymodule preinstalled with your NUC or did you later buy it (is it compatible)
Could you check in your Bios if the memory module is running with the good settings (voltage, CL etc.)

Do you have any red or yellow exclamationmarks in your Device Manager.
Because in your Msinfo32. i found this under Problem devices:
Consumer IR Devices ROOT\SYSTEM\0001 This device is not working properly because Windows cannot load the drivers required for this device.
Intel(R) Serial IO UART Host Controller - 9D27 PCI\VEN_8086&DEV_9D27&SUBSYS_20638086&REV_21\3&11583659&0&F0 37

Could you check if your current driver versions are the latest versions and/or (re)install all the 16 windows 10 drivers from the supportpage https://downloadcenter.intel.com/pro...-Kit-NUC6i5SYH

 

Now that the system is in safe mode it has stayed on all night (approx 10hrs)

The Ram and hard drive were purchased at the same time as the Nuc but they were NOT a package and NOT pre installed.

I have attached a screen shot of the device manager page showing the errors
Attachment 59947

This is the driver I installed for the ITE consumer IR
Attachment 59948

 

Firstly i would like to thank Lifetec for the help!!!!!!!!

Despite my RAM being on the approved list from INTEL http://www.intel.com/content/www/us/...000016245.html it apears that there is a issue with this particular memery and 6th Gen NUC's.

I found this thread on the Intel forum NUC6i3SYH Random freezes |Intel Communities with others using the same ram as i did having the exact same problem as i did.

i bought 2 sticks of the Kingston ram recommended in the post and the NUC has been running perfect ever since

Now i wonder if i can get Intel to reimburse me for the Corsair ram that doesn't work as i bought it on there recommendation.

Once again Lifetec thanks for the help

 

Thanks for the follow up.