Random BSOD troubleshooting.

[Slip22]

Hey all,

So after a 15 minute phone call, I rebooted my PC to find that on boot I had encountered a blue screen. It has not occurred again and is not a frequent occurrence. I will add below some useful information that may be of use to determining a possible cause.

1) The System has been in daily use for around 2 years, the system specs will be below.

2) The system has never had a sustained Overclock and any Overclocks have never been higher than 1.200v before being reverted back to default.

3) I did encounter a slight grinding noise coming from my HDD a few days ago, it has not occurred again.

4) On interior inspection the motherboard has no trauma or visible capacitor bulging, it is still in excellent condition and has not seen any abuse.

3) Temperatures and voltage are good, Vcore is default and the CPU is cooled by a 212 Evo yielding 20 degrees idle and a maximum of 40-high 40's under load.

Could this BSOD be possible data corruption that could be fixed by a clean install of windows? The OS is on an SSD.

Specs:

i5 4690k stock
MSI GTX 1070
GA-Z9ZP-D3 Gigabyte motherboard
8GB Kingston Value DDR3 RAM
650w EVGA GQ Gold rated PSU
1TB HDD
140 GB SSD

 

[grana92]

BSOD will always give you an error code, so you should write that code down and check it's meaning on this site: https://www.lifewire.com/blue-screen-error-codes-4065576 .

Blue Screens can occur for a number of reasons; memory error, hard drive error, windows error, driver error, corrupt drivers, fatal hardware malfunction, etc.. Since your PC recovered perfectly from the BSOD I would say it was a windows error or maybe memory. Anyway it's hard to diagnose without the error code..

 

[Slip22]

BSOD will always give you an error code, so you should write that code down and check it's meaning on this site: https://www.lifewire.com/blue-screen-error-codes-4065576 .

Blue Screens can occur for a number of reasons; memory error, hard drive error, windows error, driver error, corrupt drivers, fatal hardware malfunction, etc.. Since your PC recovered perfectly from the BSOD I would say it was a windows error or maybe memory. Anyway it's hard to diagnose without the error code..

Oh okay, well I did not know that.
Thanks for the information on the BSOD code.

Slip.

 

[Slip22]

BSOD will always give you an error code, so you should write that code down and check it's meaning on this site: https://www.lifewire.com/blue-screen-error-codes-4065576 .

Blue Screens can occur for a number of reasons; memory error, hard drive error, windows error, driver error, corrupt drivers, fatal hardware malfunction, etc.. Since your PC recovered perfectly from the BSOD I would say it was a windows error or maybe memory. Anyway it's hard to diagnose without the error code..

Would the event properties help in any way?

 

[SgtScream]

BSOD will always give you an error code, so you should write that code down and check it's meaning on this site: https://www.lifewire.com/blue-screen-error-codes-4065576 .

Blue Screens can occur for a number of reasons; memory error, hard drive error, windows error, driver error, corrupt drivers, fatal hardware malfunction, etc.. Since your PC recovered perfectly from the BSOD I would say it was a windows error or maybe memory. Anyway it's hard to diagnose without the error code..

Would the event properties help in any way?

Yes, you can analyze your event viewer. Make sure you look at your application and system logs. Also and minidump folder that houses your blue screen info is:
C:/Windows/Minidump/*.dmp

 

[Slip22]

Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

This is the error description that I have found.