Random BSOD or just Freeze/Reboot

IDisposable

Member
Joined
Jan 5, 2021
Posts
8
Seems to happen mostly when my USB-attached WebCam is in use but happens other times. After a clean reboot, I regularly get a one-time lag on the mouse pointer (e.g. stops responding for a couple seconds and then everything goes)... I think I've got a USB controller issue. I've tried getting all drivers current (using manufacturer's drivers if more recent)

PowerSpec 1530
  • Clevo / PowerSpec (MicroCenter house brand)
  • Laptop
  • 1530 / PB50DF2
  • Windows 11 Pro Build 22635 (but for MANY builds before as well)
  • x64
  • Windows 11 clean install from USB (cleared all partitions first)
  • Full retail
  • 2.5 years old
  • Intel i7-10875H
  • 32MB (as installed by PowerSpec)
  • NVidia GeForce RTX Super (Mobile)
  • Only using Windows Defender (nothing else)
Speccy http://speccy.piriform.com/results/vtPy5HlBLio76pXXYLa8PUF
 

Attachments

I suggest checking for USB controller driver updates, or disabling and re-enabling the USB controller. Also, mb it will be effective to connect the webcam to a different USB port.

Another recommendation is to disconnect all other USB devices, and close any unnecessary programs and tabs. If the problem persists, there may be a hardware problem with the USB controller itself.
 
Hello and welcome to the forum!

There are no dumps in the upload but there is no indication in your System log of any BSODs, there are many unexpected shutdowns or crashes however. What there is in your System log are a lot of errors for your fingerprint reader...
Code:
Event[1153]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-24T14:22:33.7960000Z
  Event ID: 1
  Task: Driver
  Level: Error
  Opcode: General
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
An operation has failed (0xA, 0x0, 0x0, 0x0).
ScReadWrite: Failed to write request.
HResult: A device which does not exist was specified.

Event[1219]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-23T23:41:27.0850000Z
  Event ID: 10
  Task: Driver
  Level: Error
  Opcode: Ioctl
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
Request[0](CLS=0x0,INS=0xCB,P1=0x2F,P2=0x1,Lc=2,Le=256,.NETServiceMethod=0x0)

Event[1220]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-23T23:41:27.0850000Z
  Event ID: 1
  Task: Driver
  Level: Error
  Opcode: General
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
An operation has failed (0x0, 0x0, 0x0, 0x0).
ScT1Transmit: Failed to send request.
HResult: A device which does not exist was specified.
Those are just a few. The WudfUsbccidDriver.dll driver is a Microsoft driver that manages your fingerprint reader, and as its name suggests this is a USB type device - this may well be the source of what you suspect are USB problems.

Do you use the fingerprint reader? If not then it would be wise to disable it. If you do use it then first check with the system integrator (PowerSpec?) to see whether they have an updated driver for it, or check on the Clevo download site for your model to see whether there is an updated driver available there. If neither of those have a suitable driver then run Windows Update, click on 'View optional updates', expand the Driver Updates section, and see whether there is a fingerprint reader driver available in there.

If you can't find an updated driver then I would disable the fingerprint reader as a test, and see whether the problem resolves.

One other USB related issue I note is that you don't have a driver installed for your Razer Huntsman Elite keyboard...
Code:
RzVirt_01    RZVIRTUAL\VID_1532&PID_0226&MI_00&COL03\8&209DFDC1&0&01    The drivers for this device are not installed.
Is that intentional? It will use the Windows keyboard driver of course so this may not be an issue at all.

In addition, although there are no BSOD bugcheck entries logged in your System log there are several errors reporting that dump file creation failed. It is important that your system is configured to write dumps, to do that ALL of the following must be true...
  • The page file must be on the same drive as your operating system
  • Set page file to "system managed"
  • Set system crash/recovery options to "Automatic memory dump"
  • Windows Error Reporting (WER) system service should be set to MANUAL
  • User account control must be running
In addition...
  • Sometimes SSD drives with older firmware do not create dumps (update the firmware)
  • Cleaner applications like Ccleaner delete dump files so don't run them until you are fixed
  • Bad Physical RAM may prevent the data from being saved and written to a file on reboot
You might want to check on all of the above.

In addition, take a look in the folder C:\Windows\LiveKernelReports and check in all sub-folders there for any dump files. Upload any you find to the cloud with a link to them here (be sure to make them public). This location is where Windows writes dump files fro problems that were recovered.
 
There are no dumps in the upload but there is no indication in your System log of any BSODs, there are many unexpected shutdowns or crashes however. What there is in your System log are a lot of errors for your fingerprint reader...

That's annoying, I've had things setup correctly for dumps... usually though, it's a hard-freeze and I have to long-power-button to get it to shutdown, so not surprisin
Code:
Event[1153]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-24T14:22:33.7960000Z
  Event ID: 1
  Task: Driver
  Level: Error
  Opcode: General
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
An operation has failed (0xA, 0x0, 0x0, 0x0).
ScReadWrite: Failed to write request.
HResult: A device which does not exist was specified.

Event[1219]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-23T23:41:27.0850000Z
  Event ID: 10
  Task: Driver
  Level: Error
  Opcode: Ioctl
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
Request[0](CLS=0x0,INS=0xCB,P1=0x2F,P2=0x1,Lc=2,Le=256,.NETServiceMethod=0x0)

Event[1220]
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2023-10-23T23:41:27.0850000Z
  Event ID: 1
  Task: Driver
  Level: Error
  Opcode: General
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Zippy
  Description:
An operation has failed (0x0, 0x0, 0x0, 0x0).
ScT1Transmit: Failed to send request.
HResult: A device which does not exist was specified.
Those are just a few. The WudfUsbccidDriver.dll driver is a Microsoft driver that manages your fingerprint reader, and as its name suggests this is a USB type device - this may well be the source of what you suspect are USB problems.

Do you use the fingerprint reader? If not then it would be wise to disable it. If you do use it then first check with the system integrator (PowerSpec?) to see whether they have an updated driver for it, or check on the Clevo download site for your model to see whether there is an updated driver available there. If neither of those have a suitable driver then run Windows Update, click on 'View optional updates', expand the Driver Updates section, and see whether there is a fingerprint reader driver available in there.

If you can't find an updated driver then I would disable the fingerprint reader as a test, and see whether the problem resolves.

I use the fingerprint driver all the time, it's fussy... I'll dig for another driver
One other USB related issue I note is that you don't have a driver installed for your Razer Huntsman Elite keyboard...
Code:
RzVirt_01    RZVIRTUAL\VID_1532&PID_0226&MI_00&COL03\8&209DFDC1&0&01    The drivers for this device are not installed.
Is that intentional? It will use the Windows keyboard driver of course so this may not be an issue at all.
In addition, although there are no BSOD bugcheck entries logged in your System log there are several errors reporting that dump file creation failed. It is important that your system is configured to write dumps, to do that ALL of the following must be true...
Good eye! I had just cleaned drivers out... it's back to having a driver after reinstalling current Razer Synapse.

  • The page file must be on the same drive as your operating system
Check
  • Set page file to "system managed"
Check
  • Set system crash/recovery options to "Automatic memory dump"
Check
  • Windows Error Reporting (WER) system service should be set to MANUAL
Manual (Trigger Start)... is that right?
  • User account control must be running
Check

In addition...
  • Sometimes SSD drives with older firmware do not create dumps (update the firmware)
Oooo, nice idea... I'll dig for a new firmware
  • Cleaner applications like Ccleaner delete dump files so don't run them until you are fixed

Yep, clean before, gather data after a BSOD. Will do
  • Bad Physical RAM may prevent the data from being saved and written to a file on reboot
Doubt that... no other RAM issues and RAM test shows good

You might want to check on all of the above.

In addition, take a look in the folder C:\Windows\LiveKernelReports and check in all sub-folders there for any dump files. Upload any you find to the cloud with a link to them here (be sure to make them public). This location is where Windows writes dump files fro problems that were recovered.
Nothing LiveKernelReports\ResourceTimeout but FIVE DMPs in LiveKernelReports\WATCHDOG... should I send any? The most recent is 8/16... so not likely related/current
 
Upload the WATCHDOG dumps, and any other dumps in any other sub-folder of LiveKernelReports.
 
No better driver for the Fingerprint, no new firmware for the SSD.
Is there a BIOS update perhaps?

The live kernel event dumps are several months old, spanning 1st June to 16th August, but they are ALL graphics card related. Four of them are 0x117 bugchecks, that's a VIDEO_TDR_TIMEOUT_DETECTED failure. TDR is the Windows Timeout Detection and Recovery Feature, it detects graphics hangs and resets the driver and graphics card to prevent a full system crash. That will crash (to the desktop) whatever app or game was using the graphics card at the time.

The oldest (1st June) is a 0x141 bugcheck, that's a VIDEO_ENGINE_TIMEOUT_DETECTED failure. It's broadly similar to the 0x117 bugchecks and indicates that a driver command to the graphics card timed out. I can see in the dumps that since this event you have updated the graphics driver twice, but you're still seeing these timeouts. That would tend to suggest that there may be a graphics card issue here.

Since this is a laptop and you can't remove the graphics card, could your try disabling the Nvidia card in Device Manager and then reboot (to ensure that nvlddmkm.sys isn't loaded) so that you're running only on the Intel iGPU. See whether you have the same issues?

Laptop graphics drivers, both Nvidia and Intel are often highly customised, for operational, performance, and power saving reasons, and the generic drivers from Intel and Nvidia may not be suitable. If nothing else works, I would uninstall both drivers (use DDU for the Nvidia driver) and download and install the latest two graphics drivers from the Clevo download site for your model of laptop. They are guaranteed to be suitable for your laptop, so see whether they help.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top