System freezes when idle

[ubuysa]

The two kernel dumps are both for the manually induced crash and are thus of no use in debugging your original freezing issue.

The system logs are very sparse too. All I can see is a problem starting SysMain (what used to be SuperFetch) but that's not causing your problems. There are a couple of NetBIOS devices that couldn't start because of name conflicts (are you sharing printers or drivers at all?) these might possibly be related to your freezing problem.

There are also 'dump file creation failed' errors from volmgr, and this is possibly why you're not getting kernel dumps. The causes for this are varied, check first that the volume (HarddiskVolume4) is not too full, then open an elevated command prompt or PowerShell session and enter the command dism /online /cleanup-image /scanhealth. If that reports no corruptions then that's good. If it reports corruptions found but which are repairable then enter the command dism /online /cleanup-image /restorehealth. If that command reports errors found then a reinstall of Windows is needed. If the dism command runs clean or if the restorehealth runs clean then enter the command sfc /scannow. If that reports no errors found then that's good. If it reports errors found and repaired then just reboot. If it reports errors found and not corrected then a reinstall of Windows is needed. In addition, if you're running any tune-up tools ensure they are not deleting the dump file or preventing its creation (these kinds of tools are best avoided in any case).

The application logs are pretty sparse too. There are a bunch of failures to start the EapHost service - this is the Extensible Authentication Protocol which provides network authentication services mainly used for VPNs. I can also see RAS (Remote Access Services) failures for the PureVPN service, so all these failures are related to a VPN via the PureVPN product.

There are also two application errors, one for Firefox in a Mozilla module - so that can be put down to Firefox. The other is a failure of Aac3572MbHal_x86.exe, which is a component of Asus Aura.

Not very conclusive I'm afraid. I would investigate my suggestions for the 'dump file creation failed' errors, you want it creating dumps after all. I would also investigate the NetBIOS issues too.

 

[macjim]

Image is clean:

PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.804

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

I'm going to run memtest today and swap out the Orig RAM for the new RAM, to see if that's the issue.

 

[ubuysa]

Image is clean:

PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.804

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

I'm going to run memtest today and swap out the Orig RAM for the new RAM, to see if that's the issue.

Run sfc /scannow too.

It might be a RAM issue.

 

[macjim]

Run sfc /scannow too.

It might be a RAM issue.

Clean too
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[ubuysa]

How full is HarddiskVolume4? If you open Disk Management (right-click on the start icon at bottom left and select Disk Management from the menu) HarddiskVolume4 will be listed as Disk 4 in the graphical display in the lower pane there.

 

[macjim]

My current disk setup

Disk 0 - 216 GB free of 464 GB - Firecuda SSD (PCS orig)
Disk 1 - 471 GB free of 1.81 TB - Seagate Baracuda HDD (Internal) ( Added from old PC)
Disk 2 - 251 GB free of 1.81 TB - Seagate Baracuda HDD (Internal) ( Added from old PC)
Disk 3 - 101 GB free of 465 GB - Samsung 850 EVO SSD ( Added from old PC)
Disk 4 - 304 GB free of 1.81 GB - Seagate Baracuda HDD, disk is from Old PC but no slots left on new PC - it sits in a USB3 docking station

https://www.amazon.co.uk/gp/product/B00IS7Y96I/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

[ubuysa]

Hmmm. I have no idea why you're getting 'dump file creation failed' errors then.

When all else fails check the RAM...

Does it freeze with only two RAM sticks inserted or only with all four?

 

[macjim]

Hmmm. I have no idea why you're getting 'dump file creation failed' errors then.

When all else fails check the RAM...

Does it freeze with only two RAM sticks inserted or only with all four?

Both, it started with 4 sticks, but also occurs with 2 sticks.

I've been running with the 2 orignal PCS sticks, and it freezes - ran Memtest86 - no issue.

I've swapped in the other two sticks I bought from Amz and I'll see how stable that is.

 

[macjim]

An update on my fun and games:

Still getting a PC freeze, which needs a hard reboot. Still only got 2x 8 GB sticks in PC.

I track the freezes by the Event 41 in the event View:

Level	Event ID	Date and Time	Cause?
Critical	41	24/02/2021 08:40	Freeze
Critical	41	24/02/2021 13:14	Freeze

24 Feb Scanned the forum and noticed it was recommended that Nvidia Audio driver with Realtek, so un-installed the Nvidia driver.

Critical	41	26/02/2021 07:52	False morning boot up
Critical	41	26/02/2021 12:52	Freeze
Critical	41	27/02/2021 17:56	Logitech Gaming & MemTest64 BSOD

Found Memtest64, I could run it within windows for more than 4 loops, managed to crash into a BSOD but it tracked back to a logitech gaming software, I don't think it relevant as I was thrashing PC when it fell over

1 March checked the system driver, noticed it was using generic windows ones, I installed the AMD Chipset drivers.

March 1, 2 ran Memtest64 for 8 hrs both days without issues.

Critical	41	03/03/2021 18:12	Freeze
Critical	41	04/03/2021 21:08	Playing Crysis 2 and it took PC down - no hard reboot needed
Critical	41	06/03/2021 20:05	Freeze

Changed memory to 3533 MHz

Critical	41	07/03/2021 09:43	Freeze
Critical	41	08/03/2021 08:48	Freeze
Critical	41	08/03/2021 19:13	Freeze
Critical	41	09/03/2021 08:32	Freeze
Critical	41	09/03/2021 14:15	Freeze

After today event changed Memory to 2400 MHz.

At this point I'm at a loss, either a full re-install of windows or a BIOS change, need to speak to PCS before I go down the BIOS route.

A number of new BIOS have this against them:

Version 2407
2020/07/03 18.72 MBytes
TUF GAMING X570-PLUS BIOS 2407
"Improved system performance and compatibility
Improved DRAM compatibility
Update AM4 combo V2 PI 1.0.0.2"

I'm on 1405 Bios.

 

[ubuysa]

Call PCS and ask about the new BIOS version.

If you'd care to export your System and Application logs as .evtx files I'll take a look.

 

[macjim]

Thanks, I'll call them to see what they say.

I've saved the MEMORY.DMP, event & Appl logs form the 27 Feb crash - But I Think I was trying to do too much with memTest64 running, files are here: https://1drv.ms/u/s!AoUU74i2sEO7rlbdy9er6lLXRO4_?e=ljrXeq

The current Event App & Sys files are here: https://1drv.ms/u/s!AoUU74i2sEO7rlVkkBkK9trIOIon?e=tA1rt0

 

[ubuysa]

Thanks, I'll call them to see what they say.

I've saved the MEMORY.DMP, event & Appl logs form the 27 Feb crash - But I Think I was trying to do too much with memTest64 running, files are here: https://1drv.ms/u/s!AoUU74i2sEO7rlbdy9er6lLXRO4_?e=ljrXeq

The current Event App & Sys files are here: https://1drv.ms/u/s!AoUU74i2sEO7rlVkkBkK9trIOIon?e=tA1rt0

The kernel dump is a SYSTEM_SERVICE_EXCEPTION stop code, which is almost always a driver. In this case the dump is very (unequivocally even) clear that the driver in question is ladfGSS.sys, which is a Logitech driver.

In my experience Logitech make great hardware and simply awful software. I'm not sure what Logitech product that driver is for, though it seems to be related to a Logitech headset? If there is any way to run your Logitech devices using the built-in Windows drivers you'll find it much more stable and reliable.

I can also see several Symantec drivers in the dump. What Symantec product are you running? It doesn't look like Norton? Symantec don't have a particularly good reputation (like Logitech really) and unless you really need this product I would uninstall it.

In your System log there are two WHEA failures. WHEA is the Windows Hardware Error Architecture and these report a hardware issue. The error they are reporting is identical to the error that those suffering from the AMD and 4 RAM sticks issue see.



I really would contact PCS and see whether the updated BIOS addresses this issue.

 

[macjim]

Thanks

I use Norton Antivirus

Logitech is a wired Keyboard( G15 I've had for the last three PC's ), Wireless Mouse & Wireless Headset

I'll bin the Logitech software and contact PCS.

 

[ubuysa]

Thanks

I use Norton Antivirus

Logitech is a wired Keyboard( G15 I've had for the last three PC's ), Wireless Mouse & Wireless Headset

I'll bin the Logitech software and contact PCS.

Please bin Norton as well. The keyboard should work with standard Windows drivers but you'll likely lose the customisation options.

 

[macjim]

Just a bit of an update.

I sent my questions to PCS, it did take a few weeks to get a reply and after a lot of back and forth between myself and PCS, they agreed I should update the BIOS. It was suggested I could RMA the PC, but I didn't think that would really help wit such a random fail.

I've just flashed the BIOS from 1405 to 3603, which appears to be the latest release.

I've kept the 2x original PCS RAM sticks installed, and I'll see the stabilty of the system. If it remains stable for a few weeks I'll think about adding the other two stick back in.

The system had been reasonably stable, down to one freeze every 5 or 6 dasy, but then froze twice with 1 hr on Wednesday

Thanks for all the help and here's hoping.

Jim

 

[macjim]

It's been almost 3 weeks since I upgraded the BIOS. Still running only 2x 8GB sticks @3600 MHz

I was clean for 10 days before the first freeze happened, then one approx every 3 days e.g.

Critical	28/04/2021 10:04​	Microsoft-Windows-Kernel-Power	41​
Critical	25/04/2021 12:34​	Microsoft-Windows-Kernel-Power	41​
Critical	22/04/2021 19:40​	Microsoft-Windows-Kernel-Power	41​
Critical	19/04/2021 11:30​	Microsoft-Windows-Kernel-Power	41​
Critical	18/04/2021 09:12​	Microsoft-Windows-Kernel-Power	41​

I've been running the system for 10 -12 hrs most days, left it running for 40 hrs with no issue.

The chances of sending this back to PCS for a RMA and them trying to solve the problem appear remote, it's probably something I'm going to have to live with.

 

[ubuysa]

It's been almost 3 weeks since I upgraded the BIOS. Still running only 2x 8GB sticks @3600 MHz

I was clean for 10 days before the first freeze happened, then one approx every 3 days e.g.

Critical	28/04/2021 10:04​	Microsoft-Windows-Kernel-Power	41​
Critical	25/04/2021 12:34​	Microsoft-Windows-Kernel-Power	41​
Critical	22/04/2021 19:40​	Microsoft-Windows-Kernel-Power	41​
Critical	19/04/2021 11:30​	Microsoft-Windows-Kernel-Power	41​
Critical	18/04/2021 09:12​	Microsoft-Windows-Kernel-Power	41​

I've been running the system for 10 -12 hrs most days, left it running for 40 hrs with no issue.

The chances of sending this back to PCS for a RMA and them trying to solve the problem appear remote, it's probably something I'm going to have to live with.

Can you upload the system and application logs please? The error 41 just indicates that Windows didn't shutdown properly, it's got nothing at all to do with power. It really just means "the kernel detected that the power went off unexpectedly", nothing else.

https://www.pcspecialist.co.uk/forums/threads/when-youre-seeking-help-with-a-bsod.71885/#post-568901

 

[macjim]

Yeah I track the hard re-boots by Event 41.

The App & Sys logs are zipped here: https://1drv.ms/u/s!AoUU74i2sEO7rl1Yg4dxV_UTocPV?e=YZ13gi

Thanks

 

[ubuysa]

It looks like you have a drive failure with whatever device is Disk 5. There is a slew of errors for this disk like this one....


That may be the root cause of a virtual memory shortage, it seems your paging file is too small...


I suggest you run a chkdsk on whichever drive is Drive 5 (use Disk Management to find out). If it's an SSD use chkdsk /f and if it's an HDD use chkdsk /r).

Also set your paging file size to be system managed.

 

[macjim]

Ah, that's my K: drive - a 32Gb Sandisk Thrumb drive.

I have a KVM which I use to share my Mouse, Keyboard & this drive with my Desktop(PCS) & my work laptop.

I assume when I switch to the laptop using the KVM, the drive goes missing in the PC system & that's why it complains.

K:\>chkdsk /f

The type of the file system is NTFS.
Cannot lock current drive.

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) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is E220D Map Update.

Stage 1: Examining basic file system structure ...
1024 file records processed.
File verification completed.
Phase duration (File record verification): 48.70 milliseconds.
0 large file records processed.
Phase duration (Orphan file record recovery): 0.25 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.23 milliseconds.

Stage 2: Examining file name linkage ...
24 reparse records processed.
1146 index entries processed.
Index verification completed.
Phase duration (Index verification): 68.68 milliseconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 0.46 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.94 milliseconds.
24 reparse records processed.
Phase duration (Reparse point and Object ID verification): 0.96 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 10.00 milliseconds.
62 data files processed.
Phase duration (Data attribute verification): 0.47 milliseconds.
CHKDSK is verifying Usn Journal...
381864 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 14.93 milliseconds.

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

30044143 KB total disk space.
20698024 KB in 515 files.
264 KB in 63 indexes.
0 KB in bad sectors.
43887 KB in use by the system.
41152 KB occupied by the log file.
9301968 KB available on disk.

4096 bytes in each allocation unit.
7511035 total allocation units on disk.
2325492 allocation units available on disk.
Total duration: 147.07 milliseconds (147 ms).

Paging file is 28.7 GB, managed by the system e.g.