This error indicates a driver power failure in the system, specifically related to notoriskl.exe.
This error indicates a driver power failure in the system, specifically related to notoriskl.exe.
Hi everyone, I built my first PC about a month ago, but lately I keep seeing random black screens while gaming. I have to completely reset it to fix the issue. I’m not sure what’s causing it. Some people suggested it could be related to the graphics card, RAM, PSU, but I ran memtest86 without any errors and both CPU and GPU are showing good activity in Cinebench. I only have one minidump from when the PC was made.
both drivers and BIOS have been updated to the latest version
download and execute microsoft autoruns64.exe with admin privileges
you possess two versions of CorsairLLAccess64.sys
Thu Jul 25 00:15:07 2024
CorsairLLAccess64.sys Mon Feb 5 01:17:49 2024
use autoruns64 and remove the previous version of CorsairLLAccess64.sys (this setup issue where you need to uninstall manually before updating)
the real bug was found in your media tek bluetooth driver. you might find an update available, but it seems the problem likely stems from having two copies of CorsairLLAccess64.sys.
you also encountered some odd memory addresses, possibly originating from firmware of an audio device. check for firmware updates on mice and headphones if they support updatable firmware. otherwise, if the address isn’t related to firmware, it could indicate a virus.
note: the bug was triggered by usbccgp.sys taking too long to respond to a power request. there were 3 pending power requests.
bluetooth attempted to cancel a power request while the media tek bluetooth driver waited for a response. the usb generic parent driver also underwent a bugcheck due to slow response time.
i suspect that some new devices now manage sleep/wake cycles independently, which can cause issues if their firmware isn’t updated or the drivers aren’t aligned with the correct specifications. you might want to open Device Manager, locate the USB hub, right-click to open properties, verify if a power management option exists, and instruct Windows not to shut it down to conserve power. this keeps the port active while preventing problems with devices that handle sleep.
the main solution involves updating the BIOS, CPU chipset drivers, motherboard firmware for USB or Bluetooth, the media tek bluetooth driver, and any add-on hardware firmware (especially new mice or headphones designed to save power by sleeping). telling Windows not to power down the hub is just a temporary workaround.**
the issue is usually caused by devices trying to wake the hub they’re connected to. Often, the signal fails to propagate through the device chain because the drivers don’t match the latest specifications.
I’m not entirely clear on how to use autoruns64 to remove the older versions, could you assist me with that? Also, I’ve updated all drivers, turned off Windows power savings. The only driver I have is for my mouse, which is quite old. My headphones and microphone don’t have drivers, so I had to download different firmware for them. Also, I haven’t found any viruses yet.
download autoruns from here:
https://learn.microsoft.com/en-us/sysint...s/autoruns
execute as admin, inspect loaded drivers
identify the listed entry and remove it
then restart your system
Generally, avoid loading two identical driver copies at once. Remove the oldest installation. When Windows detects duplicate drivers, it tries to load them but conflicts arise. It may attempt to resolve this by loading the second copy at a different memory location. Both drivers respond to services, resulting in repeated log entries and device adjustments. This can be particularly problematic for overclock drivers that modify voltages with small offsets, though it still causes issues. I've observed Corsair drivers handling millions of USB requests quickly. Most systems now route USB traffic via PCI/e bus, which can trigger GPU watchdog timeouts—such as 2-second or 30-second limits depending on the device. SSDs typically avoid these timeouts and can manage event logs from USB activity, though turning them off might resolve some problems.