[SOLVED] Freezing for 2-3s and then back to normal. Event viewer shows this message, what does it mean?

[MatevžKočevar]

Hi,
so my computer has been having this random problem of freezing for a short amount of time and then going back to functioning normally. I decided to track this and had event viewer ready when it happened again. The message showed at the exact time of the freeze and here it is: (If someone can help with what it means it would mean a lot)

Source: Windows Error Reporting, Event ID: 1001, Level: Information

Problem signature:
P1: 117
P2: ffff8008b69b8010
P3: fffff80051c72610
P4: 0
P5: 49c
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200527-1300.dmp
\\?\C:\WINDOWS\TEMP\WER-3247906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA20E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA21E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA22D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA24D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_390d951e5263601cd02f9494ac859f3e5d9d10_00000000_cab_5007c78d-d070-4e84-92ee-692de8320888

Analysis symbol:
Rechecking for solution: 0
Report Id: 5007c78d-d070-4e84-92ee-692de8320888
Report Status: 2049
Hashed bucket:
Cab Guid: 0

 

[Vyrvelata]

That error report doesn't say much (at least for me).
If you ask me its power related, check your PSU cables inside the case if they are properly connected and if there is some cable witch is not suppose to be how it is (it should be visible).

Also if you have the opportunity try different PSU.

 

[MatevžKočevar]

That error report doesn't say much (at least for me).
If you ask me its power related, check your PSU cables inside the case if they are properly connected and if there is some cable witch is not suppose to be how it is (it should be visible).

Also if you have the opportunity try different PSU.

Will check again but am not that confident I will find anything unusual since I have double checked everything before. Thank you still for your answer.

 

[howtobeironic]

In one more, event 1001 is a system hang logged. Might be PSU, might be a faulty program. Suspecting a program is more likely though. Now, try going to the path below the line These files may be available here: (copy and paste in the address bar of the file explorer) and examine if there are any logs there. Also, run msinfo32 (Win+R, then type msinfo32 there), expand the Software Environment list, and choose "Windows Error Reporting". See it there. You're looking for lines The application XXXX... or Faulting application name: XXXX.... The WER system logs every Not Responding, so there will be plenty. What are you looking for is a specific pattern (program name or matching codes on things) around the time of hangs.

 

[MatevžKočevar]

In one more, event 1001 is a system hang logged. Might be PSU, might be a faulty program. Suspecting a program is more likely though. Now, try going to the path below the line These files may be available here: (copy and paste in the address bar of the file explorer) and examine if there are any logs there. Also, run msinfo32 (Win+R, then type msinfo32 there), expand the Software Environment list, and choose "Windows Error Reporting". See it there. You're looking for lines The application XXXX... or Faulting application name: XXXX.... The WER system logs every Not Responding, so there will be plenty. What are you looking for is a specific pattern (program name or matching codes on things) around the time of hangs.

The path doesn't even exist in file explorer somehow and the msinfo32 doesn't tell anything about any errors at the time of freezing. I don't know what to do sincerely. These freezes are getting pretty annoying.

 

[howtobeironic]

This is odd, have you tried going to the path C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ and look for the stated folder? It should have a .wer file inside with even more info.

 

[MatevžKočevar]

This is odd, have you tried going to the path C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ and look for the stated folder? It should have a .wer file inside with even more info.

Yeah, I been looking for that folder for about 15 minutes and I couldn't find it on my C drive. It literally doesn't exist. Not much more I can say here...

 

[howtobeironic]

Try turning "show hidden and protected system files" on folder options. We can't possibly get deeper on the cause without these files. https://www.technipages.com/show-hidden-files-windows

 

[MatevžKočevar]

Try turning "show hidden and protected system files" on folder options. We can't possibly get deeper on the cause without these files. https://www.technipages.com/show-hidden-files-windows

Found the files now thanks to your suggestion on "show hidden files". There is only one file in the stated folder though, it's a .wer file as well and I don't have a program to open it.
Also it doesn't seem that promising that this file actually shows anything useful tho. I think it is just a saved version of what I posted above. But I might be wrong still. The name of the file is Report.wer

 

[howtobeironic]

You should be able to open a .wer file using Notepad.

 

[MatevžKočevar]

You should be able to open a .wer file using Notepad.

Oh, well thank you for that information😅. So yeah I think I found out the cause is my hardware now I just need to know which part of my PC isn't working as it should. Here is the file's content as well:


Version=1
EventType=LiveKernelEvent
EventTime=132350508099772859
ReportType=4
Consent=1
ReportStatus=2049
ReportIdentifier=5007c78d-d070-4e84-92ee-692de8320888
Wow64Host=34404
NsAppName=LiveKernelEvent
OriginalFilename=WerFault.exe
AppSessionGuid=00000000-0000-0000-0000-000000000000
BootId=35
IsFatal=4294967295
EtwNonCollectReason=1
Response.type=4
Sig[0].Name=Code
Sig[0].Value=117
Sig[1].Name=Parameter 1
Sig[1].Value=ffff8008b69b8010
Sig[2].Name=Parameter 2
Sig[2].Value=fffff80051c72610
Sig[3].Name=Parameter 3
Sig[3].Value=0
Sig[4].Name=Parameter 4
Sig[4].Value=49c
Sig[5].Name=OS version
Sig[5].Value=10_0_18363
Sig[6].Name=Service Pack
Sig[6].Value=0_0
Sig[7].Name=Product
Sig[7].Value=256_1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18363.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=8192
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18363
OsInfo[3].Key=ubr
OsInfo[3].Value=836
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=2057
OsInfo[7].Key=geoid
OsInfo[7].Value=212
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=34704
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.836.18362.0-11.0.190
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16313
OsInfo[19].Key=svolsz
OsInfo[19].Value=446
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.836.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=74a72ef3-2f77-42d7-844f-c3bce51e2339
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=FX:1180989E,FX:1190030E
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].CabName=WATCHDOG-20200527-1300.dmp
File[0].Path=WATCHDOG-20200527-1300.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200527-1300.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-3247906-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-3247906-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERA20E.tmp.WERInternalMetadata.xml
File[2].Flags=851970
File[2].Type=5
File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA20E.tmp.WERInternalMetadata.xml
File[3].CabName=WERInternalRequest.xml
File[3].Path=WERA21E.tmp.xml
File[3].Flags=851970
File[3].Type=5
File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA21E.tmp.xml
File[4].CabName=memory.csv
File[4].Path=WERA22D.tmp.csv
File[4].Flags=589826
File[4].Type=5
File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA22D.tmp.csv
File[5].CabName=sysinfo.txt
File[5].Path=WERA24D.tmp.txt
File[5].Flags=589826
File[5].Type=5
File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA24D.tmp.txt
File[6].CabName=Report.zip
File[6].Path=Report.zip
File[6].Flags=65536
File[6].Type=11
File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
Ns[0].Name=stopcode
Ns[0].Value=00000117
Ns[1].Name=p1
Ns[1].Value=FFFF8008B69B8010
Ns[2].Name=p2
Ns[2].Value=FFFFF80051C72610
Ns[3].Name=p3
Ns[3].Value=0000000000000000
Ns[4].Name=p4
Ns[4].Value=000000000000049C
FriendlyEventName=Hardware error
ConsentKey=LiveKernelEvent
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
ReportDescription=A problem with your hardware caused Windows to stop working correctly.
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=-832200865

 

[johnbl]

Video card not responding within the watchdog time out interval. This would normally bugcheck the machine but window would attempt to reset the pci bus to recover and reset the video card to prevent the bugcheck. Look for common. Video card problems ( remove overclock, check temps, check power, update video drivers)

 

[MatevžKočevar]

Video card not responding within the watchdog time out interval. This would normally bugcheck the machine but window would attempt to reset the pci bus to recover and reset the video card to prevent the bugcheck. Look for common. Video card problems ( remove overclock, check temps, check power, update video drivers)

My GPU (1660 Ti) was never being overclocked, I check the temps and they sit at 33 celcius/93 F. Also the power is connected the way it should be and the latest driver is also installed... Might as well add the voltage which sits at 0.656V

 

[howtobeironic]

I might advise checking it out by hand as well. Sometimes it doesn't fit so well but seems like it does.

 

[MatevžKočevar]

I might advise checking it out by hand as well. Sometimes it doesn't fit so well but seems like it does.

Ok, I have now checked everything regarding the video card. I took it out, air-sprayed it and the slot and then put it back in. Also installed some extra screws in the back of the case so it's even more stable in there. After 1.5 days the screen froze again just now. But with that said I have noticed that everytime my PC is left open without the side panels of the case installed, the freezes stop for a day or two. Could it be I have too little air flow within my machine? And would extra fans help with that

 

[howtobeironic]

Hm, interesting, you should try to check the CPU/GPU temperature under stress. Use a game you know the PC works hard on or CINEBENCH and monitor the temps using HWInfo. Should ideally be under 100 degrees celcius on full load.

 

[MatevžKočevar]

Hm, interesting, you should try to check the CPU/GPU temperature under stress. Use a game you know the PC works hard on or CINEBENCH and monitor the temps using HWInfo. Should ideally be under 100 degrees celcius on full load.

So I just ran the CINEBENCH test (as much as I understand it's used for CPU benchmarking) and while the noise was quite loud the CPU had no problem with the test only reaching 60 Celcius.
On the second note, I do have another PC at home with rather fine specs and I know it is working well. Is it safe to switch the CPU from this computer with the other one to see how that turns out? (they are both Intel's)

 

[howtobeironic]

Only 60 celcius is a good temperature, but let's extend that a bit. What will we be testing will be really heaving on power, and it will heat up A LOT. Follow these:http://www.playtool.com/pages/prime95/prime95.html or https://appuals.com/how-to-run-a-cpu-stress-test-using-prime95/ to do a torture test with in-place large FFT's. Run as long as your commonsense stops it or for a few hours, whichever comes first. Check the temps with it as well.

You might be able to try the CPU out, but the mobo's need to have the same socket and you will have to rebuild both PC's. Also you will need isopropyl alcohol(pure) and thermal paste.

 

[howtobeironic]

Also, make sure that you trust that PSU before starting.