Windows 10: System hang/freeze randomly for Clevo P950HR laptop

Hi,

I have an Aftershock PRIME-15 laptop from Singapore, which is actually a Clevo P950HR laptop.

I've been getting random system hangs recently and it was quite frustrating as I use it for work. When the system freezes, my mouse and keyboard stops responding (both USB and PS2), and my music/audio goes off. I tried to ping my laptop from another PC, and it seems to be okay. In the end I have to force a system reboot and lose all my work.

After hitting this issue the first time, I have enabled the hotkey to force a BSOD when the system freezes.

Here's the link for the full memory dump file.
MEMORY (3).7z - Google Drive

The minidump file is in the attachment.

Thanks *Smile

:)

 

Laptop - Jack out not working after sleep mode

This is a very common issue with Clevo laptops, if you do a search for "Clevo headphone sleep" it will show you thta probably all Clevo owners suffer the same.

The solution is to install the Clevo Hotkey utility. Reluctantly, but, so far, it solves the issue.

 

No Sound in Windows 10 64bit

It is enabled and I ran update driver "search automatically", it said it was up to date. The only thing I noticed was that under the speaker driver, it says the driver provider is microsoft and the date is 10/29/2015 whereas under the sound, video and game
controller tab, the driver provider is VIA and the date is 12/3/2015.

I didn't buy the laptop directly from Clevo. I bought it from a company that customizes various laptop companies, including Clevo. Laptop had a 3 year warranty (expired now). I did check with them, and they told me that the drivers they get are provided
by Clevo, so if I have any trouble with drivers, I should take it up with Clevo.

Clevo told me that they will not be making drivers for older models which I thought was a bit ridiculous considering that the laptop was barely 2 years old. They're essentially telling me that I need to buy a new laptop every time there is a new operating
system released. I have an even older Dell laptop that is 8 years old and it is running windows 10 flawlessly without any driver issues (realtek sound chipset). The issue is clearly with Clevo/VIA. I contacted VIA and they told me that they only release generic
drivers, and that I need to contact Clevo for working Drivers. So basically, I don't have any driver support.

As mentioned before, if I revert back to Windows 7, the sound comes out of the speakers just fine, so it isn't a hardware issue.

 

Hi zeezee,

Please run driver verifier according to the below settings. I'd like to compare the drivers from the crash dump(s) (assuming any crash occurs) with the flagged drivers from the kernel dump.

Configure Driver VerifierPlease run driver verifier using the following settings for 48 hours.

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Warning: driver verifier can cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

• In normal mode open an administrator command prompt and enter the below command
• In safe mode open an administrator command prompt and enter the below command
• On 3 boot failures, you'll boot automatically to the recovery options,
  • click Troubleshoot
  • go to the advanced options
  • choose command prompt
  • enter the below command
• Boot with the recovery media, see above 4 steps in option 3.
• Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code: verifier /reset[/quote] Crashed when running driver verifier

• Reset driver verifier
• Boot in normal mode if necessary
• Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

What is driver verifier?Driver verifier is a built-in tool that allows to check drivers on what they do.If a driver performs an action that could result in

• security corruption,
• access to data it shouldn't have,
• data corruption in the RAM,
• anything else that could give exceptions

driver verifier catches the driver and crashes the system.

 

Hi axe0,

Thank you for your reply.

I have enabled the settings just now and will let you know the outcome in 48 hours.

Thanks *Smile

 

Hi,

My laptop froze again just now and here is the new memory dump file as attached.

MEMORY (4).7z - Google Drive

Thanks

 

A manually initiated crash wasn't what I hoped for, because it shows many different drivers. With driver verifier I was trying to figure out if those drivers are involved.

Since it does not look to be, please run the below test. As you have 32GB I recommend to reserve a few days for it, or remove either of the sticks. This test will take 1/2 days with 32GB.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Hi axe0,

I have run memtest86 a few weeks ago and found zero errors. I will try to run another time whenever I can.

Yes, I manually initiated the crash because my system froze. My mouse, keyboard and audio goes off, but my network file shares were still accessible. I didn't try to remote desktop into my laptop though.

So far, there were no BSODs caused by Driver Verifier. I still have Driver Verifier on right now, will turn it off tonight by 10:00pm GMT+8.

I don't think I am able to remove the RAM sticks myself as I fear that it may void my warranty. I will check with my reseller for this.

Thanks

 

Hi axe0,

I just encountered another system hang again.

I found that there's one resource having very high contention count. Is this related to the random freezes?

Code: 0: kd> !locks**** DUMP OF ALL RESOURCE OBJECTS **** KD: Scanning for held locks.............................................................................................. Resource @ 0xffffa701f5591260 Shared 1 owning threads Contention Count = 57831 NumberOfExclusiveWaiters = 17 Threads: ffffa701f8b91440-01<*> Threads Waiting On Exclusive Access: ffffa701f9930080 ffffa701f9849080 ffffa701f9554240 ffffa701f9f61080 ffffa7020cb46080 ffffa701f9af4080 ffffa701fc01f080 ffffa701f86c6080 ffffa701f88df080 ffffa702086a2700 ffffa7020d30b080 ffffa701fa0cb040 ffffa702088a8040 ffffa701fbcce080 ffffa7020b5f9040 ffffa7020bf23200 ffffa701fa984340 KD: Scanning for held locks.... Resource @ 0xffffa701f6dca4f0 Exclusively owned Contention Count = 256 Threads: ffffa701f53b6040-01<*> KD: Scanning for held locks.. Resource @ 0xffffa701f6ddc010 Exclusively owned Contention Count = 921386514 NumberOfSharedWaiters = 2 NumberOfExclusiveWaiters = 77 Threads: ffffa70204bab700-01<*> ffffa7020253c080-01 ffffa701f9918700-01 Threads Waiting On Exclusive Access: ffffa701fb57c700 ffffa701f893a080 ffffa701f8877500 ffffa701fae37080 ffffa701fadc6700 ffffa701f8878080 ffffa701f9397080 ffffa701f7b62700 ffffa7020c34b700 ffffa70208487080 ffffa7020d125080 ffffa701f15f0080 ffffa701f08a7080 ffffa7020d304700 ffffa702039ab080 ffffa7020c049080 ffffa701fadb5700 ffffa70208602080 ffffa701fa8db080 ffffa701fb280080 ffffa7020c1e0700 ffffa701feb87700 ffffa701fa171700 ffffa7020c0da080 ffffa702059de700 ffffa70204ac0700 ffffa7020c9ca080 ffffa701f1838700 ffffa7020bfb4080 ffffa7020ce8a600 ffffa701fab52080 ffffa7020c562080 ffffa701fabc5700 ffffa70200f71700 ffffa7020c793080 ffffa7020ca4b080 ffffa7020ca80080 ffffa7020837b700 ffffa70201b48700 ffffa70209cc52c0 ffffa701fbacb080 ffffa70208791080 ffffa7020dd25080 ffffa7020cd9b080 ffffa7020f97e700 ffffa701fa086640 ffffa70204410700 ffffa7020cc10040 ffffa701fb2da700 ffffa7020fdd4080 ffffa7020f969700 ffffa70210779700 ffffa7020c9b0080 ffffa70208093700 ffffa7020b972700 ffffa7020c780080 ffffa701f88e41c0 ffffa701fb5cf080 ffffa702098b1700 ffffa7020fa56080 ffffa701f9c49080 ffffa70206bfa080 ffffa70206aa0080 ffffa7020628b580 ffffa7020fde7080 ffffa7020fb78080 ffffa7020c933080 ffffa701f887c080 ffffa7020dd5e700 ffffa7020784c700 ffffa7020c4e5700 ffffa7020c95b700 ffffa7020d2bc700 ffffa7020c8bf080 ffffa7020d0e2080 ffffa701fae70080 ffffa701fb23b700 KD: Scanning for held locks....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 269089 total locks, 3 locks currently held 0: kd> !locks -v 0xffffa701f6ddc010 Resource @ 0xffffa701f6ddc010 Exclusively owned Contention Count = 921386514 NumberOfSharedWaiters = 2 NumberOfExclusiveWaiters = 77 Threads: ffffa70204bab700-01<*> THREAD ffffa70204bab700 Cid 4d24.371c Teb: 0000007d69942000 Win32Thread: ffffa70203b286a0 WAIT: (WrPushLock) KernelMode Non-Alertable SuspendCount 1 ffffcd8c57e77320 SynchronizationEvent Not impersonating DeviceMap ffff898660a86230 Owning Process ffffa701f0d50300 Image: chrome.exe Attached Process N/A Image: N/A Wait Start TickCount 10120134 Ticks: 26930 (0:00:07:00.781) Context Switch Count 2203265 IdealProcessor: 7 UserTime 00:08:36.375 KernelTime 00:02:33.718 Win32 Start Address 0x00007ff6dedebe30 Stack Init ffffcd8c57e77b90 Current ffffcd8c57e76f20 Base ffffcd8c57e78000 Limit ffffcd8c57e71000 Call 0000000000000000 Priority 15 BasePriority 8 PriorityDecrement 80 IoPriority 2 PagePriority 5 Child-SP RetAddr Call Site ffffcd8c`57e76f60 fffff800`f52bb460 nt!KiSwapContext+0x76 ffffcd8c`57e770a0 fffff800`f52badde nt!KiSwapThread+0x190 ffffcd8c`57e77160 fffff800`f52ba5b9 nt!KiCommitThreadWait+0x10e ffffcd8c`57e77200 fffff800`f5239cdc nt!KeWaitForSingleObject+0x1c9 ffffcd8c`57e772e0 fffff800`f524af7d nt!ExfAcquirePushLockExclusiveEx+0x2ec ffffcd8c`57e773a0 fffff807`89a06822 nt!ExAcquirePushLockExclusiveEx+0x15d ffffcd8c`57e773e0 fffff807`89acae94 dxgkrnl!DXGFASTMUTEX::Acquire+0xa6 ffffcd8c`57e77410 fffff807`89ac4a41 dxgkrnl!DXGGLOBAL::ReferenceAdapterByLuid+0x64 ffffcd8c`57e77450 fffff807`89ac453b dxgkrnl!DxgkIsVirtualizationDisabledForTarget+0x41 ffffcd8c`57e77500 fffff622`0b81f533 dxgkrnl!DxgkDisplayConfigDeviceInfo+0xdb ffffcd8c`57e77900 fffff622`0b81f33a win32kbase!DrvDisplayConfigGetDeviceInfo+0x93 ffffcd8c`57e77940 fffff800`f5389003 win32kbase!NtUserDisplayConfigGetDeviceInfo+0x16a ffffcd8c`57e77a00 00007ffb`dd5a7de4 nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffcd8c`57e77a00) 0000007d`69bfce08 00000000`00000000 0x00007ffb`dd5a7de4 ffffa7020253c080-01 THREAD ffffa7020253c080 Cid 1f0c.37a0 Teb: 0000000000e7e000 Win32Thread: ffffa701fafa7920 WAIT: (WrResource) KernelMode Non-Alertable ffffcd8c56c57858 SynchronizationEvent IRP List: ffffa702039911d0: (0006,04c0) Flags: 00060000 Mdl: 00000000 Not impersonating DeviceMap ffff898660a86230 Owning Process ffffa701f9fc4080 Image: explorer.exe Attached Process N/A Image: N/A Wait Start TickCount 10147060 Ticks: 4 (0:00:00:00.062) Context Switch Count 56151 IdealProcessor: 0 UserTime 00:00:01.437 KernelTime 00:00:01.671 Win32 Start Address 0x00007ffbe0bc42c0 Stack Init ffffcd8c56c57b90 Current ffffcd8c56c573c0 Base ffffcd8c56c58000 Limit ffffcd8c56c51000 Call 0000000000000000 Priority 8 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 Child-SP RetAddr Call Site ffffcd8c`56c57400 fffff800`f52bb460 nt!KiSwapContext+0x76 ffffcd8c`56c57540 fffff800`f52badde nt!KiSwapThread+0x190 ffffcd8c`56c57600 fffff800`f52ba5b9 nt!KiCommitThreadWait+0x10e ffffcd8c`56c576a0 fffff800`f52b85fd nt!KeWaitForSingleObject+0x1c9 ffffcd8c`56c57780 fffff800`f524f6fd nt!ExpWaitForResource+0x6d ffffcd8c`56c57800 fffff800`f525070a nt!ExpAcquireResourceSharedLite+0x43d ffffcd8c`56c578a0 fffff622`0b7f947c nt!ExEnterCriticalRegionAndAcquireResourceShared+0x4a ffffcd8c`56c578e0 fffff622`0b4de0f8 win32kbase!EnterSharedCrit+0x3c ffffcd8c`56c57920 fffff800`f5389003 win32kfull!NtUserGetForegroundWindow+0x38 ffffcd8c`56c57a00 00007ffb`dd5a1804 nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffcd8c`56c57a00) 00000000`1353f818 00000000`00000000 0x00007ffb`dd5a1804 ffffa701f9918700-01 THREAD ffffa701f9918700 Cid 1164.32ac Teb: 0000003296b14000 Win32Thread: ffffa701f0efc6a0 WAIT: (WrResource) KernelMode Non-Alertable ffffcd8c5a1c78f8 SynchronizationEvent Not impersonating DeviceMap ffff898661bcc5b0 Owning Process ffffa7020dcc4580 Image: conhost.exe Attached Process N/A Image: N/A Wait Start TickCount 10147035 Ticks: 29 (0:00:00:00.453) Context Switch Count 390 IdealProcessor: 3 UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address 0x00007ffbc9111480 Stack Init ffffcd8c5a1c7b90 Current ffffcd8c5a1c7460 Base ffffcd8c5a1c8000 Limit ffffcd8c5a1c1000 Call 0000000000000000 Priority 8 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 Child-SP RetAddr Call Site ffffcd8c`5a1c74a0 fffff800`f52bb460 nt!KiSwapContext+0x76 ffffcd8c`5a1c75e0 fffff800`f52badde nt!KiSwapThread+0x190 ffffcd8c`5a1c76a0 fffff800`f52ba5b9 nt!KiCommitThreadWait+0x10e ffffcd8c`5a1c7740 fffff800`f52b85fd nt!KeWaitForSingleObject+0x1c9 ffffcd8c`5a1c7820 fffff800`f524f6fd nt!ExpWaitForResource+0x6d ffffcd8c`5a1c78a0 fffff800`f525070a nt!ExpAcquireResourceSharedLite+0x43d ffffcd8c`5a1c7940 fffff622`0b7f947c nt!ExEnterCriticalRegionAndAcquireResourceShared+0x4a ffffcd8c`5a1c7980 fffff622`0b42e7ac win32kbase!EnterSharedCrit+0x3c ffffcd8c`5a1c79c0 fffff800`f5389003 win32kfull!NtUserNotifyWinEvent+0x2c ffffcd8c`5a1c7a00 00007ffb`dd5a1624 nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffcd8c`5a1c7a00) 00000032`96cff108 00000000`00000000 0x00007ffb`dd5a1624 Threads Waiting On Exclusive Access: ffffa701fb57c700 ffffa701f893a080 ffffa701f8877500 ffffa701fae37080 ffffa701fadc6700 ffffa701f8878080 ffffa701f9397080 ffffa701f7b62700 ffffa7020c34b700 ffffa70208487080 ffffa7020d125080 ffffa701f15f0080 ffffa701f08a7080 ffffa7020d304700 ffffa702039ab080 ffffa7020c049080 ffffa701fadb5700 ffffa70208602080 ffffa701fa8db080 ffffa701fb280080 ffffa7020c1e0700 ffffa701feb87700 ffffa701fa171700 ffffa7020c0da080 ffffa702059de700 ffffa70204ac0700 ffffa7020c9ca080 ffffa701f1838700 ffffa7020bfb4080 ffffa7020ce8a600 ffffa701fab52080 ffffa7020c562080 ffffa701fabc5700 ffffa70200f71700 ffffa7020c793080 ffffa7020ca4b080 ffffa7020ca80080 ffffa7020837b700 ffffa70201b48700 ffffa70209cc52c0 ffffa701fbacb080 ffffa70208791080 ffffa7020dd25080 ffffa7020cd9b080 ffffa7020f97e700 ffffa701fa086640 ffffa70204410700 ffffa7020cc10040 ffffa701fb2da700 ffffa7020fdd4080 ffffa7020f969700 ffffa70210779700 ffffa7020c9b0080 ffffa70208093700 ffffa7020b972700 ffffa7020c780080 ffffa701f88e41c0 ffffa701fb5cf080 ffffa702098b1700 ffffa7020fa56080 ffffa701f9c49080 ffffa70206bfa080 ffffa70206aa0080 ffffa7020628b580 ffffa7020fde7080 ffffa7020fb78080 ffffa7020c933080 ffffa701f887c080 ffffa7020dd5e700 ffffa7020784c700 ffffa7020c4e5700 ffffa7020c95b700 ffffa7020d2bc700 ffffa7020c8bf080 ffffa7020d0e2080 ffffa701fae70080 ffffa701fb23b700 1 total locks [/quote] Will run the memtest86 over the weekend.

Thanks

 

They are related, but not relevant.
Most of them are threads from the same process, after waiting for the lock to be freed they swap the context when the system crashes.

 

Hi axe0,

Here's the memtest result.





Thanks

 

Check the scheduled tasks (search tasksch.msc) to see if there were any tasks running at the time of the freeze.

 

Hi,

I encountered the hang again yesterday.

As this occurred outside of a working day, I decided to observe for how long the hanging will persist.

After I came back from my 30 minutes walk, surprisingly the laptop stopped hanging.

Any idea on what is the root cause for this?

Thanks