Windows 10 BSOD




On Sun 24/04/2016 19:48:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042416-6984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3594F)
Bugcheck code: 0x124 (0x0, 0xFFFFE001D9400028, 0xB6000000, 0x100153)
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.

I can guarantee it was not a Thermal issue, This happens in times when the PC is not stressed and not during times when i is stressed. I have thermal monitoring which idle at about 21C (CPU average across all cores)
 
there was also a strange entry for your hardware:
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_1002&DEV_5A16&SUBSYS_5A141002&REV_00\3&11583659&0&10

I am not sure but the error seems to indicate that the bridge was not getting power and had illegal settings.
the system attempted to access the device 425690576 times.

I am not sure what to do about this, Maybe update to the current bios version, reset the system to defaults, make sure all the devices that could be on the bridge have proper drivers. Make sure any usb device does not pull too much power.

it looks like you have nothing connected to your asmedia hub and you have a via labs usb2.0 hub
all look like they are suspended and nothing connected to them.



-------------
Kingsoft Internet Security Sandbox kernel driver (kisknl.sys) was also making network calls and could have caused this problem.
this is the first time I have seen this driver installed.
-----------
note there was a large amount of pool used by boot tag ArIc this is for the tcp/ip network component and would hint that the problem is related to the killer network driver a root cause of all of the nonpaged pool used. (update the driver)
--------------
all you can do is fix the problems below and see if you can still get the problem.
Note: you can force a memory dump using a keyboard and I can check the memory dump for the problem way before your system crashes normally. google, how to force a memory dump via keyboard to find out how to make the registry settings.
-----------
overall i think your usbcapture device driver has a bug and somehow triggers the bugcheck 0x124 I don't know why the CPU reported the cache error unless it just overheated. I say this only because of the error in the internal logs for the USB port.

It could also be the killer ethernet drivers. I say this because it was actually the only thing running at the time, was out of date and could also be allocating the IRPS. it also sounds like the type of problem their driver bugs introduce.

- update the 4 drivers listed below to see if you can get your capture program to work correctly, or just remove the capture program if you really do not need it.

the debugger is looping in the irps and there are hundreds of thousands of them that are not correctly formated. the irp owner is not set, it just sounds like the type of bug you would get from the usb capture program. (or a bug in the USB driver)



-------------
normally for this problem and the bugcheck I would guess overheating but your internal log for the via USB driver indicates that it was being reset over and over. Then it looks like you are using the generic drivers for the VIA usb rather than the updated ones provided by your motherboard vendor.

I think the problem was most likely triggered by a bug in your usb capture program. I am seeing a huge number of IRP that are not correctly formated.
I/O request packet = irp. I think it just took 17 hours for it to crash your system.




http://www.gigabyte.com/products/product-page.aspx?pid=5655#driver
pick up the 4 updated drivers.





---------------
only thing that seems to be executing at the time of the bugcheck was
Killer Bandwidth Control Filter Driver bwcW10x64.sys
\SystemRoot\system32\DRIVERS\bwcW10x64.sys Mon Sep 28 08:46:01 2015
-------------
machine bugchecked because the CPU memory controller reported a fatal cache error on processor 5 memory bank 1
this is the memory inside the CPU rather than external memory. Based on the fact that the system was running for 17 hour 52 mins, I would be looking for a heat related problem.

in terms of drivers that might be suspect, I see these older drivers:
Kingsoft Internet Security Sandbox kernel
C:\Windows\system32\drivers\kisknl.sys Thu May 23 08:56:48 2013

Sonic CD/DVD driver (used by many different CD/DVD programs)
\SystemRoot\System32\Drivers\PxHlpa64.sys Mon Oct 17 07:29:34 2011

you also have a usb capture program running:
USBPcap.sys Fri Oct 02 02:09:46 2015 (wireshark?)

for the most part it looks like a generic window 10 retail install with no updates applied. (build 10240.16724)

machine info:
BIOS Version F1
BIOS Release Date 11/05/2015
Manufacturer Gigabyte Technology Co., Ltd.
Product GA-990FX-GAMING
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

memory Speed 667MHz
Manufacturer Corsair
Part Number CMZ4GX3M1A160



 


Is this system overclocked?