[SOLVED] BSOD every 10 minutes ?

[HardStroke]

so I tried to use my phone as a second monitor (yes, I was bored) and I downloaded xdisplay
after playing with it I uninstalled it and started getting BSODs every 10 minutes (I'm also 99% sure it happened a couple of times before I installed xdisplay)
this is from the event viewer:
10:45:08 The previous system shutdown at 10:43:56 on ‎25/‎02/‎2021 was unexpected.
The last log before 10:43:56 (was at 10:43:51):
Faulting application name: Corsair.Service.CpuIdRemote64.exe, version: 3.32.0.4, time stamp: 0x5f1fd49a
Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e616e
Exception code: 0xc0000005
Fault offset: 0x00000000000100b6
Faulting process id: 0x750
Faulting application start time: 0x01d70b52573e1142
Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.CpuIdRemote64.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 2eb79578-b9bc-4972-9f53-f2fda07e8466
Faulting package full name:
Faulting package-relative application ID:
---------------
can corsair's iCUE software be the cause of those BSODs?
or is it a config or something like that in the app?
specs:

10600K 4.9GHz all core - 1000% stable
tried 4.8GHz which is also stable, still crashes
stock - still crashes
Z490 Vision G
x2 vengeance lpx 3600mhz cl18-22-22-42 2x8gb on stock
2080 AORUS
Antec HGC Gold 850W
Kingston A400 240GB as a boot drive
its pretty old but still gets the job done, I have a 970 evo, didn't really have the time to reinstall windows - maybe its finally the time?

 

[Colif]

its not normal for exe files to cause BSOD.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

 

[HardStroke]

its not normal for exe files to cause BSOD.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer

Navigate to C:\Windows\Minidump

Copy the mini-dump files out onto your Desktop

Do not use Winzip, use the built in facility in Windows

Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder

Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

Then post a link here to the zip file, so we can take a look for you . . .

its already doing it automatically
https://mega.nz/file/3Q9w2YzB#q2MUgNlVifv8dv_JRSpzVTq2-h84LFBBSXgCwQzbERM
there you go

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/jsf3b56p/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	022621-34218-01.dmp (Feb 26 2021 - 12:33:02)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for cpuz149_x64.sys
Probably caused by:	memory_corruption (Process: Corsair.Service.CpuIdRemote64.exe)
Uptime:	0 Day(s), 1 Hour(s), 01 Min(s), and 35 Sec(s)

File information:	022621-24984-01.dmp (Feb 26 2021 - 11:04:13)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for cpuz149_x64.sys
Probably caused by:	memory_corruption (Process: Corsair.Service.CpuIdRemote64.exe)
Uptime:	0 Day(s), 0 Hour(s), 11 Min(s), and 16 Sec(s)

File information:	022621-23390-01.dmp (Feb 26 2021 - 13:04:59)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for cpuz149_x64.sys
Probably caused by:	memory_corruption (Process: Corsair.Service.CpuIdRemote64.exe)
Uptime:	0 Day(s), 0 Hour(s), 30 Min(s), and 31 Sec(s)

File information:	022621-17265-01.dmp (Feb 26 2021 - 11:30:53)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for cpuz149_x64.sys
Probably caused by:	memory_corruption (Process: Corsair.Service.CpuIdRemote64.exe)
Uptime:	0 Day(s), 0 Hour(s), 26 Min(s), and 07 Sec(s)

The following dump files were 0 bytes long which means they are invalid:
022521-27187-01.dmp

Crashing driver:

Dec 05 2019

cpuz149_x64.sys

CPUID driver

Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/Z490-VISION-G-rev-1x
If you have Revision 1.0 of the motherboard, there may be a BIOS update for your system. However, use caution, fully read the instructions on the page, and I recommend you WAIT for more instruction 1st. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Never seen CPU Z cause BSOD before, are you using it to monitor sensors as that is also what the corsair service does. Maybe they conflicting. You could try updating CPU Z

 

[HardStroke]

my motherboard is always on the latest bios, i always update it
right now its on bios F8c which is the latest version (updated about a month ago)
should i just try to uninstall cpu z?
my ssd is kinda old and bad, i already reinstalled windows on my 970 evo but i didnt format the old one
you think its worth the check?
ive just checked and the is a new bios update, ill try running it later

 

[gardenman]

right now its on bios F8c which is the latest version

The dump said you are using BIOS version F8c (12/14/2020). The latest on the webpage is F20c (02/05/2021) so it was released a few weeks ago. But like I said, read the precautions first, and it might be wise to wait for more info on it first.

 

[Colif]

should i just try to uninstall cpu z?

if the bios update doesn't fix it, try removing it or updating it. current version is 1.95.0
it should offer an update every time you load it, if there is one.