Jump to content

Hello guys,

 

I was just minding my own business on my pc and got a randomly blue screen and went to view my logs but I don't know what they mean maybe you guys know it. 

 

They are from start to end: 

 

Error 1:

 84e7f0ce2ace235ef8cfbc58e1f07fac.png

 

critical 2:  bbe266c676a5b50c8c8ff3eb1e58632d.png

Error 3 : 1c7bd7101d6f71572665dbfeb87226cc.png

and  warning: c21bbecfd3c06a0447a1f2e073c313d7.png

 

And those last 2 are confusing: f02762cb82446a1f3dc8d74a07c9ebde.png

 

9f82287067ced510eae7ef5d474e9ac1.png

 

Does this mean that my cpu is dying ? 

 

Link to comment
https://linustechtips.com/topic/416708-weird-bluescreen-cpu-dying/
Share on other sites

Link to post
Share on other sites

try to defrag. your hard disk. go to start menu type in Disk defragmenter then go from there

Join da discord 

 

Spoiler

(Intel Core i5 4590 - XFX R9 280 - ASUS z97-A USB 3.1 - EVGA SuperNOVA 750B - 16GB EVGA DDR3-EDITION - NZXT H440 -

WD BLACK 1TB - OZC ARC 100 240gb)

#locked(ง ͠° ͟ل͜ ͡°)ง

Link to post
Share on other sites

your CPU is fine

Join da discord 

 

Spoiler

(Intel Core i5 4590 - XFX R9 280 - ASUS z97-A USB 3.1 - EVGA SuperNOVA 750B - 16GB EVGA DDR3-EDITION - NZXT H440 -

WD BLACK 1TB - OZC ARC 100 240gb)

#locked(ง ͠° ͟ل͜ ͡°)ง

Link to post
Share on other sites

try to defrag. your hard disk. go to start menu type in Disk defragmenter then go from there

 

Well people say that you aren;t suppose to defrag SSD's ? 

Link to post
Share on other sites

Well people say that you aren;t suppose to defrag SSD's ? 

I did not know u had an ssd

Join da discord 

 

Spoiler

(Intel Core i5 4590 - XFX R9 280 - ASUS z97-A USB 3.1 - EVGA SuperNOVA 750B - 16GB EVGA DDR3-EDITION - NZXT H440 -

WD BLACK 1TB - OZC ARC 100 240gb)

#locked(ง ͠° ͟ل͜ ͡°)ง

Link to post
Share on other sites

Well people say that you aren;t suppose to defrag SSD's ? 

Yes, you shouldn't. You will be reducing the lifespan by making it write alot of data and there is a marginal difference anyway in performance.

CPU+Cooler: Intel Core i5 4690K @ 4.5GHz + Corsair H105 (Getting custom loop soon)  GPU: EVGA GeForce GTX 970 SC  RAM: Kingston HyperX Fury 8GB  Motherboard: Asus Maximus VII Hero  PSU: Corsair AX860i  Case: Corsair Graphite 760T Black

Link to post
Share on other sites

showing us a crash dump will help.

CPU+Cooler: Intel Core i5 4690K @ 4.5GHz + Corsair H105 (Getting custom loop soon)  GPU: EVGA GeForce GTX 970 SC  RAM: Kingston HyperX Fury 8GB  Motherboard: Asus Maximus VII Hero  PSU: Corsair AX860i  Case: Corsair Graphite 760T Black

Link to post
Share on other sites

CPU is fine, it is just a bug in the Logitech monitoring thing-a-ma-jig for what ever reason. Could have been a random error but if it keeps happening you should either

  1. do some system maintenance, which includes but not limited to registry defrag and cleaning or
  2. uninstall the logitech doodad and what is using SIDESHOW once it is not a vital program and see if you get the BSOD again.

A water-cooled mid-tier gaming PC.

Link to post
Share on other sites

 

CPU is fine, it is just a bug in the Logitech monitoring thing-a-ma-jig for what ever reason. Could have been a random error but if it keeps happening you should either

  1. do some system maintenance, which includes but not limited to registry defrag and cleaning or
  2. uninstall the logitech doodad and what is using SIDESHOW once it is not a vital program and see if you get the BSOD again.

 

 

Well The pc is freshly installed (3 days ago) The only logitech thingy i have is the G13, but it is using realy old drivers from 2010/2012 or so. 

Link to post
Share on other sites

Well The pc is freshly installed (3 days ago) The only logitech thingy i have is the G13, but it is using realy old drivers from 2010/2012 or so. 

The age of the driver is not the real issue, the real issue is if the driver is windows ready for your specific OS, which you never mentioned what it is.

A water-cooled mid-tier gaming PC.

Link to post
Share on other sites

The age of the driver is not the real issue, the real issue is if the driver is windows ready for your specific OS, which you never mentioned what it is.

 

Windows 7 but i'll update the drivers. :)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×