Question Constant blue screens and hard crashes ?

[johnbl]

Just finished, got another blue screen even.
This one happened even with that driver unchecked.
Heres another dump More dumping

note: so far this is the most likely suspect, it explains the long timeout value, it is not likely to work correctly since the usb specifications have changed so much over the years, you have a updated bios which will have the updated usb specifications.
the bios update, needs to match the chipset drivers and the various usb drivers. (they should be somewhat backward compatible unless there are bugs. (there are always bugs)
file name CMUSBDAC.sys
Timestamp: Wed Aug 20 23:58:25 2014
listed as C-Media USB Audio Class Driver
(might be for a microphone like blue snowball microphone.)
date seems bogus.
but it looks like another audio driver.
you might remove the audio drivers, since it is usb you would want to go into control panel, device manager, find the menu item to show hidden devices and enable it. then find each greyed out entry and delete it. usb devices drivers are hidden when the device is removed. you have to manually delete them for each port the device was plugged into.

note: if you do have a blue snowball microphone you might install this driver

ASIO4ALL Driver​

you would want to google the for the installer.


looks like you have a overclock driver installed also:
iocbios2.sys Fri Jun 16 15:05:53 2023
(intel over clocking driver)

cpu info:
Identifier = REG_SZ Intel64 Family 6 Model 151 Stepping 2
ProcessorNameString = REG_SZ 12th Gen Intel(R) Core(TM) i9-12900K

cpu released nov 2021

note: for old usb devices they are unlikely to understand the low power states and the new methods that allow the devices to wake up the computer. You can work around this by going into windows control panel device manger, find the usb root hub, right mouse click on it to bring up properties, the find the power management tab and tell windows not to power down the device to save power. then you need to do the same for the port (if it is a option) and for the device itself (if it is a option)
you do not want any of the devices in the chain of devices to get powered down.

also note: kernel memory dumps include the usb hardware logs and the info on the drivers for all of the usb devices. info is not in a minidump file.

 

[AlmightyKing]

note: so far this is the most likely suspect, it explains the long timeout value, it is not likely to work correctly since the usb specifications have changed so much over the years, you have a updated bios which will have the updated usb specifications.
the bios update, needs to match the chipset drivers and the various usb drivers. (they should be somewhat backward compatible unless there are bugs. (there are always bugs)
file name CMUSBDAC.sys
Timestamp: Wed Aug 20 23:58:25 2014
listed as C-Media USB Audio Class Driver
(might be for a microphone like blue snowball microphone.)
date seems bogus.
but it looks like another audio driver.
you might remove the audio drivers, since it is usb you would want to go into control panel, device manager, find the menu item to show hidden devices and enable it. then find each greyed out entry and delete it. usb devices drivers are hidden when the device is removed. you have to manually delete them for each port the device was plugged into.

note: if you do have a blue snowball microphone you might install this driver

ASIO4ALL Driver​

you would want to google the for the installer.


looks like you have a overclock driver installed also:
iocbios2.sys Fri Jun 16 15:05:53 2023
(intel over clocking driver)

cpu info:
Identifier = REG_SZ Intel64 Family 6 Model 151 Stepping 2
ProcessorNameString = REG_SZ 12th Gen Intel(R) Core(TM) i9-12900K

cpu released nov 2021

I uninstalled a bunch of drivers that were grayed out in the Device Manager tab. I also uninstalled a bunch of sound drivers that I wasn't using, particularly Snowball, Nvidia high-definition audio, a bunch of Asus audio drivers, etc.
I just have realtek installed for now (surprisingly, it works and sounds good)

As for the Intel overclock driver, I downloaded XTU to see if I could undervolt my CPU earlier this week. I figured since my CPU temps were so high, it could have been the reason behind the blue screens. Should I find this intel overclocking driver and uninstall it too?

After all this, should I rerun verifier.exe and see if it blue screens anymore? If it doesn't, would that mean everything is fixed?

 

[AlmightyKing]

note: so far this is the most likely suspect, it explains the long timeout value, it is not likely to work correctly since the usb specifications have changed so much over the years, you have a updated bios which will have the updated usb specifications.
the bios update, needs to match the chipset drivers and the various usb drivers. (they should be somewhat backward compatible unless there are bugs. (there are always bugs)
file name CMUSBDAC.sys
Timestamp: Wed Aug 20 23:58:25 2014
listed as C-Media USB Audio Class Driver
(might be for a microphone like blue snowball microphone.)
date seems bogus.
but it looks like another audio driver.
you might remove the audio drivers, since it is usb you would want to go into control panel, device manager, find the menu item to show hidden devices and enable it. then find each greyed out entry and delete it. usb devices drivers are hidden when the device is removed. you have to manually delete them for each port the device was plugged into.

note: if you do have a blue snowball microphone you might install this driver

ASIO4ALL Driver​

you would want to google the for the installer.


looks like you have a overclock driver installed also:
iocbios2.sys Fri Jun 16 15:05:53 2023
(intel over clocking driver)

cpu info:
Identifier = REG_SZ Intel64 Family 6 Model 151 Stepping 2
ProcessorNameString = REG_SZ 12th Gen Intel(R) Core(TM) i9-12900K

cpu released nov 2021

note: for old usb devices they are unlikely to understand the low power states and the new methods that allow the devices to wake up the computer. You can work around this by going into windows control panel device manger, find the usb root hub, right mouse click on it to bring up properties, the find the power management tab and tell windows not to power down the device to save power. then you need to do the same for the port (if it is a option) and for the device itself (if it is a option)
you do not want any of the devices in the chain of devices to get powered down.

also note: kernel memory dumps include the usb hardware logs and the info on the drivers for all of the usb devices. info is not in a minidump file.

Got another one but this time it wasn't a bluescreen. The whole computer just froze up and made this weird buzzing noise (Most likely from the audio looping you get from a computer freeze/ crash).

Nothing showed up on my mini dump file and the event doesn't show up on view reliability history, however it does show up on event view.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 4/19/2025 12:43:07 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Almighty
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>10</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2025-04-19T04:43:07.7350446Z" />
<EventRecordID>7151</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Almighty</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
<Data Name="CsEntryScenarioInstanceIdV2">0</Data>
<Data Name="LongPowerButtonPressDetected">false</Data>
<Data Name="LidReliability">false</Data>
<Data Name="InputSuppressionState">0</Data>
<Data Name="PowerButtonSuppressionState">0</Data>
<Data Name="LidState">3</Data>
<Data Name="WHEABootErrorCount">0</Data>
</EventData>
</Event>



, im noticing a trend here. It mostly happens with games with Anti-cheat systems in the background, HellDivers2 Apex Legends Destiny 2 (all using Easy-AntiCheat). Last one I remember getting from something outside those games was The Last of us Part1.

 

[SkyNetRising]

The whole computer just froze up and made this weird buzzing noise

Have you run memtest with both ram modules installed? (as suggested above)

 

[johnbl]

- Remove overclock utility
- change memory dump type to kernel
- go into bios, make any change and change it back and save configuration. reboot
- run verifier again.

provide kernel memory dump and I will take a look at the internal logs.
note: often if you uninstall sound drivers, windows plug and play will reinstall them a few seconds later. you would need to disable the driver or go into BIOS and disable the hardware if you have that option. you can also use the pnputil.exe tool and remove the driver package from the driverstore so that plug and play does not have a driver to install.
here is a third party tool to delete drivers from the driver store. It is easier that using pnputil.exe
(driverstoreexplorer)
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.12.82

there are limited number of DMA channels that a sound device can use. if a sound driver responds to the wrong DMA request it can overflow the second drivers buffer. if a speaker is connected, you will hear a bunch of strange sounds before the bugcheck. BIOS builds a database of hardware settings that it passes to windows plug and play. making any change to the bios and change it back and save should force the bios to rebuild the database. This can free up setting if you disable any motherboard hardware. it is also one of the reasons that bios upgrades fix things when there are really no fixes that were made that should have helped. (upgrade to bios forces rescan of hardware and rebuild of database of settings sent to windows)

 

[AlmightyKing]

Have you run memtest with both ram modules installed? (as suggested above)

No, I will give this a try soon
(not looking forward to another hour-long memory test)

Do you think this will give me solutions?

 

[SkyNetRising]

No, I will give this a try soon (not looking forward to another hour-long memory test)
Do you think this will give me solutions?

If memtest with two modules fails, this means your ram is unstable.

Then you either have to adjust dram settings or replace modules
(or use your pc with only single module installed).