Question PC randomly restarts - error 41 and error 10

Feb 19, 2021
10
0
10
0
Hi everyone

For the last few weeks I've had an issue where my PC suddenly restarts. I've tried looking for clues in event viewer but all I can find are the following:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

The previous system shutdown at 15:00:36 on ‎19/‎02/‎2021 was unexpected.

svchost (14244,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.
I'm on windows 10 - 64bit version 1909
Have 16gb of ram. AMD Ryzen 7 2700x process. GTX 2070 Nvidia. PSU is Corsair TX850M 850 watts.
The BIOS is outdated 08/08/2018 though am reluctant to update as I'm not too sure how to. Though I can if it's advised.

Each time it restarted I was doing something different. Today I was playing a game, yesterday I was on a Zoom call and the time before that it was idle on the desktop.

I tried using the free version of WhoCrashed which summarised the following:


On Mon 05/08/2019 13:49:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20190805-0402.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!WheaConfigureErrorSource+0x5B2E)
Bugcheck code: 0x1A1 (0xFFFFA384C0D7B040, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Though what's interesting is that the time my PC restarted was in fact 15:15, not 13:49. There's a pattern to it as well. It appears to always happen in the afternoon, I work from home so it is on a lot, never had a problem in the day or night. It also appears to always restart twice in the day, with each event being within an hour of each other.

According to event viewer a pattern in the error just before it restarts is:

A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

I've checked over 4 restart events and this is the error that has preceded it each time.
 

Bob.B

Prominent
Feb 8, 2021
577
64
490
8
Hi everyone

For the last few weeks I've had an issue where my PC suddenly restarts. I've tried looking for clues in event viewer but all I can find are the following:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

The previous system shutdown at 15:00:36 on ‎19/‎02/‎2021 was unexpected.

svchost (14244,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.
I'm on windows 10 - 64bit version 1909
Have 16gb of ram. AMD Ryzen 7 2700x process. GTX 2070 Nvidia. PSU is Corsair TX850M 850 watts.
The BIOS is outdated 08/08/2018 though am reluctant to update as I'm not too sure how to. Though I can if it's advised.

Each time it restarted I was doing something different. Today I was playing a game, yesterday I was on a Zoom call and the time before that it was idle on the desktop.

I tried using the free version of WhoCrashed which summarised the following:


On Mon 05/08/2019 13:49:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20190805-0402.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!WheaConfigureErrorSource+0x5B2E)
Bugcheck code: 0x1A1 (0xFFFFA384C0D7B040, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Though what's interesting is that the time my PC restarted was in fact 15:15, not 13:49. There's a pattern to it as well. It appears to always happen in the afternoon, I work from home so it is on a lot, never had a problem in the day or night. It also appears to always restart twice in the day, with each event being within an hour of each other.

According to event viewer a pattern in the error just before it restarts is:

A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

I've checked over 4 restart events and this is the error that has preceded it each time.
Start with have a good backup of all your stuff.
Just in case things go from bad to worse.

Run this...... Speccy - Free Download
Then read this and post a link of the speccy....... Speccy...publish
 
Feb 19, 2021
10
0
10
0
So it just happened again. This is a first for the night time. Again on event viewer showing

1- A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

2- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

3- The previous system shutdown at 21:39:24 on ‎19/‎02/‎2021 was unexpected.
 

Bob.B

Prominent
Feb 8, 2021
577
64
490
8
So it just happened again. This is a first for the night time. Again on event viewer showing

1- A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12

2- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

3- The previous system shutdown at 21:39:24 on ‎19/‎02/‎2021 was unexpected.
Could be a lot of anything.
Power/hardware/software/firmware.
Run a pass of chkdsk with the R option on both disk.
See if it turns up anything.
 
Feb 19, 2021
10
0
10
0
Done, here are the results.

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 ...
Cleaning up instance tags for file 0x3fc1f.
Cleaning up instance tags for file 0x5dd13.
922368 file records processed.
File verification completed.
11478 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
2781 reparse records processed.
1157904 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
2781 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 6731 unused index entries from index $SII of file 0x9.
Cleaning up 6731 unused index entries from index $SDH of file 0x9.
Cleaning up 6731 unused security descriptors.
Security descriptor verification completed.
117769 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
922352 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
68071821 free clusters processed.
Free space verification is complete.

Windows has made corrections to the file system.
No further action is required.

468219903 KB total disk space.
194661232 KB in 380285 files.
261564 KB in 117770 indexes.
0 KB in bad sectors.
1009819 KB in use by the system.
65536 KB occupied by the log file.
272287288 KB available on disk.

4096 bytes in each allocation unit.
117054975 total allocation units on disk.
68071822 allocation units available on disk.

Internal Info:
00 13 0e 00 1d 99 07 00 7c 95 0d 00 00 00 00 00 ........|.......
97 04 00 00 46 06 00 00 00 00 00 00 00 00 00 00 ....F...........

Windows has finished checking your disk.
Please wait while your computer restarts.
 

Bob.B

Prominent
Feb 8, 2021
577
64
490
8
Done, here are the results.

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 ...
Cleaning up instance tags for file 0x3fc1f.
Cleaning up instance tags for file 0x5dd13.
922368 file records processed.
File verification completed.
11478 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
2781 reparse records processed.
1157904 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
2781 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 6731 unused index entries from index $SII of file 0x9.
Cleaning up 6731 unused index entries from index $SDH of file 0x9.
Cleaning up 6731 unused security descriptors.
Security descriptor verification completed.
117769 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
922352 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
68071821 free clusters processed.
Free space verification is complete.

Windows has made corrections to the file system.
No further action is required.

468219903 KB total disk space.
194661232 KB in 380285 files.
261564 KB in 117770 indexes.
0 KB in bad sectors.
1009819 KB in use by the system.
65536 KB occupied by the log file.
272287288 KB available on disk.

4096 bytes in each allocation unit.
117054975 total allocation units on disk.
68071822 allocation units available on disk.

Internal Info:
00 13 0e 00 1d 99 07 00 7c 95 0d 00 00 00 00 00 ........|.......
97 04 00 00 46 06 00 00 00 00 00 00 00 00 00 00 ....F...........

Windows has finished checking your disk.
Please wait while your computer restarts.
Now run it on the seagate disk.
 
Feb 19, 2021
10
0
10
0
This one took forever

Chkdsk was executed in read/write mode.

Checking file system on D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

Stage 1: Examining basic file system structure ...
36096 file records processed. File verification completed.
58 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
990 reparse records processed. 45902 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found. 990 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 85 unused index entries from index $SII of file 0x9.
Cleaning up 85 unused index entries from index $SDH of file 0x9.
Cleaning up 85 unused security descriptors.
Security descriptor verification completed.
4904 data files processed. CHKDSK is verifying Usn Journal...
37955160 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
36080 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
206787694 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976756735 KB total disk space.
149422836 KB in 28185 files.
13896 KB in 4905 indexes.
0 KB in bad sectors.
169223 KB in use by the system.
65536 KB occupied by the log file.
827150780 KB available on disk.

4096 bytes in each allocation unit.
244189183 total allocation units on disk.
206787695 allocation units available on disk.

Just doing the F drive now as the Seagate is partitioned.
 
Feb 19, 2021
10
0
10
0
Okay, here's the last one

Chkdsk was executed in read/write mode.

Checking file system on F:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

Stage 1: Examining basic file system structure ...
57856 file records processed. File verification completed.
65 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
15373 reparse records processed. 58754 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found. 15373 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 77 unused index entries from index $SII of file 0x9.
Cleaning up 77 unused index entries from index $SDH of file 0x9.
Cleaning up 77 unused security descriptors.
Security descriptor verification completed.
450 data files processed. CHKDSK is verifying Usn Journal...
38938216 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
57840 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
170966729 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976755711 KB total disk space.
292679292 KB in 27677 files.
17336 KB in 451 indexes.
0 KB in bad sectors.
192167 KB in use by the system.
65536 KB occupied by the log file.
683866916 KB available on disk.

4096 bytes in each allocation unit.
244188927 total allocation units on disk.
170966729 allocation units available on disk.
 

Bob.B

Prominent
Feb 8, 2021
577
64
490
8
Okay, here's the last one

Chkdsk was executed in read/write mode.

Checking file system on F:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

Stage 1: Examining basic file system structure ...
57856 file records processed. File verification completed.
65 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
15373 reparse records processed. 58754 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found. 15373 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 77 unused index entries from index $SII of file 0x9.
Cleaning up 77 unused index entries from index $SDH of file 0x9.
Cleaning up 77 unused security descriptors.
Security descriptor verification completed.
450 data files processed. CHKDSK is verifying Usn Journal...
38938216 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
57840 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
170966729 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976755711 KB total disk space.
292679292 KB in 27677 files.
17336 KB in 451 indexes.
0 KB in bad sectors.
192167 KB in use by the system.
65536 KB occupied by the log file.
683866916 KB available on disk.

4096 bytes in each allocation unit.
244188927 total allocation units on disk.
170966729 allocation units available on disk.
Well that did not seem to find much.
Run the machine and see if anything changed.
If still bad perhaps dism and sfc might be worth a shot.
I don't have any stick time with either so use google to figure out how to run them.
 
Feb 19, 2021
10
0
10
0
Hi everyone

For the last few weeks I've had an issue where my PC suddenly restarts. I've tried looking for clues in event viewer but all I can find are the following:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

I made sure to adjust the settings so the PC doesn't restart when there's an issue but to no avail.

I'm on windows 10 - 64bit version 1909
Have 16gb of ram. AMD Ryzen 7 2700x process. GTX 2070 Nvidia. My PSU is 850w MSI


Each time it restarted I was doing something different. Today I was playing a game, yesterday I was on a Zoom call and the time before that it was idle on the desktop.

I tried using the free version of WhoCrashed which found nothing. I have formatted my PC and freshly reinstalled W10 - on the latest version. Ran memtest86 which completed 4 passes with no issues. I've updated my BIOS. I've replaced the hard drive with a new NVMe, I've replaced my PSU. At this point, I'm basically building a new PC.
 
Feb 19, 2021
10
0
10
0
I've basically formatted and reinstalled windows on a new NVMe, replaced my PSU and still having this issue. I ran memtest86 and let it complete all cycles which it passed. I'm out of ideas now as to whether it's the graphics card or motherboard. Unfortunately AMD means I have no internal graphics to use to test this out.
 

Bob.B

Prominent
Feb 8, 2021
577
64
490
8
I've basically formatted and reinstalled windows on a new NVMe, replaced my PSU and still having this issue. I ran memtest86 and let it complete all cycles which it passed. I'm out of ideas now as to whether it's the graphics card or motherboard. Unfortunately AMD means I have no internal graphics to use to test this out.
Just for yuks.
Remove the side panel from the case........test
If you have small table fan available point it at the innards.
 
Feb 19, 2021
10
0
10
0
If we're checking temps then can confirm there's no problem there. I've monitored my temps and sits at 40 for cou and 37 for gpu when idle.
 
Feb 19, 2021
10
0
10
0
Have you tried connecting a ups or a different psu? These types of issues can be tricky to diag without spare parts.
Yeah I reconnected everything and replaced my psu with something brand new. It's an MSI 850watts

Before I look to replace my gpu or mobo. Is it possible it could be something to do with the surge protected extension lead?
 

ASK THE COMMUNITY

TRENDING THREADS