BSOD

IceX

IceX

Arch-Supremacy Member
Joined
Oct 30, 2001
Messages
13,256
Reaction score
914
I've been having random BSODs for the past 2 months probably 1-2 times per week.

How can I determine what is the issue?

This was my windows error message after it auto rebooted.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800A1982D0
BCP2: FFFFF8800440F7F8
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082317-11138-01.dmp
C:\Users\User\AppData\Local\Temp\WER-16192-0.sysdata.xml
 
shiroyuki03

shiroyuki03

Senior Member
Joined
Jun 27, 2010
Messages
1,293
Reaction score
0
IceX said:
I've been having random BSODs for the past 2 months probably 1-2 times per week.

How can I determine what is the issue?

This was my windows error message after it auto rebooted.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800A1982D0
BCP2: FFFFF8800440F7F8
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\082317-11138-01.dmp
C:\Users\User\AppData\Local\Temp\WER-16192-0.sysdata.xml
Click to expand...

to know what exactly causes the BSOD, you will have to upload this file from this path ( C:\Windows\Minidump\082317-11138-01.dmp) and let the forumers analyze.
 
IceX

IceX

Arch-Supremacy Member
Joined
Oct 30, 2001
Messages
13,256
Reaction score
914
it says i do not have permission to open the file.

There's only 1 user account in my pc..
 
IceX

IceX

Arch-Supremacy Member
Joined
Oct 30, 2001
Messages
13,256
Reaction score
914
cybertech said:
Goto this page and upload the dmp file will show instant result.
Click to expand...

uploaded the file and below is the log:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03297750
Debug session time: Fri Sep 1 12:12:14.798 2017 (UTC - 4:00)
System Uptime: 0 days 0:04:24.626
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009c62010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880044587f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
atikmpag+f7f8
fffff880`044587f8 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`06136888 fffff880`0452b388 : 00000000`00000116 fffffa80`09c62010 fffff880`044587f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`06136890 fffff880`0452b092 : fffff880`044587f8 fffffa80`09c62010 fffffa80`080e5d50 fffffa80`0719d410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061368d0 fffff880`1154bfcb : fffffa80`09c62010 00000000`00000000 fffffa80`080e5d50 fffffa80`0719d410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06136900 fffff880`11575d45 : 00000000`ffffffff 00000000`00003f55 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061369e0 fffff880`1157448b : 00000000`00000102 00000000`00000004 00000000`00003f55 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06136a10 fffff880`115472f2 : ffffffff`ff676980 fffffa80`0719d410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06136ab0 fffff880`1157404a : 00000000`00000000 fffffa80`06caa940 00000000`00000080 fffffa80`0719d410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06136bc0 fffff800`03360152 : 00000000`fffffc32 fffffa80`07af7b50 fffffa80`06676b10 fffffa80`07af7b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06136c00 fffff800`030b6926 : fffff880`02f65180 fffffa80`07af7b50 fffff880`02f6ffc0 fffffa80`0706c180 : nt!PspSystemThreadStartup+0x5a
fffff880`06136c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+f7f8
fffff880`044587f8 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+f7f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5971306e

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
 
shiroyuki03

shiroyuki03

Senior Member
Joined
Jun 27, 2010
Messages
1,293
Reaction score
0
IceX said:
uploaded the file and below is the log:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03297750
Debug session time: Fri Sep 1 12:12:14.798 2017 (UTC - 4:00)
System Uptime: 0 days 0:04:24.626
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009c62010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880044587f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
atikmpag+f7f8
fffff880`044587f8 4883ec28 sub rsp,28h

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`06136888 fffff880`0452b388 : 00000000`00000116 fffffa80`09c62010 fffff880`044587f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`06136890 fffff880`0452b092 : fffff880`044587f8 fffffa80`09c62010 fffffa80`080e5d50 fffffa80`0719d410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061368d0 fffff880`1154bfcb : fffffa80`09c62010 00000000`00000000 fffffa80`080e5d50 fffffa80`0719d410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06136900 fffff880`11575d45 : 00000000`ffffffff 00000000`00003f55 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`061369e0 fffff880`1157448b : 00000000`00000102 00000000`00000004 00000000`00003f55 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06136a10 fffff880`115472f2 : ffffffff`ff676980 fffffa80`0719d410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06136ab0 fffff880`1157404a : 00000000`00000000 fffffa80`06caa940 00000000`00000080 fffffa80`0719d410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06136bc0 fffff800`03360152 : 00000000`fffffc32 fffffa80`07af7b50 fffffa80`06676b10 fffffa80`07af7b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06136c00 fffff800`030b6926 : fffff880`02f65180 fffffa80`07af7b50 fffff880`02f6ffc0 fffffa80`0706c180 : nt!PspSystemThreadStartup+0x5a
fffff880`06136c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+f7f8
fffff880`044587f8 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+f7f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5971306e

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
Click to expand...

as you can see. its a graphic card issue. refer to those in bold. you might want to try reinstalling the driver and see if it works. otherwise, it might be possible gpu uplorry.
 
cybertech

cybertech

Arch-Supremacy Member
Joined
Dec 3, 2000
Messages
16,590
Reaction score
1,561
TS, check your graphic card is the gpu fan spinning?
I have seen and solved many BSOD because of the GPU fan not spinning.
If it is onboard display card, then it could be drivers issue as mentioned in the above post.
 
You must log in or register to reply here.
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top