Random BSoDs

[Cyberiad]

Hello folks,

For the last 5 or so days I have been experiencing random Blue Screens, the first one I thought it was just random but well, another 4 happened so it's not that random. Anyways, I'll attach the .dmp files and I'd appreciate it if you folks could help me out.

Cheers.

 

[BorisTheAnimal]

Hello Cyberiad and welcome to 7forums

Could you please run the DM Log Collector tool:

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

As it will help us solve your issues!

Thanks, Boris

 

[Cyberiad]

Hello and thank you for the welcome =)

Apologies, I have ran the tool and the file is attached =)

 

[BorisTheAnimal]

Saw in the Event Log that after one of the crashes there was a problem with heat in your machine.

Event[54344]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2016-09-01T14:54:03.520
Event ID: 41
Task: N/A
Level: Critical
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Prometheus-PC
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[54350]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2016-09-01T14:54:04.378
Event ID: 89
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Prometheus-PC
Description:
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 323K
_AC3 = 318K
_AC4 = 313K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data.

The red text shows that the CRT which translates to Critical Shutdown Treshold was at 104 Celsius just after the crash.

I would recommend that you check your CPU cooler that it functions properly and if need be reapply the Thermal Compound between the Cooler and the CPU.

Cheers, Boris

 

[Cyberiad]

Hi Boris,

Thank you for the reply. Is it safe to assume then that each BSOD was as a result of the machine overheating? Or was that just one cause? I'll have a look at my machine when I get home and check out the cooler + replace the thermal paste.

Additionally, I googled around and there are other, software solutions related to the error you pointed out, as well as BIOS changes. I'll have a look at that as well to make sure that the BIOS has the fan set to the correct RPM and see if any software conflicts are causing the CPU to overheat.

 

[Cyberiad]

Just a little update.

I've upgraded to Win 10 ('bout time) and now have a temperature monitor installed. My CPU temp sits around 30-35 with it climbing to around 42-45 whilst playing Aion etc. One thing I noticed is that the few temperature monitors I have used are each pulling up my motherboard as having a temperature of 114-115c, I checked the motherboard sensor and it indicates around 30c which is in line with the other heat generating devices in the machine (cpu, gpu etc). I checked online and apparently it's a known issue with my motherboard type, I am wondering though if windows is picking up on the false temperature reading and shutting down the system as a result.

 

[BorisTheAnimal]

Well looking through the Event Log I saw at least 10 of these that "the system has rebooted without cleanly shutting down first." and a second after that it listed the same heating issue.

Alright check your CPU cooler and also the BIOS, I'll keep on trying to find out more about the error to get to the bottom of this!

Cheers, Boris

 

[BorisTheAnimal]

Went to the Asus support page for your motherboard that there is a BIOS update that will improve system stability, I believe it is worth a try since that is basically what you are having issues with.

So without further ado, please head on over to Asus Support page:

Z97-K

And select your OS, open up the BIOS dropdown and select the latest one, after that the download has finished stay on the Support page and scroll down and download the BIOS utility as I believe it help you in this, follow the on screen instructions, it should be quite straightforward, if not then just ask for help!

Cheers, Boris

 

[Cyberiad]

Thank you very much for that! I'm terrified of flashing the bios XD

The CPU cooler is fine on the system and the bios is fine as well, there's no actual issue that I can see, even checked the mobo when I took off the heatsink and fan, no burns or scorches or anything, no odd burn smells either so I definitely don't think there a heat problem. I've been checking my temperatures throughout the night as well, the cpu temp peaked once at 50c and has stayed around 42 since then. Same for everything else except the motherboard according to the monitor, it's sitting at 111c, how? I don't know.

Perhaps the bios flash will fix this.

 

[BorisTheAnimal]

Thank you very much for that! I'm terrified of flashing the bios XD

The CPU cooler is fine on the system and the bios is fine as well, there's no actual issue that I can see, even checked the mobo when I took off the heatsink and fan, no burns or scorches or anything, no odd burn smells either so I definitely don't think there a heat problem. I've been checking my temperatures throughout the night as well, the cpu temp peaked once at 50c and has stayed around 42 since then. Same for everything else except the motherboard according to the monitor, it's sitting at 111c, how? I don't know.

Perhaps the bios flash will fix this.

Perhaps.

Or then you just have a faulty sensor on the motherboard that keeps outputting the wrong temperature. For example like this:

Asus mobo temperature issue [Solved] - Asus - Motherboards

The solution is what you are facing here.

 

[BorisTheAnimal]

Also perform these, it wont hurt:

Open up a Command Prompt (Admin)
Type sfc /scannow then Enter(Mind the space before "/")

And:

Type chkdsk /f /r then Enter(Mind the space before "/")

 

[Cyberiad]

Ah yes I saw that thread, I know that if that's the case then I'll have to live with a faulty sensor.

My concern is if that info is being interpreted by windows and causing the shutdowns.

 

[BorisTheAnimal]

Ah yes I saw that thread, I know that if that's the case then I'll have to live with a faulty sensor.

My concern is if that info is being interpreted by windows and causing the shutdowns.

Did you see my previous message about the tasks to run in Command Prompt?

If not be a darling and run them!

Cheers, Boris

 

[Cyberiad]

Good morning!

I ran both commands the scannow came back fine, however the chkdsk took around four hours to run and did it's job but I cannot find a log for it. I went into the event view and navigated to where the report should be according to the various instructions I found online.

 

[BorisTheAnimal]

Okay, uhm. Here is an example guide for checking the log of chkdsk:

https://askleo.com/how_do_i_see_the_results_of_a_chkdsk_that_ran_on_boot/

Any crashes?

 

[Cyberiad]

I had to do a manual search of Winnit, for some reason the search function didn't pick it up... Here is the report;

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
371968 file records processed. File verification completed.
6399 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
484554 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 1573 unused index entries from index $SII of file 0x9.
Cleaning up 1573 unused index entries from index $SDH of file 0x9.
Cleaning up 1573 unused security descriptors.
Security descriptor verification completed.
56294 data files processed. CHKDSK is verifying Usn Journal...
38850376 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
371952 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
167053735 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976195583 KB total disk space.
307279104 KB in 309187 files.
192896 KB in 56295 indexes.
0 KB in bad sectors.
508639 KB in use by the system.
65536 KB occupied by the log file.
668214944 KB available on disk.

4096 bytes in each allocation unit.
244048895 total allocation units on disk.
167053736 allocation units available on disk.

Internal Info:
00 ad 05 00 b4 93 05 00 f9 af 0a 00 00 00 00 00 ................
f6 01 00 00 b6 09 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[BorisTheAnimal]

Alrighty seems to be cleared!

I would recommend that you follow this tutorial for MemTest86+:

Diagnostic Test

 RAM TEST

:ar: Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

And how about new hardware, anything that you might have put into the computer before the errors started to happen?

Cheers, Boris

 

[BorisTheAnimal]

Also even though chkdsk might have cleared your C drive, I would still recommend that you also run SeaTools:

SeaTools for Windows | Seagate

How to guide:

How to use SeaTools for Windows

Cheers, Boris