kernel 41 Bug Check 0x116: VIDEO_TDR_ERROR

please help,this has been happening for months now
the pc just goes into sleep mode and then crashes
cant play any game cos of this

amd ryzen 5 1500x quad 3.50ghz
8gb ram ddr4 2400mhz
500w raidmax rx-500xt psu
AsRock AM4 A320M-DGS
rx 470 4gb gc

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 11/26/2018 1:02:10 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
Computer: DESKTOP-JJ9HT42
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="">
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<TimeCreated SystemTime="2018-11-26T00:02:10.178300300Z" />
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Security UserID="S-1-5-18" />
<Data Name="BugcheckCode">278</Data>
<Data Name="BugcheckParameter1">0xffffaa86e649e010</Data>
<Data Name="BugcheckParameter2">0xfffff807719d03a0</Data>
<Data Name="BugcheckParameter3">0xffffffffc0000001</Data>
<Data Name="BugcheckParameter4">0x3</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>

Post was last edited on November 25, 2018 4:34 PM PST

Discussion is locked

Reply to: kernel 41 Bug Check 0x116: VIDEO_TDR_ERROR
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: kernel 41 Bug Check 0x116: VIDEO_TDR_ERROR
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Speccy please.

Post was last edited on November 25, 2018 4:17 PM PST

- Collapse -
thanks for replying

Post was last edited on November 25, 2018 4:26 PM PST

- Collapse -

Seems OK to me, but my fellow mods are better Speccy readers than me. How do you update your drivers? Don't rely on MS for that.

- Collapse -
thanks for replying

thru device manager
-update driver
-search automatically for updated driver software

- Collapse -
- Collapse -
thanks for replying

I turned it off,and i hope its indeed a driver problem cos i spent a bunch on this stuff
thanks for the fast replies mate,cheers and goodnight!

- Collapse -
Last one.

Night mate. Got to go now. Let's wait and see what Bob says.

- Collapse -
The Speccy is showing a failing HDD.

Look at the 01 and 07 values of the Seagate. Now go google your TDR ERROR and see that too often it's the HDD causing that. Plenty of priors about this so I'll stop here.

- Collapse -
thanks for replying

+ System

- Provider

[ Name] Microsoft-Windows-Wininit
[ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
[ EventSourceName] Wininit

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 4

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2018-11-26T18:34:15.734541300Z

EventRecordID 1585


- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer DESKTOP-JJ9HT42


- EventData

Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 194048 file records processed. File verification completed. 22421 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 2347 reparse records processed. 256890 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 2347 reparse records processed. Stage 3: Examining security descriptors ... Cleaning up 1383 unused index entries from index $SII of file 0x9. Cleaning up 1383 unused index entries from index $SDH of file 0x9. Cleaning up 1383 unused security descriptors. Security descriptor verification completed. 31422 data files processed. CHKDSK is verifying Usn Journal... 36495536 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 194032 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 19350222 free clusters processed. Free space verification is complete. Adding 5024 bad clusters to the Bad Clusters File. Windows has made corrections to the file system. No further action is required. 116706303 KB total disk space. 38914784 KB in 128105 files. 81124 KB in 31423 indexes. 20096 KB in bad sectors. 309503 KB in use by the system. 65536 KB occupied by the log file. 77380796 KB available on disk. 4096 bytes in each allocation unit. 29176575 total allocation units on disk. 19345199 allocation units available on disk. Internal Info: 00 f6 02 00 33 6f 02 00 b2 46 04 00 00 00 00 00 ....3o...F...... ac 00 00 00 7f 08 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

i did chkdsk this was the results

- Collapse -
All this won't fix the HDD and TDR issue.

I'm not going to write at length since the HDD and TDR issue is a classic. You will encounter folk that don't believe it. Not much you can do for them.

- Collapse -
Bug check

After you get that bum hdd out of the mix and get that bug check issue sorted.

Not sure how well that method of blocking driver updates that you used works.

Since you have group policy editor on your machine also do this.

Scan down to where it talks about gpe.

Next step.... you have the wrong ram in your machine.
What you want is a 2x4GB @ 2666 kit.
That will get you the proper speed and will enable the dual channel feature.

Next step..... it looks like your ssd is running at sata2 speed.
If so that is not right.

CNET Forums

Forum Info