Computer Restarted from Bugcheck Error - HELP

Toggle sidebar Toggle sidebar
B

BackNBlack

Commendable
Jun 13, 2016
9
0
1,510
Please help, I've been having random restarts from bugchecks.

Here is the link to the 7z minidump file. https://onedrive.live.com/embed?cid=A0BDE4B354A48B8A&resid=A0BDE4B354A48B8A%21459&authkey=ACJYPnUo3i-Izuo

Below is the information from the MEMORY.DMP WinDbg results.
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Machine Name:
Kernel base = 0xfffff803`0381d000 PsLoadedModuleList = 0xfffff803`03afbcd0
Debug session time: Mon Jun 13 15:22:45.173 2016 (UTC - 4:00)
System Uptime: 4 days 18:51:49.862
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {7c20, ff, 78, fffff803039e08c0}

Probably caused by : ntkrnlmp.exe ( nt!KiEndCounterAccumulation+c )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000007c20, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000078, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803039e08c0, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1701

BIOS_DATE: 03/25/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: MAXIMUS VIII RANGER

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: 7c20

BUGCHECK_P2: ff

BUGCHECK_P3: 78

BUGCHECK_P4: fffff803039e08c0

READ_ADDRESS: 0000000000007c20

CURRENT_IRQL: d

FAULTING_IP:
nt!KiEndCounterAccumulation+c
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h]

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: BACKNBLACK

ANALYSIS_SESSION_TIME: 06-13-2016 15:32:33.0596

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffd0007ba6bde0 -- (.trap 0xffffd0007ba6bde0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=ffffd0007b977cc0
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff803039e08c0 rsp=ffffd0007ba6bf78 rbp=00000000001ea4c2
r8=0000000000007c00 r9=0000000000000000 r10=ffffd0007b971444
r11=0000000000000109 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na po nc
nt!KiEndCounterAccumulation+0xc:
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h] ds:00000000`00007c20=????????????????
Resetting default scope

EXCEPTION_RECORD: fffff80073191380 -- (.exr 0xfffff80073191380)
ExceptionAddress: c0330475c98548d9
ExceptionCode: 8348c033
ExceptionFlags: ccc328c4
NumberParameters: 964705003
Parameter[0]: 0001c7e82deb0451
Parameter[1]: 74c08548d08b4800
Parameter[2]: 0374c984024b8a20
Parameter[3]: f980014b8aead348
Parameter[4]: 00000001b80e7340
Parameter[5]: 2348c8ff48e0d348
Parameter[6]: 20c48348c28b48d0
Parameter[7]: 74c98548ccccc35b
Parameter[8]: 485708245c894874
Parameter[9]: 480002798020ec83
Parameter[10]: 801575d98b48fa8b
Parameter[11]: 4001798008750a39
Parameter[12]: 3803418a3ceb0a75
Parameter[13]: 00015fe834740141
Parameter[14]: 7240f980014b8a00

LAST_CONTROL_TRANSFER: from fffff8030396a2e9 to fffff8030395f780

STACK_TEXT:
ffffd000`7ba6bc98 fffff803`0396a2e9 : 00000000`0000000a 00000000`00007c20 00000000`000000ff 00000000`00000078 : nt!KeBugCheckEx
ffffd000`7ba6bca0 fffff803`03968ac7 : 000001fc`60607d78 00000000`00000001 00000000`0000004d ffffd000`7b96b180 : nt!KiBugCheckDispatch+0x69
ffffd000`7ba6bde0 fffff803`039e08c0 : fffff803`03982ae2 ffffd000`7b977cc0 00000000`00000000 00000178`dd255afa : nt!KiPageFault+0x247
ffffd000`7ba6bf78 fffff803`03982ae2 : ffffd000`7b977cc0 00000000`00000000 00000178`dd255afa ffffd000`7ba5c660 : nt!KiEndCounterAccumulation+0xc
ffffd000`7ba6bf80 fffff803`03960b80 : ffffe000`fcb8f010 ffffd000`7ba5c660 ffffe000`f46edc00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x149e2
ffffd000`7ba6bfb0 fffff803`03960fd7 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0xc0
ffffd000`7ba5c5e0 fffff800`73192972 : fffff800`73191380 00000000`00000046 ffffd000`7b96b180 ffffe000`fe861270 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd000`7ba5c778 fffff800`73191380 : 00000000`00000046 ffffd000`7b96b180 ffffe000`fe861270 00000000`00000000 : intelppm!C1Halt+0x2
ffffd000`7ba5c780 fffff803`0386f875 : 00000000`00000000 00000000`00000068 0002f935`7b48da9c ffffe000`fcb8f010 : intelppm!AcpiCStateIdleExecute+0x20
ffffd000`7ba5c7b0 fffff803`0386f0bb : 00000000`00000000 00000000`00000002 ffffe000`fcb8f0f0 00000000`00000000 : nt!PpmIdleExecuteTransition+0x605
ffffd000`7ba5ca00 fffff803`0396250c : ffffffff`00000000 ffffd000`7b96b180 ffffd000`7b977cc0 ffffe001`4f6f4840 : nt!PoIdle+0x33b
ffffd000`7ba5cb60 00000000`00000000 : ffffd000`7ba5d000 ffffd000`7ba56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: d31af1e84877aae49d33ab47b067afcb9cc8d93b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: febe78555ce06a73b0693dba40c508a13eec4dd7

THREAD_SHA1_HASH_MOD: f52d7f996b4dfd0119f4e40c92cfaadd13b86b92

FOLLOWUP_IP:
nt!KiEndCounterAccumulation+c
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h]

FAULT_INSTR_CODE: 20588b4d

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiEndCounterAccumulation+c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 571af445

BUCKET_ID_FUNC_OFFSET: c

FAILURE_BUCKET_ID: AV_nt!KiEndCounterAccumulation

BUCKET_ID: AV_nt!KiEndCounterAccumulation

PRIMARY_PROBLEM_CLASS: AV_nt!KiEndCounterAccumulation

TARGET_TIME: 2016-06-13T19:22:45.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-23 00:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 4ca

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!kiendcounteraccumulation

FAILURE_ID_HASH: {bd23d296-b07f-e492-1736-0c1b9b42244d}

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

7: kd> g
^ No runnable debuggees error in 'g'
7: kd> g
^ No runnable debuggees error in 'g'
7: kd> BUGCHECK_P2: ff.bugcheck
^ Operation not supported by current debuggee error in 'BUGCHECK_P2: ff.bugcheck'
7: kd>
7: kd> dq NT!KiBugCheckData L5
fffff803`03b02700 00000000`0000000a 00000000`00007c20
fffff803`03b02710 00000000`000000ff 00000000`00000078
fffff803`03b02720 fffff803`039e08c0
7: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00007c20 00000000`000000ff 00000000`00000078 fffff803`039e08c0

I hope someone can help me determine what the root cause is.

Thank You!
 
Sort by date Sort by votes
Hello... let's see what the OS is reporting as the error... Right click Computer-Manage-System Tools-Windows logs-system.... Click on the "RED" errors, for more information... and files/drivers/Apps, comments/suggestions/information associated with them B )

Posting screen images from here will help me, help you faster... But copy and posting text will work too B )
 
Upvote 0 Downvote
Event Logs from during the time of reboot are below.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/13/2016 3:24:05 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: BACKNBLACK
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-06-13T19:24:05.477912000Z" />
<EventRecordID>16228</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x7c20</Data>
<Data Name="BugcheckParameter2">0xff</Data>
<Data Name="BugcheckParameter3">0x78</Data>
<Data Name="BugcheckParameter4">0xfffff803039e08c0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 6/13/2016 3:24:13 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BACKNBLACK
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000007c20, 0x00000000000000ff, 0x0000000000000078, 0xfffff803039e08c0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2cf8f1c8-d58c-4bcd-a7f1-f12acad45c18.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-06-13T19:24:13.576513400Z" />
<EventRecordID>16256</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000000a (0x0000000000007c20, 0x00000000000000ff, 0x0000000000000078, 0xfffff803039e08c0)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">2cf8f1c8-d58c-4bcd-a7f1-f12acad45c18</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 6/13/2016 3:24:12 PM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BACKNBLACK
Description:
The previous system shutdown at 15:22:22 on ‎13/‎06/‎2016 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-06-13T19:24:12.529526600Z" />
<EventRecordID>16211</EventRecordID>
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security />
</System>
<EventData>
<Data>15:22:22</Data>
<Data>‎13/‎06/‎2016</Data>
<Data>
</Data>
<Data>
</Data>
<Data>413487</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E007060001000D000F00160016007B02E007060001000D001300160016007B023C0000003C000000000000000000000000000000000000000100000000000000</Binary>
</EventData>
</Event>

I greatly appreciate your help, let me know if you need any further information.
 
Upvote 0 Downvote
ASUS ROG Maximus VIII Ranger Motherboard
32 GB Corsair Vengeance LPX DDR4 2400 Memory
Intel Core i7-6700K processor
EVGA Geforce GTX 980 GPU
Corsair Hydro H100i-v2 cooler
Corsair AX1200 PSU
Samsung 850 EVO SSD
Seagate 2tb drive
Asus VS247H-P Monitor
Asus VE248H monitor
Logitech G700S mouse
Logitech G15 keyboard
 
Upvote 0 Downvote
no overclocking.
I can run the PC idle all day long with no lockups/restarts, however on occasion while running a game, just happens to be Overwatch lately since that is all I am playing I will get the error as indicated in my first post.
 
Upvote 0 Downvote
Hello... can you take Digital Picture of the Screen and post it for us as they POP up?
1) you could have a POWER Supply/Video card/CPU over heating and losing communications with the OS... this is all the kernal41 and other "system did not shut down properly... do you have another PS or Video card to try?
2) as a "Simple Test" remove a cover off your PC case and test the game that way as a case temperature problem.

let me know
 
Upvote 0 Downvote
I am certain it is not an overheating issue as I have been monitoring CPU/GPU temperatures and they are certainly not high by any means. I do not have another PS or GPU to try, however I have run Prime 95 on several occasions for 2+ hours and have no issues. I also ran 3d Mark with no issues.

I received two more critical events last night, event WinDbg print outs below:

First One:

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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.306.amd64fre.th2_release_sec.160422-1850
Machine Name:
Kernel base = 0xfffff803`0381d000 PsLoadedModuleList = 0xfffff803`03afbcd0
Debug session time: Mon Jun 13 15:22:45.173 2016 (UTC - 4:00)
System Uptime: 4 days 18:51:49.862
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {7c20, ff, 78, fffff803039e08c0}

Probably caused by : ntkrnlmp.exe ( nt!KiEndCounterAccumulation+c )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000007c20, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000078, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803039e08c0, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1701

BIOS_DATE: 03/25/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: MAXIMUS VIII RANGER

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 7c20

BUGCHECK_P2: ff

BUGCHECK_P3: 78

BUGCHECK_P4: fffff803039e08c0

READ_ADDRESS: fffff80303b9b520: Unable to get MiVisibleState
0000000000007c20

CURRENT_IRQL: d

FAULTING_IP:
nt!KiEndCounterAccumulation+c
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h]

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: BACKNBLACK

ANALYSIS_SESSION_TIME: 06-20-2016 12:38:49.0927

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME: ffffd0007ba6bde0 -- (.trap 0xffffd0007ba6bde0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=ffffd0007b977cc0
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff803039e08c0 rsp=ffffd0007ba6bf78 rbp=00000000001ea4c2
r8=0000000000007c00 r9=0000000000000000 r10=ffffd0007b971444
r11=0000000000000109 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na po nc
nt!KiEndCounterAccumulation+0xc:
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h] ds:00000000`00007c20=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8030396a2e9 to fffff8030395f780

STACK_TEXT:
ffffd000`7ba6bc98 fffff803`0396a2e9 : 00000000`0000000a 00000000`00007c20 00000000`000000ff 00000000`00000078 : nt!KeBugCheckEx
ffffd000`7ba6bca0 fffff803`03968ac7 : 000001fc`60607d78 00000000`00000001 00000000`0000004d ffffd000`7b96b180 : nt!KiBugCheckDispatch+0x69
ffffd000`7ba6bde0 fffff803`039e08c0 : fffff803`03982ae2 ffffd000`7b977cc0 00000000`00000000 00000178`dd255afa : nt!KiPageFault+0x247
ffffd000`7ba6bf78 fffff803`03982ae2 : ffffd000`7b977cc0 00000000`00000000 00000178`dd255afa ffffd000`7ba5c660 : nt!KiEndCounterAccumulation+0xc
ffffd000`7ba6bf80 fffff803`03960b80 : ffffe000`fcb8f010 ffffd000`7ba5c660 ffffe000`f46edc00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x149e2
ffffd000`7ba6bfb0 fffff803`03960fd7 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0xc0
ffffd000`7ba5c5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 87e41ea7cc2a9d9d115522b70a3b10355ad40b31

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4ea062357ea3678dbecb1285395962363a523e36

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP:
nt!KiEndCounterAccumulation+c
fffff803`039e08c0 4d8b5820 mov r11,qword ptr [r8+20h]

FAULT_INSTR_CODE: 20588b4d

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiEndCounterAccumulation+c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 571af445

IMAGE_VERSION: 10.0.10586.306

BUCKET_ID_FUNC_OFFSET: c

FAILURE_BUCKET_ID: AV_nt!KiEndCounterAccumulation

BUCKET_ID: AV_nt!KiEndCounterAccumulation

PRIMARY_PROBLEM_CLASS: AV_nt!KiEndCounterAccumulation

TARGET_TIME: 2016-06-13T19:22:45.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-23 00:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: b9e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!kiendcounteraccumulation

FAILURE_ID_HASH: {bd23d296-b07f-e492-1736-0c1b9b42244d}

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

Second One Here:

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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.420.amd64fre.th2_release_sec.160527-1834
Machine Name:
Kernel base = 0xfffff803`71c1d000 PsLoadedModuleList = 0xfffff803`71efbcf0
Debug session time: Sun Jun 19 21:46:51.225 2016 (UTC - 4:00)
System Uptime: 0 days 1:01:16.928
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80371c418d9, ffffe001ee18a080, 5f00}

Probably caused by : memory_corruption ( nt!MiCheckVirtualAddress+b9 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80371c418d9, The address that the exception occurred at
Arg3: ffffe001ee18a080, Parameter 0 of the exception
Arg4: 0000000000005f00, Parameter 1 of the exception

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.420.amd64fre.th2_release_sec.160527-1834

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1701

BIOS_DATE: 03/25/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: MAXIMUS VIII RANGER

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80371c418d9

BUGCHECK_P3: ffffe001ee18a080

BUGCHECK_P4: 5f00

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!MiCheckVirtualAddress+b9
fffff803`71c418d9 1f ???

EXCEPTION_PARAMETER1: ffffe001ee18a080

EXCEPTION_PARAMETER2: 0000000000005f00

BUGCHECK_STR: 0x1E_c000001d

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: BACKNBLACK

ANALYSIS_SESSION_TIME: 06-20-2016 12:44:08.0698

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff80371d98be2 to fffff80371d5f7a0

FAILED_INSTRUCTION_ADDRESS:
nt!MiCheckVirtualAddress+b9
fffff803`71c418d9 1f ???

STACK_TEXT:
ffffd000`24b66d58 fffff803`71d98be2 : 00000000`0000001e ffffffff`c000001d fffff803`71c418d9 ffffe001`ee18a080 : nt!KeBugCheckEx
ffffd000`24b66d60 fffff803`71d6a4c2 : ffffe001`ec280208 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2a9e2
ffffd000`24b67440 fffff803`71d681c6 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000005 : nt!KiExceptionDispatch+0xc2
ffffd000`24b67620 fffff803`71c418d9 : 00000000`00000004 0000000a`00000000 ffffd001`070af180 00000000`00000000 : nt!KiInvalidOpcodeFault+0x106
ffffd000`24b677b0 fffff803`71c88d91 : ffffd000`24b67990 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCheckVirtualAddress+0xb9
ffffd000`24b677e0 fffff803`71c8828c : 00000000`00000006 00000000`00005f00 00000000`00000000 fffff803`00000000 : nt!MiResolvePageTablePage+0x101
ffffd000`24b678a0 fffff803`71d68abc : 00000000`00000000 ffffe001`eb33bd70 00000000`00000000 ffffe001`ec2bf2e0 : nt!MmAccessFault+0x25c
ffffd000`24b67a00 00007fff`cab5e289 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
000000c5`2d27f570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`cab5e289


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: b15dfef278ab5785935f6e219b80330d804d1962

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d2f7b3389c781c95712ce8cd83ecd8cc753c1467

THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!MiCheckVirtualAddress+b9
fffff803`71c418d9 1f ???

FAULT_INSTR_CODE: 841f

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MiCheckVirtualAddress+b9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5749178b

IMAGE_VERSION: 10.0.10586.420

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: b9

FAILURE_BUCKET_ID: 0x1E_c000001d_BAD_IP_nt!MiCheckVirtualAddress

BUCKET_ID: 0x1E_c000001d_BAD_IP_nt!MiCheckVirtualAddress

PRIMARY_PROBLEM_CLASS: 0x1E_c000001d_BAD_IP_nt!MiCheckVirtualAddress

TARGET_TIME: 2016-06-20T01:46:51.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-05-27 23:59:07

BUILDDATESTAMP_STR: 160527-1834

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.420.amd64fre.th2_release_sec.160527-1834

ANALYSIS_SESSION_ELAPSED_TIME: 509

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c000001d_bad_ip_nt!micheckvirtualaddress

FAILURE_ID_HASH: {45963da9-7fa7-fbf2-97c2-eeac6d6b8111}

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

 
Upvote 0 Downvote
Hello... this info you are sending me is Hard to read? or?... Please follow my instructions to view/img the actual Windows screen for me... this is where I work best... B / I have corrected a error in my instruction, adding "system Tools" to the Path... check to see if this helps you help me... B /

You NEED to be logged on as administrator to the OS...

let's see what the OS is reporting as the error... Right click computer-manage-System Tools-Windows logs-system.... Click on the "RED" errors, for more information... and files/drivers/Apps, comments/suggestions/information associated with them B )

Posting screen images from here will help me, help you faster... But copy and posting text will work too B )

Check this post and see how easy this is for me to read the "DEBUG" report... THX B )

http://www.tomshardware.com/answers/id-3095849/understanding-cpu-temperature-readings-cpuid-hwmonitor.html
 
Upvote 0 Downvote
oops Sorry about that those are taken from WinDbg, thought they would be helpful.

Below are the critical errors I received yesterday out of the Event Viewer

#1
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/19/2016 8:45:37 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: BACKNBLACK
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-06-20T00:45:37.909380800Z" />
<EventRecordID>16628</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

#2
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/19/2016 9:47:47 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: BACKNBLACK
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-06-20T01:47:47.045024500Z" />
<EventRecordID>16682</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">30</Data>
<Data Name="BugcheckParameter1">0xffffffffc000001d</Data>
<Data Name="BugcheckParameter2">0xfffff80371c418d9</Data>
<Data Name="BugcheckParameter3">0xffffe001ee18a080</Data>
<Data Name="BugcheckParameter4">0x5f00</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

#3
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 6/19/2016 10:19:31 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: BACKNBLACK
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-06-20T02:19:31.649334900Z" />
<EventRecordID>16736</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>BACKNBLACK</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom