Custom i7-5960x/Windows 10 freezing - PLEASE HELP!

[BrockJon]

Hello,

I'm hoping someone can help me here. A friend built me a system for music and video production. In short, the system freezes once I get into Windows (and occasionally during bootup) - sometimes right when I get to the desktop, other times after longer usage periods (up to hours). What's strange is it runs without any problems in Safe Mode (w/ networking).

These are the components (all software and drivers are current):

* i7-5960x 8 core (OC'd to 4.4GHz) (with be quiet! Dark ROck 3 CPU cooler)
* ASRock X99 OC Formula/3.1
* 64GB Corsair Dominator Platinum DDR 4 2800 (OC'd to 3000)
* Asus GTX980ti Strix
* Samsung m.2 950 512GB (for Windows 10/software)
* 2x Samsung 850 1TB in RAID0
* 2x WD Black 5TB in RAID0
* ASRock Thunderbolt 2 AIC-Expresss Card
* Sonnet Technologies Allegro FW card
* be quiet! Dark Power Pro 11 power supply
* Corsair 600Q case
* UA Thunderbolt Apollo QUAD
* Windows 10 Pro (64-bit)

To troubleshoot, I've removed the TB and FW cards and uninstalled their drivers, gone down to a single stick of RAM (which I also swapped with another stick) with no USB devices hooked up and it still freezes. I've reset the W10 install and refreshed it. I also reset the CPU and RAM to their standard settings in the BIOS. None of this has made any difference.

All temperatures are well below any level of concern (mid 40s and lower). I used Intel's processor checker software and run the CPU stress test and the CPU checked out fine.

I have gotten a few BSoDs (WHEA_UNCORRECTABLE_ERROR), but usually the cursor just freezes on the screen during use within Windows.

I'm inclined to think it's either:
* a faulty mobo (but why would the computer run fine in Safe Mode?)
* a bad sector on the m.2 drive (seems very unlikely to me)
* a bad power supply (seems very unlikely to me)
* a Windows 10 issue (I've basically reinstalled it twice and it still freezes when no other software is installed)

I use this computer for work and am hamstrung until I can get it working (consistently) again. I appreciate your help!

Thanks,
Brock

(I also posted this in the Systems forum as I'm not sure which is most appropriate.)

 

[Colif]

try running this and see what those whea errors have to say: http://www.resplendence.com/whocrashed
run a scan and post it here if the cause isn't obvious - it usually isn't

only way to know win 10 hasn't got any other software installed after fresh install is not have wifi and not have Ethernet attached as it will grab drivers within first 20 minutes of install, mainly hardware drivers. Which are usually the cause.

Anyway, I wait for report

 

[BrockJon]

try running this and see what those whea errors have to say: http://www.resplendence.com/whocrashed
run a scan and post it here if the cause isn't obvious - it usually isn't

only way to know win 10 hasn't got any other software installed after fresh install is not have wifi and not have Ethernet attached as it will grab drivers within first 20 minutes of install, mainly hardware drivers. Which are usually the cause.

Anyway, I wait for report

Hi Colif,

Thanks for your reply. I DLed the program. So far, this is what's it's reporting:

Crash dumps are enabled but no valid crash dumps have been found. In case you are experiencing system crashes, it may be that crash dumps are prevented from being written out. Check out the following article for possible causes: If crash dumps are not written out.


Do I need to wait for the system to crash again before it has anything to work with? When the computer's frozen, I'd had to hard power it off, so I'm not sure anything reports are actually being generated (then again, I don't know).

Please let me know.

Thanks!
Brock

 

[Colif]

Have you formatted pc since the Whea errors?

The 0x0000124 is a hardware error that indicates that your system has found an uncorrectable hardware error. It’s also known as WHEA_UNCORRECTABLE_ERROR

The most common cause is the CPU voltage being too low, but here are some other common causes for this error:

corrupt hardware: damaged hard disk, video card problem, RAM corruption, problems with the processor
driver compatibility issues (this especially happens for Windows 8.1 systems)
driver conflict
heat related problems, e.g. overclocking the system
a corrupt Windows registry
corrupt or removed Windows-specific system files

https://neosmart.net/wiki/0x0000124-whea-uncorrectable-error/

freezes don't let windows write error logs as its frozen. I think freezes are normally hardware based so the other thread may help you more than I can.

One other thing before someone else beats me... you should not be overclocked when installing windows 10. It is better to be stock clock on ram and CPU when installing as it can lead to errors like this and other bsod - not saying its the cause but it could be,

One thing you can do is look in Event viewer and see if there are any errors leading up to the crash.

 

[The_Prophecy]

If WhoCrashed doesn't provide any info, you can also check the Event Viewer in Windows, or use a program called BlueScreenView from NirSoft.

BlueScreenView: http://www.nirsoft.net/utils/blue_screen_view.html

Edit: Colif also makes a good point. Remove the overclocks on the CPU and RAM.

Doesn't matter if they are OC'ed while installing WIndows, but if it starts crashing during day to day operations, then they should both be reverted to stock clocks and slowly ramped back up once stable operation is achieved.

 

[BrockJon]

If WhoCrashed doesn't provide any info, you can also check the Event Viewer in Windows, or use a program called BlueScreenView from NirSoft.

BlueScreenView: http://www.nirsoft.net/utils/blue_screen_view.html

Edit: Colif also makes a good point. Remove the overclocks on the CPU and RAM.
Doesn't matter if they are OC'ed while installing WIndows, but if it starts crashing during day to day operations, then they should both be reverted to stock clocks and slowly ramped back up once stable operation is achieved.

Thank you for your reply.

Right now it's not showing any dumps. Also, RE: the OCing, the system was still freezing with the CPU and RAM set to stock speeds in the BIOS. There was no difference in that regard at all.

 

[BrockJon]

Have you formatted pc since the Whea errors?

The 0x0000124 is a hardware error that indicates that your system has found an uncorrectable hardware error. It’s also known as WHEA_UNCORRECTABLE_ERROR

The most common cause is the CPU voltage being too low, but here are some other common causes for this error:

corrupt hardware: damaged hard disk, video card problem, RAM corruption, problems with the processor
driver compatibility issues (this especially happens for Windows 8.1 systems)
driver conflict
heat related problems, e.g. overclocking the system
a corrupt Windows registry
corrupt or removed Windows-specific system files

https://neosmart.net/wiki/0x0000124-whea-uncorrectable-error/

freezes don't let windows write error logs as its frozen. I think freezes are normally hardware based so the other thread may help you more than I can.

One other thing before someone else beats me... you should not be overclocked when installing windows 10. It is better to be stock clock on ram and CPU when installing as it can lead to errors like this and other bsod - not saying its the cause but it could be,

One thing you can do is look in Event viewer and see if there are any errors leading up to the crash.

I can reinstall with W10 at stock settings. Would a reset be sufficient?

 

[Colif]

I would think so, it puts a fresh win 10 on, and lets you save files.

 

[BrockJon]

Finally got a crash dump Here's the WhoCrashed version:

On Sun 4/17/2016 6:55:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041716-10625-01.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE001BBE8C028, 0xBE200000, 0xC110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 4/17/2016 6:55:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE001BBE8C028, 0xBE200000, 0xC110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



And here's the full version:
hal.dll hal.dll+35f1f fffff803`d7be7000 fffff803`d7c5a000 0x00073000 0x5632d17a 10/29/2015 6:10:02 PM
ntoskrnl.exe ntoskrnl.exe+21073c fffff803`d741b000 fffff803`d7be7000 0x007cc000 0x56fa1e56 3/28/2016 10:19:02 PM
kd.dll fffff803`d6067000 fffff803`d6072000 0x0000b000 0x00000000
mcupdate_GenuineIntel.dll fffff801`10680000 fffff801`1070e000 0x0008e000 0x00000000
werkernel.sys fffff801`10710000 fffff801`10720000 0x00010000 0x00000000
CLFS.SYS fffff801`10720000 fffff801`10785000 0x00065000 0x00000000
tm.sys fffff801`10790000 fffff801`107b5000 0x00025000 0x00000000
PSHED.dll fffff801`107c0000 fffff801`107d7000 0x00017000 0x00000000 Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 10.0.10586.0 (th2_release.151029-1700) Microsoft Corporation C:\WINDOWS\system32\PSHED.dll
BOOTVID.dll fffff801`107e0000 fffff801`107eb000 0x0000b000 0x00000000 Microsoft® Windows® Operating System VGA Boot Driver 10.0.10586.0 (th2_release.151029-1700) Microsoft Corporation C:\WINDOWS\system32\BOOTVID.dll
cmimcext.sys fffff801`107f0000 fffff801`107fe000 0x0000e000 0x00000000
ntosext.sys fffff801`10600000 fffff801`1060c000 0x0000c000 0x00000000
CI.dll fffff801`115f0000 fffff801`11689000 0x00099000 0x00000000
msrpc.sys fffff801`11690000 fffff801`116ec000 0x0005c000 0x5632d746 10/29/2015 6:34:46 PM
FLTMGR.SYS fffff801`116f0000 fffff801`11752000 0x00062000 0x00000000
ksecdd.sys fffff801`11760000 fffff801`11785000 0x00025000 0x00000000
clipsp.sys fffff801`10800000 fffff801`108a5000 0x000a5000 0x5632d7db 10/29/2015 6:37:15 PM
Wdf01000.sys fffff801`108b0000 fffff801`10975000 0x000c5000 0x5632d4db 10/29/2015 6:24:27 PM
WDFLDR.SYS fffff801`10980000 fffff801`10993000 0x00013000 0x5632d168 10/29/2015 6:09:44 PM
acpiex.sys fffff801`109a0000 fffff801`109c3000 0x00023000 0x5632d854 10/29/2015 6:39:16 PM
WppRecorder.sys fffff801`109d0000 fffff801`109dd000 0x0000d000 0x5632d166 10/29/2015 6:09:42 PM
cng.sys fffff801`109e0000 fffff801`10a78000 0x00098000 0x56fa2c89 3/28/2016 11:19:37 PM
ACPI.sys fffff801`10a80000 fffff801`10b10000 0x00090000 0x56cbf9c9 2/22/2016 10:18:49 PM
WMILIB.SYS fffff801`10b10000 fffff801`10b1c000 0x0000c000 0x5632d166 10/29/2015 6:09:42 PM
WindowsTrustedRT.sys fffff801`10b30000 fffff801`10b4f000 0x0001f000 0x5632d826 10/29/2015 6:38:30 PM
WindowsTrustedRTProxy.sys fffff801`10b50000 fffff801`10b5b000 0x0000b000 0x5632d825 10/29/2015 6:38:29 PM
pcw.sys fffff801`10b60000 fffff801`10b72000 0x00012000 0x5632d166 10/29/2015 6:09:42 PM
msisadrv.sys fffff801`10b80000 fffff801`10b8b000 0x0000b000 0x5632d8f3 10/29/2015 6:41:55 PM
pci.sys fffff801`10b90000 fffff801`10be6000 0x00056000 0x5632d60a 10/29/2015 6:29:30 PM
vdrvroot.sys fffff801`10bf0000 fffff801`10c02000 0x00012000 0x5632d845 10/29/2015 6:39:01 PM
pdc.sys fffff801`10c10000 fffff801`10c2e000 0x0001e000 0x5632d16f 10/29/2015 6:09:51 PM
CEA.sys fffff801`10c30000 fffff801`10c49000 0x00019000 0x5632d902 10/29/2015 6:42:10 PM
partmgr.sys fffff801`10c50000 fffff801`10c72000 0x00022000 0x5632d170 10/29/2015 6:09:52 PM
spaceport.sys fffff801`10c80000 fffff801`10d06000 0x00086000 0x5632d745 10/29/2015 6:34:45 PM
volmgr.sys fffff801`10d10000 fffff801`10d28000 0x00018000 0x5632d16d 10/29/2015 6:09:49 PM
volmgrx.sys fffff801`10d30000 fffff801`10d8e000 0x0005e000 0x5632d170 10/29/2015 6:09:52 PM
mountmgr.sys fffff801`10d90000 fffff801`10dad000 0x0001d000 0x5632d16c 10/29/2015 6:09:48 PM
nvme.sys fffff801`10db0000 fffff801`10dce000 0x0001e000 0x566a9ad1 12/11/2015 1:43:45 AM
storport.sys fffff801`10dd0000 fffff801`10e48000 0x00078000 0x5632d71d 10/29/2015 6:34:05 PM
iaStorA.sys fffff801`10e50000 fffff801`113c2000 0x00572000 0x556ecb31 6/3/2015 1:38:57 AM
fileinfo.sys fffff801`113f0000 fffff801`11409000 0x00019000 0x5632d7dd 10/29/2015 6:37:17 PM
Wof.sys fffff801`11410000 fffff801`11448000 0x00038000 0x5632d818 10/29/2015 6:38:16 PM
WdFilter.sys fffff801`11450000 fffff801`1149c000 0x0004c000 0x5632d73b 10/29/2015 6:34:35 PM
NTFS.sys fffff801`12580000 fffff801`12798000 0x00218000 0x56fa1d8d 3/28/2016 10:15:41 PM
Fs_Rec.sys fffff801`127a0000 fffff801`127ad000 0x0000d000 0x5632d166 10/29/2015 6:09:42 PM
ndis.sys fffff801`11800000 fffff801`11920000 0x00120000 0x56fa2b6d 3/28/2016 11:14:53 PM
NETIO.SYS fffff801`11920000 fffff801`11998000 0x00078000 0x5632d715 10/29/2015 6:33:57 PM
ksecpkg.sys fffff801`119a0000 fffff801`119ce000 0x0002e000 0x56518feb 11/22/2015 1:50:35 AM
tcpip.sys fffff801`119d0000 fffff801`11c27000 0x00257000 0x56fa29c0 3/28/2016 11:07:44 PM
fwpkclnt.sys fffff801`11c30000 fffff801`11c97000 0x00067000 0x5632d17b 10/29/2015 6:10:03 PM
wfplwfs.sys fffff801`11ca0000 fffff801`11cca000 0x0002a000 0x5632d7b4 10/29/2015 6:36:36 PM
fvevol.sys fffff801`11cd0000 fffff801`11d71000 0x000a1000 0x5632d675 10/29/2015 6:31:17 PM
volsnap.sys fffff801`11d80000 fffff801`11de9000 0x00069000 0x5632d170 10/29/2015 6:09:52 PM
rdyboost.sys fffff801`11df0000 fffff801`11e34000 0x00044000 0x5632d76b 10/29/2015 6:35:23 PM
mup.sys fffff801`11e40000 fffff801`11e65000 0x00025000 0x5632d4db 10/29/2015 6:24:27 PM
disk.sys fffff801`11e80000 fffff801`11e9f000 0x0001f000 0x5632d16e 10/29/2015 6:09:50 PM
CLASSPNP.SYS fffff801`11ea0000 fffff801`11f00000 0x00060000 0x5632d175 10/29/2015 6:09:57 PM
crashdmp.sys fffff801`11f20000 fffff801`11f39000 0x00019000 0x5632d81c 10/29/2015 6:38:20 PM
cdrom.sys fffff801`11fe0000 fffff801`12011000 0x00031000 0x00000000
filecrypt.sys fffff801`12020000 fffff801`1203d000 0x0001d000 0x00000000
tbs.sys fffff801`12040000 fffff801`1204c000 0x0000c000 0x00000000
Null.SYS fffff801`12050000 fffff801`1205a000 0x0000a000 0x5632d166 10/29/2015 6:09:42 PM
Beep.SYS fffff801`12060000 fffff801`1206a000 0x0000a000 0x00000000
BasicDisplay.sys fffff801`12070000 fffff801`12084000 0x00014000 0x5632d89c 10/29/2015 6:40:28 PM
watchdog.sys fffff801`12090000 fffff801`120a5000 0x00015000 0x00000000
dxgkrnl.sys fffff801`120b0000 fffff801`1229d000 0x001ed000 0x56cd47bc 2/23/2016 10:03:40 PM
BasicRender.sys fffff801`122a0000 fffff801`122b2000 0x00012000 0x5632d8e4 10/29/2015 6:41:40 PM
Npfs.SYS fffff801`122c0000 fffff801`122d9000 0x00019000 0x5632d166 10/29/2015 6:09:42 PM
Msfs.SYS fffff801`122e0000 fffff801`122ef000 0x0000f000 0x5632d166 10/29/2015 6:09:42 PM
tdx.sys fffff801`122f0000 fffff801`12313000 0x00023000 0x563b27bd 11/5/2015 1:56:13 AM
TDI.SYS fffff801`12320000 fffff801`1232f000 0x0000f000 0x5632d8ef 10/29/2015 6:41:51 PM
netbt.sys fffff801`12330000 fffff801`1237b000 0x0004b000 0x5632d77c 10/29/2015 6:35:40 PM
afd.sys fffff801`12380000 fffff801`12412000 0x00092000 0x563b2123 11/5/2015 1:28:03 AM
vwififlt.sys fffff801`12420000 fffff801`12439000 0x00019000 0x5632d7e7 10/29/2015 6:37:27 PM
pacer.sys fffff801`12440000 fffff801`1246b000 0x0002b000 0x5632d792 10/29/2015 6:36:02 PM
netbios.sys fffff801`12470000 fffff801`12482000 0x00012000 0x5632d7fa 10/29/2015 6:37:46 PM
rdbss.sys fffff801`12490000 fffff801`12501000 0x00071000 0x5632d527 10/29/2015 6:25:43 PM
csc.sys fffff801`114a0000 fffff801`1152e000 0x0008e000 0x5632d521 10/29/2015 6:25:37 PM
nsiproxy.sys fffff801`12510000 fffff801`12520000 0x00010000 0x5632d808 10/29/2015 6:38:00 PM
npsvctrig.sys fffff801`12520000 fffff801`1252d000 0x0000d000 0x5632d897 10/29/2015 6:40:23 PM
mssmbios.sys fffff801`12530000 fffff801`12540000 0x00010000 0x5632d80f 10/29/2015 6:38:07 PM
gpuenergydrv.sys fffff801`12540000 fffff801`1254a000 0x0000a000 0x5632d87a 10/29/2015 6:39:54 PM
dfsc.sys fffff801`12550000 fffff801`1257a000 0x0002a000 0x56fa28bb 3/28/2016 11:03:23 PM
AsrAppCharger.sys fffff801`127d0000 fffff801`127d7000 0x00007000 0x4dc8f73e 5/10/2011 12:28:46 AM
ahcache.sys fffff801`11530000 fffff801`1156c000 0x0003c000 0x5632d169 10/29/2015 6:09:45 PM
CompositeBus.sys fffff801`127e0000 fffff801`127f1000 0x00011000 0x5632d8e0 10/29/2015 6:41:36 PM
UAD2System.sys fffff801`11570000 fffff801`11598000 0x00028000 0x5595e904 7/2/2015 5:44:36 PM
kdnic.sys fffff801`11e70000 fffff801`11e7d000 0x0000d000 0x5632d8e9 10/29/2015 6:41:45 PM
umbus.sys fffff801`127b0000 fffff801`127c5000 0x00015000 0x5632d7e5 10/29/2015 6:37:25 PM
intelppm.sys fffff801`115a0000 fffff801`115cb000 0x0002b000 0x5632d16f 10/29/2015 6:09:51 PM
wmiacpi.sys fffff801`115d0000 fffff801`115dc000 0x0000c000 0x5632d7d0 10/29/2015 6:37:04 PM
tfl81x.sys fffff801`11790000 fffff801`117a6000 0x00016000 0x52179c82 8/23/2013 9:31:46 AM
UAD2Pcie.sys fffff801`117b0000 fffff801`117c2000 0x00012000 0x5595e904 7/2/2015 5:44:36 PM
1394ohci.sys fffff801`10610000 fffff801`10650000 0x00040000 0x5632d7c7 10/29/2015 6:36:55 PM
nvlddmkm.sys fffff801`141b0000 fffff801`14e01000 0x00c51000 0x56f0a395 3/21/2016 5:44:53 PM
HDAudBus.sys fffff801`14e10000 fffff801`14e2a000 0x0001a000 0x5632d7e1 10/29/2015 6:37:21 PM
portcls.sys fffff801`14e30000 fffff801`14e88000 0x00058000 0x56fa301a 3/28/2016 11:34:50 PM
drmk.sys fffff801`14e90000 fffff801`14eb1000 0x00021000 0x5632d834 10/29/2015 6:38:44 PM
ks.sys fffff801`14ec0000 fffff801`14f28000 0x00068000 0x00000000
USBXHCI.SYS fffff801`14f30000 fffff801`14f91000 0x00061000 0x56fa2ec5 3/28/2016 11:29:09 PM
ucx01000.sys fffff801`14fa0000 fffff801`14fd8000 0x00038000 0x00000000
TeeDriverW8x64.sys fffff801`13800000 fffff801`13830000 0x00030000 0x55e4afb3 8/31/2015 11:49:07 AM
e1d65x64.sys fffff801`13830000 fffff801`138b5000 0x00085000 0x5582f3e4 6/18/2015 8:37:56 AM
usbehci.sys fffff801`138c0000 fffff801`138dc000 0x0001c000 0x5632d578 10/29/2015 6:27:04 PM
USBPORT.SYS fffff801`138e0000 fffff801`13955000 0x00075000 0x5632d586 10/29/2015 6:27:18 PM
L1C63x64.sys fffff801`13960000 fffff801`13982000 0x00022000 0x5158fbc5 3/31/2013 7:15:17 PM
serial.sys fffff801`13990000 fffff801`139ab000 0x0001b000 0x56fa34f1 3/28/2016 11:55:29 PM
serenum.sys fffff801`139b0000 fffff801`139bf000 0x0000f000 0x5632d905 10/29/2015 6:42:13 PM
GEARAspiWDM.sys fffff801`139c0000 fffff801`139c7000 0x00007000 0x00000000
nvvad64v.sys fffff801`139d0000 fffff801`139dd000 0x0000d000 0x00000000
ksthunk.sys fffff801`139e0000 fffff801`139ee000 0x0000e000 0x5632d8f9 10/29/2015 6:42:01 PM
NdisVirtualBus.sys fffff801`139f0000 fffff801`139fd000 0x0000d000 0x5632d822 10/29/2015 6:38:26 PM
swenum.sys fffff801`13a00000 fffff801`13a0c000 0x0000c000 0x5632d90c 10/29/2015 6:42:20 PM
rdpbus.sys fffff801`13a10000 fffff801`13a1e000 0x0000e000 0x5632d187 10/29/2015 6:10:15 PM
usbhub.sys fffff801`13a20000 fffff801`13aa0000 0x00080000 0x5632d660 10/29/2015 6:30:56 PM
USBD.SYS fffff801`13aa0000 fffff801`13aae000 0x0000e000 0x5632d8f2 10/29/2015 6:41:54 PM
UAFWAudio.sys fffff801`13ab0000 fffff801`13ae5000 0x00035000 0x00000000
nvhda64v.sys fffff801`13af0000 fffff801`13b24000 0x00034000 0x00000000
UsbHub3.sys fffff801`13b30000 fffff801`13bb7000 0x00087000 0x00000000
RTKVHD64.sys fffff801`13bc0000 fffff801`14050000 0x00490000 0x55a6330c 7/15/2015 2:16:44 AM
uaspstor.sys fffff801`14050000 fffff801`14068000 0x00018000 0x5632d8e5 10/29/2015 6:41:41 PM
usbccgp.sys fffff801`14070000 fffff801`1409b000 0x0002b000 0x5632d84c 10/29/2015 6:39:08 PM
hidusb.sys fffff801`140a0000 fffff801`140b1000 0x00011000 0x5632d8e8 10/29/2015 6:41:44 PM
HIDCLASS.SYS fffff801`140c0000 fffff801`140ee000 0x0002e000 0x5632d7a9 10/29/2015 6:36:25 PM
HIDPARSE.SYS fffff801`140f0000 fffff801`14101000 0x00011000 0x5632d8a7 10/29/2015 6:40:39 PM
kbdhid.sys fffff801`14110000 fffff801`14120000 0x00010000 0x5632d86e 10/29/2015 6:39:42 PM
kbdclass.sys fffff801`14120000 fffff801`14133000 0x00013000 0x5632d81c 10/29/2015 6:38:20 PM
CMUSBDAC.sys fffff801`15970000 fffff801`15d07000 0x00397000 0x55bb18a2 7/30/2015 10:41:38 PM
mouhid.sys fffff801`15d10000 fffff801`15d1f000 0x0000f000 0x5632d847 10/29/2015 6:39:03 PM
mouclass.sys fffff801`15d20000 fffff801`15d32000 0x00012000 0x5632d805 10/29/2015 6:37:57 PM
iLokDrvr.sys fffff801`15d40000 fffff801`15d4b000 0x0000b000 0x509aafb2 11/7/2012 11:00:02 AM
synusb64.sys fffff801`15d50000 fffff801`15d5b000 0x0000b000 0x4a44cd63 6/26/2009 5:30:11 AM
usbvideo.sys fffff801`15d60000 fffff801`15d9e000 0x0003e000 0x5632d7e7 10/29/2015 6:37:27 PM
usbaudio.sys fffff801`15da0000 fffff801`15dc6000 0x00026000 0x5632d832 10/29/2015 6:38:42 PM
win32k.sys fffff961`d0670000 fffff961`d0693000 0x00023000 0x00000000
win32kfull.sys fffff961`d0000000 fffff961`d0382000 0x00382000 0x00000000
win32kbase.sys fffff961`d0390000 fffff961`d04f1000 0x00161000 0x00000000
dump_diskdump.sys fffff801`15510000 fffff801`1551f000 0x0000f000 0x5632d8fa 10/29/2015 6:42:02 PM
dump_nvme.sys fffff801`15540000 fffff801`1555e000 0x0001e000 0x566a9ad1 12/11/2015 1:43:45 AM
dump_dumpfve.sys fffff801`15580000 fffff801`1559c000 0x0001c000 0x5632d882 10/29/2015 6:40:02 PM
UAFWAudioAudio.sys fffff801`155a0000 fffff801`155b0000 0x00010000 0x513e44dc 3/11/2013 12:55:56 PM

 

[The_Prophecy]

What do your system temps look like? Grab HWMonitor if you don't have it already:

http://www.cpuid.com/softwares/hwmonitor.html

 

[BrockJon]

What do your system temps look like? Grab HWMonitor if you don't have it already:

http://www.cpuid.com/softwares/hwmonitor.html

OC'd (@ 4.4) at idle the temps were in low 40s. In use it was in the mid 40s to 50s. During the Prime95 stress test they quickly soared to 90+ (so I aborted). At standard speeds, the temps were a bit lower, except for the Prime 95 test they were in the mid 60s to low 70s.

 

[BrockJon]

The system passed the memcheck (Windows) and the m.2 passed Disk Check (Windows).

I wanted to do Memtest86 but I can't get it to properly install on a USB 3.0 thumb drive. I run the install (with the option to format the driver to Fat), but it immediately give me an error message saying that the drive won't be bootable and then completes the rest of the process. When I set in BIOS to boot from the USB drive, it ignores it -- so whatever needs to be on there to make it bootable isn't. I even used Diskpart to "clean" the drive and tried reinstalling, but it didn't work.

I think my question at this point is -- is this likely the mobo? If so, why would the computer work 100% fine in Safe Mode?

 

[Colif]

One thing you can try is run driver verifier in safe mode: http://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html

Why? to knock off the chances its one of the drivers currently installed causing this. Since it crashes in live it might be a driver still, its more or less the only difference

WHEA errors can be anything, do you have any USB dongles attached to pc (last WHEA error i did had it caused by these).

 

[BrockJon]

One thing you can try is run driver verifier in safe mode: http://www.tenforums.com/tutorials/5470-driver-verifier-enable-disable-windows-10-a.html

Why? to knock off the chances its one of the drivers currently installed causing this. Since it crashes in live it might be a driver still, its more or less the only difference

WHEA errors can be anything, do you have any USB dongles attached to pc (last WHEA error i did had it caused by these).

Did a clean install of W10 with stock CPU/RAM settings having formatted the disk first and I had nothing connected. It froze almost immediately. I didn't even have a chance to load drivers - it wouldn't stay up that long.

Mobo is headed back to ASRock. We'll see what happens. I'll report back.

 

[The_Prophecy]

If you haven't sent it back yet but it is disassembled, check the CPU socket for bent pins? I've seen that cause all kinds of weird problems. Usually happens by putting too much pressure on the CPU when installing, which sucks because you actually have to use a not-so-insignificant amount of force to close locking lever for the CPU socket once the CPU is in place.

If you've already sent it out, I'll just keep my fingers crossed that the board is indeed the issue.

 

[BrockJon]

No bent pins. I actually did that to a 4,1 Mac Pro. It was awful - and expensive.