Freezing and crashing

Jeka · 24 Aug 2023

Hello,

My PC freezes randomly. Sometimes watching Youtube and sometimes playing CS. I have tried different stress tests and nothing happens, everything is fine and the next day while listetning music or just browsing internet it freezes. I have not found a way to replicate these freezes. Nothing is overclocked except I have XMP profile on and GPUs power and temp limits are maxed out (tried them at stock and still freezes). All my temps are under control, max temp is GPU hotstop around 60-70C and CPU after RMA like 72C on full load and like I said, these freezes happen sometimes when Im just browsing internet so there is no load. I dont get bluesreens just full on freezes and rarely crashes. I have tried the following:

Re-installed Windows two times

Updated BIOS and all possible drivers multiple times

Changed RAM slots

Changed XMP profile 1, 2 and off

Tested RAM with MemTest86 with no errors

Tested RAM with WindowsMemoryDiagnostics with no errors

Changed my SSD slot below GPU

Re-applied CPU thermalpaste

Re-applied GPU thermalpaste

Tested every connection on PSU and motherboard

Turned off Windows core isolation

Changed extension cords

RMA'd CPU (got new one today, crashing but not freezing)

https://1drv.ms/u/s!AoANc1vLS4P7ijpT..._HSQo?e=2E7zyF

ubuysa · 24 Aug 2023

Your system log shows that there is some sort of hardware error on there...

Code:

Event[6256]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-15T11:02:02.5790000Z
  Event ID: 1
  Task: N/A
  Level: Error 
  Opcode: Info  

  Keyword: WHEA Error Event Logs, 
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: JakePC
  Description: 
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

In addition, the application log shows several live kernel events - these are problems from which which Windows recovers. A dump is written to C:\Windows\LiveKernelReports for upload to Microsoft...

Code:

Event[66]
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2023-08-04T22:05:16.7050000Z
  Event ID: 1001
  Task: N/A
  Level: Information 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: WIN-EO3G7E8PS7N
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 15e
P2: 1
P3: ffffa8080970f1a0
P4: ffffa80802dec360
P5: 47
P6: 10_0_22621
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20230804-1205.dmp
\\?\C:\WINDOWS\SystemTemp\WER-35484-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\NDIS-20230804-1205.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ff75447e-e6e5-4573-ac12-d82408b303db.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5240cadb-336d-4f6c-80e8-6ade9ff1ded5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.89eec1bd-80cf-4b53-b229-0a5ace35fae3.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3d6bb816-7958-421f-95e0-3579eaa46d42.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_15e_3c5be826c485fe6c87d774d57297396d5a98fa3_00000000_6135ae17-60a1-4bd8-9cc0-eae0053dd2f7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6135ae17-60a1-4bd8-9cc0-eae0053dd2f7
Report Status: 4
Hashed bucket: 
Cab Guid: 0

The P1 value of 0x15E is the bugcheck code, this one is a BUGCODE_NDIS_DRIVER_LIVE_DUMP indicating that the problem was networking related. The P2 value of 0x1 indicates that the problem was a miniport fatal error (the miniport is Windows representation of the network adapter). This might suggest that the problem lies in your LAN adapter or the driver for it.

It would help if you could navigate to the C:\Windows\LiveKernelReports folder, there may be several sub-folders, visit each sub-folder and upload all dumps you find in there to the cloud with a link to them here (be sure to make it public). You can zip them all up together if you like to make it easier. Note that dumps in LiveKernelRepoorts are deleted automatically once they have been uploaded to Microsoft, so there might be nothing there now.

I might be able to give you more information if you can upload the dump (especially the one in the NDIS sub-folder).

Jeka · 24 Aug 2023

ubuysa said:

Your system log shows that there is some sort of hardware error on there...

Code:

Event[6256]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-15T11:02:02.5790000Z
  Event ID: 1
  Task: N/A
  Level: Error 
  Opcode: Info  

  Keyword: WHEA Error Event Logs, 
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: JakePC
  Description: 
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

In addition, the application log shows several live kernel events - these are problems from which which Windows recovers. A dump is written to C:\Windows\LiveKernelReports for upload to Microsoft...

Code:

Event[66]
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2023-08-04T22:05:16.7050000Z
  Event ID: 1001
  Task: N/A
  Level: Information 
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: WIN-EO3G7E8PS7N
  Description: 
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 15e
P2: 1
P3: ffffa8080970f1a0
P4: ffffa80802dec360
P5: 47
P6: 10_0_22621
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\NDIS\NDIS-20230804-1205.dmp
\\?\C:\WINDOWS\SystemTemp\WER-35484-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\NDIS-20230804-1205.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ff75447e-e6e5-4573-ac12-d82408b303db.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5240cadb-336d-4f6c-80e8-6ade9ff1ded5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.89eec1bd-80cf-4b53-b229-0a5ace35fae3.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3d6bb816-7958-421f-95e0-3579eaa46d42.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_15e_3c5be826c485fe6c87d774d57297396d5a98fa3_00000000_6135ae17-60a1-4bd8-9cc0-eae0053dd2f7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6135ae17-60a1-4bd8-9cc0-eae0053dd2f7
Report Status: 4
Hashed bucket: 
Cab Guid: 0

The P1 value of 0x15E is the bugcheck code, this one is a BUGCODE_NDIS_DRIVER_LIVE_DUMP indicating that the problem was networking related. The P2 value of 0x1 indicates that the problem was a miniport fatal error (the miniport is Windows representation of the network adapter). This might suggest that the problem lies in your LAN adapter or the driver for it.

It would help if you could navigate to the C:\Windows\LiveKernelReports folder, there may be several sub-folders, visit each sub-folder and upload all dumps you find in there to the cloud with a link to them here (be sure to make it public). You can zip them all up together if you like to make it easier. Note that dumps in LiveKernelRepoorts are deleted automatically once they have been uploaded to Microsoft, so there might be nothing there now.

I might be able to give you more information if you can upload the dump (especially the one in the NDIS sub-folder).

There was files only in WHEA folder. Here you go https://1drv.ms/u/s!AoANc1vLS4P7ijuJ...b_UWc?e=NBFtjk

ubuysa · 25 Aug 2023

Those dumps are from 15th August and 24th August and they're identical, they all report a boot error...

Code:

6: kd> !errrec ffffc20150d98020
===============================================================================
Common Platform Error Record @ ffffc20150d98020
-------------------------------------------------------------------------------
Record Id     : 01d9cf4ebffe6c62
Severity      : Fatal (1)
Length        : 28896
fffff8075dc09960: Unable to get Flags value from nt!KdVersionBlock
Creator       : Microsoft
fffff8075dc09960: Unable to get Flags value from nt!KdVersionBlock
Notify Type   : BOOT Error Record
Timestamp     : 8/15/2023 8:01:53 (UTC)
Flags         : 0x00000002 PreviousError

Sadly the WHEA error record is incomplete in these minidumps, that's not unusual. The boot error indication however probably points at the system drive. That would be a more understandable cause of the fatal hardware error log messages.

I would suggest you now do two things:

Download Samsung Magician and run a full diagnostic on your 980 Pro system drive. Look for firmware and/or driver updates there too.
Download the Intel Driver & Support Assistant and use that to look for chipset and LAN driver updates.

Jeka · 25 Aug 2023

ubuysa said:

Those dumps are from 15th August and 24th August and they're identical, they all report a boot error...

Code:

6: kd> !errrec ffffc20150d98020
===============================================================================
Common Platform Error Record @ ffffc20150d98020
-------------------------------------------------------------------------------
Record Id     : 01d9cf4ebffe6c62
Severity      : Fatal (1)
Length        : 28896
fffff8075dc09960: Unable to get Flags value from nt!KdVersionBlock
Creator       : Microsoft
fffff8075dc09960: Unable to get Flags value from nt!KdVersionBlock
Notify Type   : BOOT Error Record
Timestamp     : 8/15/2023 8:01:53 (UTC)
Flags         : 0x00000002 PreviousError

Sadly the WHEA error record is incomplete in these minidumps, that's not unusual. The boot error indication however probably points at the system drive. That would be a more understandable cause of the fatal hardware error log messages.

I would suggest you now do two things:

Download Samsung Magician and run a full diagnostic on your 980 Pro system drive. Look for firmware and/or driver updates there too.
Download the Intel Driver & Support Assistant and use that to look for chipset and LAN driver updates.

SSD seems fine. There were Wifi and Bluetooth drivers updates. Werid cause Asus offers different versions on their site.

ubuysa · 25 Aug 2023

It might well be worth uninstalling the Intel supplied drivers and using the ones from the Asus site. You're using the LAN adapter to connect though aren't you? It might be worth disabling at WiFi adapter and rebooting just to be sure that driver is not installed. I can't be sure which network adapter was causing that 0x15E live kernel event.

Will it freeze in Safe Mode? I appreciate that there's not a great deal you can accomplish in Safe Mode, even in Safe Mode with Networking, but in Safe Mode you're running just the bare bones core of Windows and if it freezes in Safe Mode we can be confident that the cause is hardware. It would be useful to know.