BSOD and computer also hangs requiring hard reset,

[madboy23]

I keep getting blue screen of death as well as computer hanging requiring a hard reset, particularly when using ableton live music software, but also happens when not.

Have run memtest and memory passed fine.

Not done any other tests, what is weird is the memory dmp, seemed to point to a different thing each time, but I am no expert in analysing this.

Any other thoughts?

Thanks Mike

Here are the last 5 memory dmp.

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Loading Dump File [C:\Windows\Minidump\061617-93928-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`0380c000 PsLoadedModuleList = 0xfffff800`03a4e730
Debug session time: Fri Jun 16 17:28:51.996 2017 (UTC + 1:00)
System Uptime: 0 days 23:13:58.823
Loading Kernel Symbols
...............................................................

Loading User Symbols
Loading unloaded module list

Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {fffff8a06e762000, 0, fffff88004e486d3, 0}
 
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
 
Could not read faulting driver name
Probably caused by : avgntflt.sys ( avgntflt+126d3 )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a06e762000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004e486d3, If non-zero, the instruction address which referenced the bad memory
                address.
Arg4: 0000000000000000, (reserved)
 
Debugging Details:
-----------------
 
Could not read faulting driver name
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ab8100
GetUlongFromAddress: unable to read from fffff80003ab81c8
 fffff8a06e762000 Paged pool
 
FAULTING_IP: 
avgntflt+126d3
fffff880`04e486d3 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8]
 
MM_INTERNAL_CODE:  0
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  Evolve R2 Setu
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
TRAP_FRAME:  fffff88013b38ff0 -- (.trap 0xfffff88013b38ff0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000001e rbx=0000000000000000 rcx=fffff8a0073018f0
rdx=0000000067460714 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004e486d3 rsp=fffff88013b39188 rbp=fffff8a06e7606e0
 r8=00000000ffffeff4  r9=0000000000640073 r10=0061002e00760061
r11=fffff8a00730002c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
avgntflt+0x126d3:
fffff880`04e486d3 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8] ds:fffff8a0`6e761ffc=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff800038f940e to fffff8000387b4c0
 
STACK_TEXT:  
fffff880`13b38e88 fffff800`038f940e : 00000000`00000050 fffff8a0`6e762000 00000000`00000000 fffff880`13b38ff0 : nt!KeBugCheckEx
fffff880`13b38e90 fffff800`038795ee : 00000000`00000000 fffff8a0`6e762000 fffff880`13b39100 00000000`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x3bc5f
fffff880`13b38ff0 fffff880`04e486d3 : fffff880`04e574f7 00000000`00000000 00000000`00000009 fffff8a0`6e7606e0 : nt!KiPageFault+0x16e
fffff880`13b39188 fffff880`04e574f7 : 00000000`00000000 00000000`00000009 fffff8a0`6e7606e0 fffff8a0`0654c7a0 : avgntflt+0x126d3
fffff880`13b39190 00000000`00000000 : 00000000`00000009 fffff8a0`6e7606e0 fffff8a0`0654c7a0 fffff8a0`0654c7a0 : avgntflt+0x214f7
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
avgntflt+126d3
fffff880`04e486d3 4c8b540af8      mov     r10,qword ptr [rdx+rcx-8]
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  avgntflt+126d3
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: avgntflt
 
IMAGE_NAME:  avgntflt.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5909ba17
 
FAILURE_BUCKET_ID:  X64_0x50_avgntflt+126d3
 
BUCKET_ID:  X64_0x50_avgntflt+126d3
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0x50_avgntflt+126d3
 
FAILURE_ID_HASH:  {566c5280-0c5d-5910-b746-81702c16b1c8}
 
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Windows\Minidump\070417-94255-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`03816000 PsLoadedModuleList = 0xfffff800`03a58750
Debug session time: Tue Jul  4 22:58:22.471 2017 (UTC + 1:00)
System Uptime: 0 days 0:20:03.299
Loading Kernel Symbols
...............................................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, fffffa801043b028, be000000, 800400}
 
Probably caused by : GenuineIntel
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801043b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
STACK_TEXT:  
fffff880`009f7b58 fffff800`03e0ea3b : 00000000`00000124 00000000`00000000 fffffa80`1043b028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f7b60 fffff800`0399ffef : 00000000`00000001 fffffa80`10231ea0 00000000`00000000 fffffa80`10231ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7ba0 fffff800`03e0e700 : 00000000`00000728 fffffa80`10231ea0 fffff880`009f7f30 fffff880`009f7f00 : nt!WheaReportHwError+0x26f
fffff880`009f7c00 fffff800`03e0e052 : fffffa80`10231ea0 fffff880`009f7f30 fffffa80`10231ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7d50 fffff800`03e0df0d : 00000000`00000008 00000000`00000001 fffff880`009f7fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7d90 fffff800`03e01e88 : fffffa80`109b01a0 00000000`314c535f 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7dc0 fffff800`0388572c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7df0 fffff800`03885593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7f30 fffff880`0442d83f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1b930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBPORT!USBPORTSVC_LogEntry+0x1f
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: GenuineIntel
 
IMAGE_NAME:  GenuineIntel
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
IMAGE_VERSION:  
 
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
 
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
 
FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
 
Followup: MachineOwner
---------
 
-------------------------------------------------------------------------------------------------------

 
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\070717-93943-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`0380e000 PsLoadedModuleList = 0xfffff800`03a50750
Debug session time: Fri Jul  7 16:25:33.324 2017 (UTC + 1:00)
System Uptime: 0 days 0:39:29.151
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck FE, {6, fffffa801089f1a0, 4f444648, 0}
 
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c0 )
 
Followup: MachineOwner
---------
 
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
                has been corrupted.
Arg2: fffffa801089f1a0, Object address
Arg3: 000000004f444648, Signature that was expected
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
 
OVERLAPPED_MODULE: Address regions for 'nikkbdmidi' and 'spsys.sys' overlap
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0xFE
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  2
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
DPC_STACK_BASE:  FFFFF880030BFFB0
 
LAST_CONTROL_TRANSFER:  from fffff8800402d8c1 to fffff8000387ee40
 
STACK_TEXT:  
fffff880`030b87d8 fffff880`0402d8c1 : 00000000`000000fe 00000000`00000006 fffffa80`1089f1a0 00000000`4f444648 : nt!KeBugCheckEx
fffff880`030b87e0 fffff880`040117f6 : fffffa80`0c785098 fffff880`030b8900 fffffa80`1089f000 00000000`00000055 : USBPORT!USBPORT_AssertSig+0x25
fffff880`030b8820 fffff880`0400fc45 : 00000000`00000001 00000000`ffffffff 00000000`00000000 00000000`ffffff02 : USBPORT!GetHcFdoExt+0x1a
fffff880`030b8850 fffff880`04012e38 : fffffa80`0f011ba0 00000000`00000000 00000000`00000000 fffff880`0400714d : USBPORT!USBPORT_TxSetState+0x1d
fffff880`030b8880 fffff880`04015a1b : fffffa80`0f011ba0 00000000`00000000 fffffa80`1089fa18 fffff880`0402d84c : USBPORT!USBPORT_Core_iCompleteTransfer+0x90
fffff880`030b88d0 fffff880`041c06a8 : fffffa80`0d52dd90 fffffa80`108a06e0 00000000`00000001 fffffa80`00000000 : USBPORT!USBPORTSVC_CompleteTransfer+0x2b3
fffff880`030b8960 fffff880`041bfc1b : fffffa80`0d52daf8 00000000`00000000 fffffa80`0d52dd90 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c0
fffff880`030b89f0 fffff880`041c510e : fffffa80`0d52daf8 fffff880`0402d8c2 00000000`00000010 00000000`00000246 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`030b8a30 fffff880`04001e6b : 00000000`00000002 fffffa80`0d52d8b0 fffffa80`1089f1a0 00000000`ffffff02 : usbehci!EHCI_PollEndpoint+0x56
fffff880`030b8a70 fffff880`04006bc1 : 00000000`00000070 00000000`00000004 fffffa80`0d52d8b0 fffffa80`1089f050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`030b8aa0 fffff880`04012303 : fffffa80`1089f1a0 00000000`00000070 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`030b8b00 fffff880`04002f69 : fffffa80`1089f050 00000000`00000000 fffffa80`1089fa02 fffffa80`1089fa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`030b8b60 fffff800`0388a7fc : fffff880`03090180 fffffa80`1089fa18 fffffa80`1089fa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b8b90 fffff800`03876b4a : fffff880`03090180 fffff880`0309b0c0 00000000`00000000 fffff880`04002d90 : nt!KiRetireDpcList+0x1bc
fffff880`030b8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+6c0
fffff880`041c06a8 408ac6          mov     al,sil
 
SYMBOL_STACK_INDEX:  6
 
SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+6c0
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: usbehci
 
IMAGE_NAME:  usbehci.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  57b37a2c
 
IMAGE_VERSION:  6.1.7601.23529
 
FAILURE_BUCKET_ID:  X64_0xFE_BAD_SIGNATURE_usbehci!EHCI_sMode_PollEndpointSlot+6c0
 
BUCKET_ID:  X64_0xFE_BAD_SIGNATURE_usbehci!EHCI_sMode_PollEndpointSlot+6c0
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0xfe_bad_signature_usbehci!ehci_smode_pollendpointslot+6c0
 
FAILURE_ID_HASH:  {d11c4f60-a031-62c2-71c5-c4609ba1a13a}
 
Followup: MachineOwner
---------
 
 
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\071417-103335-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`03867000 PsLoadedModuleList = 0xfffff800`03aa9750
Debug session time: Fri Jul 14 14:23:32.785 2017 (UTC + 1:00)
System Uptime: 0 days 1:51:47.613
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck D1, {1, 2, 8, 1}
 
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
 
Followup: MachineOwner
---------
 
3: 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 an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000001, address which referenced memory
 
Debugging Details:
------------------
 
 
OVERLAPPED_MODULE: Address regions for 'fastfat' and 'spsys.sys' overlap
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b13100
GetUlongFromAddress: unable to read from fffff80003b131c8
 0000000000000001 Nonpaged pool
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
+0
00000000`00000001 ??              ???
 
PROCESS_NAME:  System
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0xD1
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
TRAP_FRAME:  fffff88002fff830 -- (.trap 0xfffff88002fff830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8015e24230 rbx=0000000000000000 rcx=fffffa800d4d49b1
rdx=fffffa8015e24231 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000001 rsp=fffff88002fff9c0 rbp=fffff880040177b7
 r8=fffffa8015e24230  r9=0000000000000040 r10=fffff88002fd7b20
r11=fffffa800d4d49b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000001 ??              ???
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff800038d73e9 to fffff800038d7e40
 
FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`00000001 ??              ???
 
STACK_TEXT:  
fffff880`02fff6e8 fffff800`038d73e9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02fff6f0 fffff800`038d6060 : 00000000`00000000 fffffa80`106f2a18 fffffa80`106f21a0 fffff800`03822750 : nt!KiBugCheckDispatch+0x69
fffff880`02fff830 00000000`00000001 : 00000000`00000000 fffffa80`0e3b9df0 fffffa80`1a4ea010 fffff880`04013307 : nt!KiPageFault+0x260
fffff880`02fff9c0 00000000`00000000 : fffffa80`0e3b9df0 fffffa80`1a4ea010 fffff880`04013307 fffffa80`106f21a0 : 0x1
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`038d6060 440f20c0        mov     rax,cr8
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  nt!KiPageFault+260
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5915f59a
 
IMAGE_VERSION:  6.1.7601.23807
 
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
 
BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0xd1_code_av_null_ip_nt!kipagefault+260
 
FAILURE_ID_HASH:  {c3dfd409-49b9-d611-6abd-d25149dd8653}
 
Followup: MachineOwner
---------
 


------------------------------------------------------------------------------

 

[axe0]

Hi madboy23,

Welcome to the 7forums

The 0x50 blames a driver from Avira, uninstall it temporary and use Microsoft Security Essentials as alternative.

The 0x124 means that an uncorrectable hardware error has occured, seeing it started after a call from the USB port drivers and in combination with the bugcode_usb_driver you'll want to update/reinstall chipset and USB drivers from MSI. Also check your USB devices for driver update from their manufacturer.

The 0xD1 occured because of an invalid instruction protocol, can't pinpoint the cause unfortunately.

 

[madboy23]

Thanks a lot for your response, I have also had the following bsod reports, do you think it might be a hardware issues?

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\071617-102648-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Symbol search path is: SRV*C:\Windows\symbol_cache*[url="http://msdl.microsoft.com/download/symbols"]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`0385f000 PsLoadedModuleList = 0xfffff800`03aa1750
Debug session time: Sun Jul 16 14:49:52.254 2017 (UTC + 1:00)
System Uptime: 0 days 20:50:40.082
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, fffffa8010401028, be000000, 800400}
 
Probably caused by : GenuineIntel
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010401028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
STACK_TEXT:  
fffff880`009f7b58 fffff800`03828a3b : 00000000`00000124 00000000`00000000 fffffa80`10401028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f7b60 fffff800`039e8fef : 00000000`00000001 fffffa80`10408ea0 00000000`00000000 fffffa80`10408ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7ba0 fffff800`03828700 : 00000000`00000728 fffffa80`10408ea0 fffff880`009f7f30 fffff880`009f7f00 : nt!WheaReportHwError+0x26f
fffff880`009f7c00 fffff800`03828052 : fffffa80`10408ea0 fffff880`009f7f30 fffffa80`10408ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7d50 fffff800`03827f0d : 00000000`00000008 00000000`00000001 fffff880`009f7fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7d90 fffff800`0381be88 : fffffa80`10720050 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7dc0 fffff800`038ce72c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7df0 fffff800`038ce593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7f30 fffff880`0458cfc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_Core_CheckTimeout+0x34
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: GenuineIntel
 
IMAGE_NAME:  GenuineIntel
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
IMAGE_VERSION:  
 
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
 
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
 
FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
 
Followup: MachineOwner
---------

 

[axe0]

Could you follow the Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums please, I'll need some extra information.

 

[madboy23]

I have attached the zip file.

Thanks for your help really appreciate it.

 

[axe0]

The only consistency I can find is USB, what USB devices are connected to your pc?


You want to run below hard drive scans on all your storage devices (hard drives, SSD drives, external connected drives and USBs)
There are thousands of events about errors with multiple storage devices. Most recents being "the file system on the disk is corrupt and unusable. Please run the chkdsk utility on the volume LACIE 2".

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :ar: Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

[madboy23]

I have had 3 usb hard drives, (2external hard drives and 1 usb stick) fail recently, so they may be the hard ware problems, yet they are no longer attached and I have had blue screens of death since then.

Other usb devices attached are

4 usb hubs
Ableton push midi controller
Komplete kontrol midi keyboard
Soundcraft mtk12 audio interface
Shuttle pro controller

Plus the drives listed in my profile.

I did run this to sort out usb residue Drive Tools for Windows
But still getting bluescreen of death

I am considering doing a full windows 7 reinstall to see if that solves the problem, what do you think?

 

[madboy23]

I am looking at device manager and there are loads of usb hubs on there, I only have 4 external hubs, is this right see screenshot attached.

 

[axe0]

That drive tool, per its description, does nothing more than removing unused entries from the registry. IMHO a little useless.

If your hard drives are close to a critical stage, a clean install won't help solve the problem.

 

[madboy23]

Is that screenshot of the usb hubs, look right to you? 12 hubs, I only have 4 external ones, would they be referring to hubs internal to the pc (excuse my ignorance if thats a stupid question)

 

[axe0]

The USB list is of all USB devices connected, I believe both direct and indirect.

 

[madboy23]

Hi there again, I replaced my power supply with a corsair rm750i, i reinstalled windows and i am still getting BSOD. But the last 2 are exactly the same, seems like it might be the cpu. What do you think?


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-38610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea0750
Debug session time: Sun Aug 6 17:01:59.288 2017 (UTC + 1:00)
System Uptime: 0 days 2:20:38.850
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800dec7028, be000000, 800400}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800dec7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`009f7b58 fffff800`02c27a3b : 00000000`00000124 00000000`00000000 fffffa80`0dec7028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f7b60 fffff800`02de7fef : 00000000`00000001 fffffa80`0dd8a870 00000000`00000000 fffffa80`0dd8a8c0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7ba0 fffff800`02c27700 : 00000000`00000728 fffffa80`0dd8a870 fffff880`009f7f30 fffff880`009f7f00 : nt!WheaReportHwError+0x26f
fffff880`009f7c00 fffff800`02c27052 : fffffa80`0dd8a870 fffff880`009f7f30 fffffa80`0dd8a870 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7d50 fffff800`02c26f0d : 00000000`00000008 00000000`00000001 fffff880`009f7fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7d90 fffff800`02c1ae88 : 00000000`00000002 fffffa80`0e4971a0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7dc0 fffff800`02ccd72c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7df0 fffff800`02ccd593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7f30 fffff800`02cd8bc6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1ba40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseSpinLock+0x6


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

SECOND MINI DMP


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-37221-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4c750
Debug session time: Sun Aug 6 18:22:54.927 2017 (UTC + 1:00)
System Uptime: 0 days 0:23:42.756
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800de3f028, be000000, 800400}

Probably caused by : GenuineIntel

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de3f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff800`040e7a98 fffff800`03202a3b : 00000000`00000124 00000000`00000000 fffffa80`0de3f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`040e7aa0 fffff800`02d93fef : 00000000`00000001 fffffa80`0de362a0 00000000`00000000 fffffa80`0de362f0 : hal!HalBugCheckSystem+0x1e3
fffff800`040e7ae0 fffff800`03202700 : 00000000`00000728 fffffa80`0de362a0 fffff800`040e7e70 fffff800`040e7e00 : nt!WheaReportHwError+0x26f
fffff800`040e7b40 fffff800`03202052 : fffffa80`0de362a0 fffff800`040e7e70 fffffa80`0de362a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`040e7c90 fffff800`03201f0d : 00000000`00000008 00000000`00000001 fffff800`040e7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`040e7cd0 fffff800`031f5e88 : 00000000`00000002 fffffa80`0e57b100 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`040e7d00 fffff800`02c7972c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`040e7d30 fffff800`02c79593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`040e7e70 fffff800`02c84cef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`040dba20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x4f


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800de3f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff800`040e7a98 fffff800`03202a3b : 00000000`00000124 00000000`00000000 fffffa80`0de3f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`040e7aa0 fffff800`02d93fef : 00000000`00000001 fffffa80`0de362a0 00000000`00000000 fffffa80`0de362f0 : hal!HalBugCheckSystem+0x1e3
fffff800`040e7ae0 fffff800`03202700 : 00000000`00000728 fffffa80`0de362a0 fffff800`040e7e70 fffff800`040e7e00 : nt!WheaReportHwError+0x26f
fffff800`040e7b40 fffff800`03202052 : fffffa80`0de362a0 fffff800`040e7e70 fffffa80`0de362a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`040e7c90 fffff800`03201f0d : 00000000`00000008 00000000`00000001 fffff800`040e7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`040e7cd0 fffff800`031f5e88 : 00000000`00000002 fffffa80`0e57b100 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`040e7d00 fffff800`02c7972c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`040e7d30 fffff800`02c79593 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`040e7e70 fffff800`02c84cef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`040dba20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x4f


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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

 

[axe0]

The dumps only show that a processor aborts any processing and reports an error after which the system crashes, this is a standard thing with 0x124 crashes.
Run !errrec command on argument 2, e.g. of last dump !errrec fffffa800de3f028, it dumps the error records that contains the reason why a crash was called. Please post the output of the error record, note the triple 'r' in !errrec.

EDIT: run the !errrec command on all recent 0x124 dumps. The more error records there are, the easier it is to find the reason for the crashes.

 

[madboy23]

Here is the dm diagnosis, do you still see usb as a problem,

Cheers,
Mike

 

[axe0]

Included hard drive tests, file system issues explained in post #6 is still happening

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it please.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :arrow: Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

 

[madboy23]

I am currently scanning drives using hd tune, no problems yet but only done 4 drives and i have 11, on most of the drives I can't get any info under the health tab, is that because they are usb?

I also used the drive verifier programme, windows would not even load just got to starting windows and BSOD repeatedly every time I tried to boot into windows, had to go into safe mode and turn drive verifier off. Got this dmp file.


Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080617-9375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*Symbol information
Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e54750
Debug session time: Sun Aug 6 20:01:14.846 2017 (UTC + 1:00)
System Uptime: 0 days 0:00:09.658
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {215, fffff8800f041eab, fffff980082b0e10, 0}

*** WARNING: Unable to verify timestamp for NIWinCDEmu.sys
*** ERROR: Module load completed but symbols could not be loaded for NIWinCDEmu.sys
Probably caused by : NIWinCDEmu.sys ( NIWinCDEmu+9eab )

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

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000215, A non-successful non-STATUS_NOT_SUPPORTED IRP status for IRP_MJ_PNP is being
passed down stack. Failed PNP IRPs must be completed.
Arg2: fffff8800f041eab, The address in the driver's code where the error was detected.
Arg3: fffff980082b0e10, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc9_215

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 215

FAULTING_IP:
NIWinCDEmu+9eab
fffff880`0f041eab 4883c438 add rsp,38h

FOLLOWUP_IP:
NIWinCDEmu+9eab
fffff880`0f041eab 4883c438 add rsp,38h

IRP_ADDRESS: fffff980082b0e10

DEVICE_OBJECT: fffffa800f499e00

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800031154ec to fffff80002c82e40

STACK_TEXT:
fffff880`033af0d8 fffff800`031154ec : 00000000`000000c9 00000000`00000215 fffff880`0f041eab fffff980`082b0e10 : nt!KeBugCheckEx
fffff880`033af0e0 fffff800`0311f5aa : fffff800`03113b00 fffff880`0f041eab fffff980`082b0e10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033af120 fffff800`031205b3 : 00000000`00000215 fffff880`0f041eab fffff980`082b0e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033af170 fffff800`0312c1e2 : fffff980`082b0f70 00000000`00000002 00000000`00000000 fffff800`02d7227b : nt!VfErrorReport1+0x63
fffff880`033af210 fffff800`03115230 : fffff980`082b0f70 fffffa80`0f498760 fffff980`082b0f70 fffff980`082b0f70 : nt!VfPnpVerifyIrpStackDownward+0xe2
fffff880`033af280 fffff800`0312dc80 : fffffa80`0f498760 fffffa80`0f7e0050 fffff980`082b0e10 fffffa80`0e0c01c8 : nt!VfMajorVerifyIrpStackDownward+0x80
fffff880`033af2e0 fffff800`0312deb6 : fffff980`00000000 fffffa80`00000000 fffffa80`00000000 fffff880`0f041eab : nt!IovpCallDriver1+0x4a0
fffff880`033af390 fffff800`03131ce2 : fffff980`082b0e10 00000000`00000002 fffff980`082b0e48 00000000`00000000 : nt!VfBeforeCallDriver+0x186
fffff880`033af3f0 fffff880`0f041eab : fffff980`082b0e10 00000000`00000002 fffffa80`0f499060 fffffa80`0f7f4430 : nt!IovCallDriver+0x502
fffff880`033af450 fffff980`082b0e10 : 00000000`00000002 fffffa80`0f499060 fffffa80`0f7f4430 fffffa80`00000000 : NIWinCDEmu+0x9eab
fffff880`033af458 00000000`00000002 : fffffa80`0f499060 fffffa80`0f7f4430 fffffa80`00000000 fffff980`082b0e10 : 0xfffff980`082b0e10
fffff880`033af460 fffffa80`0f499060 : fffffa80`0f7f4430 fffffa80`00000000 fffff980`082b0e10 fffff980`014c8e00 : 0x2
fffff880`033af468 fffffa80`0f7f4430 : fffffa80`00000000 fffff980`082b0e10 fffff980`014c8e00 fffff880`0f0420c4 : 0xfffffa80`0f499060
fffff880`033af470 fffffa80`00000000 : fffff980`082b0e10 fffff980`014c8e00 fffff880`0f0420c4 fffff980`014c8e00 : 0xfffffa80`0f7f4430
fffff880`033af478 fffff980`082b0e10 : fffff980`014c8e00 fffff880`0f0420c4 fffff980`014c8e00 fffff880`033af510 : 0xfffffa80`00000000
fffff880`033af480 fffff980`014c8e00 : fffff880`0f0420c4 fffff980`014c8e00 fffff880`033af510 fffffa80`0e0c01c8 : 0xfffff980`082b0e10
fffff880`033af488 fffff880`0f0420c4 : fffff980`014c8e00 fffff880`033af510 fffffa80`0e0c01c8 00000000`00000002 : 0xfffff980`014c8e00
fffff880`033af490 fffff980`014c8e00 : fffff880`033af510 fffffa80`0e0c01c8 00000000`00000002 00000000`00000000 : NIWinCDEmu+0xa0c4
fffff880`033af498 fffff880`033af510 : fffffa80`0e0c01c8 00000000`00000002 00000000`00000000 fffff880`0f041f28 : 0xfffff980`014c8e00
fffff880`033af4a0 fffffa80`0e0c01c8 : 00000000`00000002 00000000`00000000 fffff880`0f041f28 fffff880`033af740 : 0xfffff880`033af510
fffff880`033af4a8 00000000`00000002 : 00000000`00000000 fffff880`0f041f28 fffff880`033af740 00000000`00000000 : 0xfffffa80`0e0c01c8
fffff880`033af4b0 00000000`00000000 : fffff880`0f041f28 fffff880`033af740 00000000`00000000 00000000`00000002 : 0x2


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: NIWinCDEmu+9eab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NIWinCDEmu

IMAGE_NAME: NIWinCDEmu.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5062e9b1

FAILURE_BUCKET_ID: X64_0xc9_215_VRF_NIWinCDEmu+9eab

BUCKET_ID: X64_0xc9_215_VRF_NIWinCDEmu+9eab

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc9_215_vrf_niwincdemu+9eab

FAILURE_ID_HASH: {29fd4de1-7065-5473-6755-81a7450a8ed5}

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

 

[madboy23]

Found these, do you think this could be the problem?

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-blue-screen-error-niwincdemusys/d48dd300-6d0c-48ed-9502-49fea69e2c66
BSOD for NI driver? | NI Community Forum
Native Instruments Native Access = BSOD?!! - Cockos Incorporated Forums

Cheers,
mike

 

[axe0]

Please finish the hardware scans, the driver being flagged could be a false positive as a result of bad hardware.

 

[madboy23]

Hi There,

Still getting problems with BSOD (though not as bad), I checked all the hard drives and the ones that were dodgy I no longer use, memtest passed fine, used prime cpu and furmark all fine.

I have attached the dm log file, can you see anything there that might indicate what is causing it.

I am thinking it might just be a dodgy motherboard or processor.

The bsod tend to happen when i ma using Ableton Live with midi controllers Ableton Push2 and the Native Instruments Komplete kontrol keyboard, can you see if they are having any impact? Which is also the time when the CPU is being used alot.

Any help would be much appreciated.

Cheers,
Mike

 

[axe0]

Logs show a lot of hard drive issues the past months, if you removed the onces that were bad there's a good chance the issue is with the motherboard.