And that would be RGB Fusion, which I believe is part of MB or peripheral lighting effects program.
Constant Blue Screens Windows 10
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I am having Constant BlueScreens on Windows, first it was USBXHCI.sys related, removed some software related to Corsair iCUE and crashes recently have been getting related to HIDCLASS.sys
Crosshair VIII Hero (WiFi) Motherboard, latest BIOS and drivers
Windows 10 Pro fully up to date
Here are connected USB devices
NZXT Kraken X73 AIO Liquid Cooler and NZXT Cam Software
Corsair K95 RGB and Corsair iCUE software
Logitech G502 Hero and Logitech Software (connected to K95)
Logitech Desktop Mic
Focusrite Scarlett Solo 2nd Gen
Razer Kiyo Webcam (connected via USB extension cable)
Connected to USB Hub which is connected to USB extension cable
Logitech Extreme 3D Pro
Saitek Flight Rudder Pedals
at one point a Samsung Galaxy S5 that was charging
I have had crashes with iCue and Logitech Software closed
USBXHCI.sys
KMODE_EXCEPTION_NOT_HANDLED
HIDCLASS.sys
KMODE_EXCEPTION_NOT_HANDLED
KERNEL_SECURITY_CHECK_FAILURE
DRIVER_IRQL_NOT_LESS_OR_EQUAL
mini dumps for all crashes found here https://1drv.ms/u/s!AreYLbFUtxfggUykmZx4sJ9luOQ8?e=7toLz1
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
29 answers
Sort by: Most helpful
-
Anonymous
2020-10-04T15:54:22+00:00 -
Anonymous
2020-10-04T00:11:39+00:00 i figured that out and uninstalled it
I also got another BSOD related to glckio2.sys that did not generate a dump for some reason, I will try again later.
-
Anonymous
2020-10-03T23:24:43+00:00 asramdisk.sys is component of the ASUS RamDisk Driver (rog) - https://rog.asus.com/technology/republic-of-gam...
But the system uptime was only slightly more than a minute so I cant say it was not part of the boot process.
-
Anonymous
2020-10-03T19:13:45+00:00 deleted the old driver and tried again
here is the latest, computer booted to desktop, but crashed shortly later
https://1drv.ms/u/s!AreYLbFUtxfggU-SNBTdtO2tRIfG?e=1POYYg
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000000, caller is trying to allocate zero bytes
Arg2: 0000000000000000, current IRQL
Arg3: 0000000000000001, pool type
Arg4: 0000000000000000, number of bytes
Debugging Details:
Page f45c5a not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CHANDLERPC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: c4
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 1
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff818a
2689b5a8 fffff803195dae34 : 00000000000000c4 0000000000000000 0000000000000000 0000000000000001 : nt!KeBugCheckExffff818a
2689b5b0 fffff803195f6e82 : 0000000000000081 fffff80317aa2d98 0000000000000000 00000000000000c4 : nt!VerifierBugCheckIfAppropriate+0xe0ffff818a
2689b5f0 fffff803195de658 : 0000000000000081 0000000000000020 0000000070617257 0000000000000000 : nt!ExAllocatePoolSanityChecks+0xfeffff818a
2689b630 fffff80319fc9d55 : 0000000000000081 ffff818a2689b700 0000000070617257 0000000000000081 : nt!VeAllocatePoolWithTagPriority+0x88ffff818a
2689b6a0 fffff803195de9c4 : 0000000000000081 ffff898b746a2f90 0000000000000000 fffff803195f41f4 : VerifierExt!ExAllocatePool_internal_wrapper+0x1c5ffff818a
2689b730 fffff80317aa2d98 : 0000000000000000 0000000000000000 ffff898b746a2f90 fffff80319fc5291 : nt!VerifierExAllocatePool+0xd4ffff818a
2689b780 fffff80317aa13f3 : ffff818a2689b86c fffff80317aaf1c0 0000000000000002 0000000000000010 : asramdisk+0x2d98ffff818a
2689b820 fffff8031935f434 : ffff898b73f60b90 ffff898b6b191000 ffff818a2689ba60 ffff898b746a2f90 : asramdisk+0x13f3ffff818a
2689b900 fffff80319329e0d : 0000000000000014 0000000000000000 0000000000000000 0000000000001000 : nt!PnpCallDriverEntry+0x4cffff818a
2689b960 fffff8031936fd77 : 0000000000000000 0000000000000000 fffff80319930440 ffff898b6a6054a0 : nt!IopLoadDriver+0x4e5ffff818a
2689bb30 fffff80318ecdf15 : ffff898b00000000 ffffffff80004dc8 ffff898b7459a040 ffff898b00000000 : nt!IopLoadUnloadDriver+0x57ffff818a
2689bb70 fffff80318e72dd5 : ffff898b7459a040 0000000000000080 ffff898b618cd1c0 000f8067bcbbbdff : nt!ExpWorkerThread+0x105ffff818a
2689bc10 fffff803190074f8 : ffffcf81c8540180 ffff898b7459a040 fffff80318e72d80 1f1f1f1f1f1f1f1f : nt!PspSystemThreadStartup+0x55ffff818a
2689bc60 0000000000000000 : ffff818a2689c000 ffff818a26896000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: asramdisk+2d98
MODULE_NAME: asramdisk
IMAGE_NAME: asramdisk.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2d98
FAILURE_BUCKET_ID: 0xc4_0_VRF_asramdisk!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {eb878648-866b-c872-728e-235e32de420a}
Followup: MachineOwner
-
Anonymous
2020-10-01T21:42:53+00:00 Yes, delete the old saitek driver.