Windows 10 BSOD every 10 minutes

[HardStroke]

So yesterday i tried using my phone as a second monitor since i have a 120hz refresh rate and thought it would be a cool idea

I installed xdisplay and used if for 10 minutes

After that i uninstalled it

And started gettinf bsods every 10 minutes

I think, not 100% sure but i think i had about 2 or 3 bsods before i even tried using xdisplay, so maybe it has nothing to do with that

No matter what i do, i get bsod

I restarted the pc, went to bed, and the pc on the lockscreen, still got a bsod

Specs:

10600k on 4.9ghz - 110% stable

Tried 4.8ghz, still crashes

Tried stock, still crashes

Gigabyte vision g, latest bios

×2 Corsair 3600mhz cl18-22-22-42 16gb (2x8gb) 32 gb total, overclocked them as well, still crashes on stock

Rtx 2080, latest drivers

Boot drive: a400 240gb about 2.5 years old

I have a 970 evo, didnt really have the time to reinstall windows on in

antec hgc gold 850w

Windows 10 EP, latest update - not 20h2

[Applefreak]

6 minutes ago, HardStroke said:

So yesterday i tried using my phone as a second monitor since i have a 120hz refresh rate and thought it would be a cool idea

I installed xdisplay and used if for 10 minutes

After that i uninstalled it

And started gettinf bsods every 10 minutes

I think, not 100% sure but i think i had about 2 or 3 bsods before i even tried using xdisplay, so maybe it has nothing to do with that

No matter what i do, i get bsod

I restarted the pc, went to bed, and the pc on the lockscreen, still got a bsod

Specs:

10600k on 4.9ghz - 110% stable

Tried 4.8ghz, still crashes

Tried stock, still crashes

Gigabyte vision g, latest bios

×2 Corsair 3600mhz cl18-22-22-42 16gb (2x8gb) 32 gb total, overclocked them as well, still crashes on stock

Rtx 2080, latest drivers

Boot drive: a400 240gb about 2.5 years old

I have a 970 evo, didnt really have the time to reinstall windows on in

antec hgc gold 850w

Windows 10 EP, latest update - not 20h2

Did you remove the driver and the service as well, those would have been left behind unless the creator of the program did follow common sense (most do not).

[GuiltySpark_]

Almost certainly a bad driver. What the BSOD say? Event viewer may have some information as well. Does this happen in safe mode?

 

[HardStroke]

52 minutes ago, rickeo said:

Almost certainly a bad driver. What the BSOD say? Event viewer may have some information as well. Does this happen in safe mode?

 

 

54 minutes ago, Applefreak said:

Did you remove the driver and the service as well, those would have been left behind unless the creator of the program did follow common sense (most do not).

Ill be home in a bit so ill send you the log later

Do you guys think that i should just try to roll back the windows to an earlier state?

Altough i did have a few crashes borfe i installed xdisplay

[HardStroke]

16 hours ago, rickeo said:

Almost certainly a bad driver. What the BSOD say? Event viewer may have some information as well. Does this happen in safe mode?

 

says: irql_not_less_or_equal

I just checked the event viewer and this is what was written:

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: 

[LogicalDrm]

-> Moved to Troubleshooting

[Hon Leung]

On 2/24/2021 at 1:55 PM, HardStroke said:

Do you guys think that i should just try to roll back the windows to an earlier state?

Im surprised no one suggested sfc /scannow, or am I missing something... BSOD is like 90% or more of the time just system file corruption.

[GuiltySpark_]

2 hours ago, McPlayerTeam said:

Im surprised no one suggested sfc /scannow, or am I missing something... BSOD is like 90% or more of the time just system file corruption.

BSOD's actually are most commonly crap drivers or malfunctioning hardware. 

 

He's got a pretty bad looking message in the Event Viewer for Corsair iCUE, i'd start by removing that entirely, probably with something like REVO Uninstaller. 

 

Also just using the machine for a bit in safemode can't hurt. 

 

Nothing wrong with doing a system file check too, of course. 

[HardStroke]

23 hours ago, McPlayerTeam said:

Im surprised no one suggested sfc /scannow, or am I missing something... BSOD is like 90% or more of the time just system file corruption.

tried that

said that everything is ok