Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD and computer also hangs requiring hard reset,

4 Weeks Ago   #1
madboy23

windows 7 x64
 
 
BSOD and computer also hangs requiring hard reset,

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.


Code:
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*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.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*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`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*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`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*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`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
---------
 


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



My System SpecsSystem Spec
.
4 Weeks Ago   #2
axe0

Windows 10 Pro
 
 

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.
My System SpecsSystem Spec
4 Weeks Ago   #3
madboy23

windows 7 x64
 
 

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


Code:
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*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`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
---------
My System SpecsSystem Spec
.

4 Weeks Ago   #4
axe0

Windows 10 Pro
 
 

Could you follow the Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums please, I'll need some extra information.
My System SpecsSystem Spec
4 Weeks Ago   #5
madboy23

windows 7 x64
 
 

I have attached the zip file.

Thanks for your help really appreciate it.


Attached Files
File Type: zip MIKE2-PC-19_07_2017_150508_27.zip (2.11 MB, 1 views)
My System SpecsSystem Spec
4 Weeks Ago   #6
axe0

Windows 10 Pro
 
 

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".




BSOD and computer also hangs requiring hard reset, Diagnostics Test BSOD and computer also hangs requiring hard reset,
 HDD TEST

Note   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   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 Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
My System SpecsSystem Spec
4 Weeks Ago   #7
madboy23

windows 7 x64
 
 

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?
My System SpecsSystem Spec
4 Weeks Ago   #8
madboy23

windows 7 x64
 
 

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.


Attached Thumbnails
BSOD and computer also hangs requiring hard reset,-usb-hub-screenshot.png  
My System SpecsSystem Spec
4 Weeks Ago   #9
axe0

Windows 10 Pro
 
 

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.
My System SpecsSystem Spec
4 Weeks Ago   #10
madboy23

windows 7 x64
 
 

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)
My System SpecsSystem Spec
Reply

 BSOD and computer also hangs requiring hard reset,




Thread Tools




Similar help and support threads
Thread Forum
After 6 hours, the PC just hangs and I have to hard reset
This happened EVERY DAY. I have my PC set to turn off automatically at 1 AM. If I leave it on all day then the next morning I'll come to it and it'll just have the desktop there and none of the icons or ctrl alt del or even pressing the power button will work. I have to hard reset. It's screwing up...
BSOD Help and Support
New Computer Randomly Hard Freezes requiring cold boot to get working.
New custom computer running windows 7 64 pro with SP1. I installed the Os, and drivers from the Asus motherboard disk, on the first day I got it, and from the 2nd day the computer started having random freezes that vary from 1-3 times per day. The first time was while watching a video,...
General Discussion
Random Computer Freeze Requiring Hard Reset
Hello, I recently reinstalled Windows 7 on my custom built PC. Since doing so I have random freezes that allow me to do nothing other than hard reset the computer. There is no particular time that it does it, and it has mostly been noticed while either on the desktop or using Firefox. ...
BSOD Help and Support
Random computer freeze requiring hard reset
Hi all, I've been having this problem for quite some time now (I would say a year or more) where my computer completely freezes up without any prompting. It's quite frustrating to diagnose since it happens on such a random basis -there seems to be no trend as to what kind of programs I have...
General Discussion
Laptop screen goes black, requiring hard reset
Hello, I was hoping maybe somebody could help me with this laptop. The issue I'm having is most of the time when I walk away from it and leave it on, upon returning the screen is just black, the computer is running but there is no response on the keyboard or mouse, which requires a hard shutdown...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:25.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App