Continuous BSOD's + CPU Overheating

nzr · 13 Apr 2020

Windows Version 1909(OS Build 18363.752)

Okay so the main problem is when the computer is under load,(but the intermittently when idle) ie;

- playing games or rendering video files, the computer starts stressing out. The core temperatures fluctuate like crazy. I've redone the thermal paste, stripped everything off the computer and cleaned everything. I don't really know how to analyze a minidump file I've tried but it hasn't went so well.. As far as I've come as it could be a possible driver error, BUT... I've downloaded and updated all my software/hardware drivers I can, the OS is up to date also.

I've also factory reset the computer and wiped all drives and started again and still the same issues. Can somebody please help as I'm going crazy trying to figure this out.

CPU - Intel Core i7 4790K (not overclocked)
Mainboard - MSI B85M-E45 (MS-7817)
RAM - 16GB DDR3 2133MHz Memory (2x8GB)
Graphics Card - AMD Radeon R9 200 Series
Power Supply - 750W FSP Quiet Power Supply - Silver 80 PLUS

Any replies I will greatly appreciate as I've tried to get to the bottom of this for a while, cheers.

MrPepka · 13 Apr 2020

Update BIOS - Support For B85M-E45 | Motherboard - The world leader in motherboard design | MSI Global

Ztruker · 13 Apr 2020

All the dumps are the same, here are the last two:

041020-34218-01.dmp

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff85091e285028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Code:

0: kd> !errrec ffff85091e285028
===============================================================================
Common Platform Error Record @ ffff85091e285028
-------------------------------------------------------------------------------
Record Id     : 01d60c5b791f683b
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/10/2020 20:25:12 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff85091e2850a8
Section       @ ffff85091e285180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff85091e2850f0
Section       @ ffff85091e285240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : c3 06 03 00 00 08 10 00 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffff85091e285240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff85091e285138
Section       @ ffff85091e2852c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 0 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00007ffbb83fea2e
  Misc.       : 0x00007ffbb83fea2e

041220-33500-01.dmp

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb285cfe7c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Code:

1: kd> !errrec ffffb285cfe7c028
===============================================================================
Common Platform Error Record @ ffffb285cfe7c028
-------------------------------------------------------------------------------
Record Id     : 01d60f7641276615
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/12/2020 20:56:31 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffb285cfe7c0a8
Section       @ ffffb285cfe7c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000001

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffb285cfe7c0f0
Section       @ ffffb285cfe7c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : c3 06 03 00 00 08 10 01 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffb285cfe7c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffb285cfe7c138
Section       @ ffffb285cfe7c2c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 1 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0xfffff80429611fb6
  Misc.       : 0xfffff80429611fb6

From what you described, this appears to be a CPU failure. Unlikely to be caused by a faulty device driver. CPU is probably failing because of temps.

Nevertheless, we can run Driver Verifier and run some CPU, GPU and RAM tests to see what they show.

Overclocking:
If you are overclocking, set all the hardware components to their defaults.

Test your DDR3 RAM modules for possible errors.
MemTest86+ - Test RAM
Run memtest86+ for at least 8 consecutive passes.

If it starts showing errors/red lines, stop testing. A single error is enough to determine that something is going bad.
Take a picture of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Stress test the Graphics Card using Furmark.
FurMark - GPU Stress Test
Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.
Prime95 - Stress Test Your CPU
It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

nzr · 14 Apr 2020

Okay so the overclocking side of things don't matter as I've not overclocked nor touched any settings. Everything is stock as should be.

Stress Test from the GPU (FurMark) looked positive to me, no crashing nor any lag.
Stress Test from the CPU makes the tempretures crazy high, but it seems like it takes longer than before to get to this.
Didn't do the stress test for the RAM as of yet.

I now went on and used the Driver Verifier. Where when I followed all the intructions it did as you said followed up with the BSOD. I've uploaded the minidump file itself and the V2Logger file.

Minidump file; 041420-34578-01 - 14-04-20.rar - Google Drive
V2 Logger; DESKTOP-Q9BPFIA-(2020-04-14_21-19-58).zip - Google Drive

- - - Updated - - -

MrPepka said:

Update BIOS - Support For B85M-E45 | Motherboard - The world leader in motherboard design | MSI Global

Tried this also man and its still the same. Thankyou tho much appreciated.

Ztruker · 15 Apr 2020

The Driver Verifier dump i9ndicates isctd64.sys is the cause of the BSOD.

isctd64.sys's description is "Intel(R) Smart Connect Technology Device Driver"
isctd64.sys is digitally signed by Intel(R) Smart Connect software.

isctd64.sys is usually located in the 'C:\Windows\system32\drivers\' folder.

I recommend you uninstall it as the driver is old, from Tue Nov 27 14:52:34 2012. If there is a BIOS setting for it, turn it off as well.
See what that does for you.

nzr · 15 Apr 2020

Ztruker said:

The Driver Verifier dump i9ndicates isctd64.sys is the cause of the BSOD.

I recommend you uninstall it as the driver is old, from Tue Nov 27 14:52:34 2012. If there is a BIOS setting for it, turn it off as well.
See what that does for you.

Okay thats it deleted and turned off in the BOIS. Must be a driver thats always activated as I've never turned that off since the PC was bought almost 8 years ago.... Thankyou, ill let you know if this keeps up.

nzr · 18 Apr 2020

Okay, so had another crash unfortunately after fixing that problem.Attachment 275222

Ztruker · 19 Apr 2020

Rats, was hoping that would resolve the problem. All the other dumps are the same as the following, just different processors, 0, 2, 4 and 6:

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc20a2f679028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Code:

6: kd> !ERRREC ffffc20a2f679028
===============================================================================
Common Platform Error Record @ ffffc20a2f679028
-------------------------------------------------------------------------------
Record Id     : 01d601d55e88ddcc
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/25/2020 22:41:08 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffc20a2f6790a8
Section       @ ffffc20a2f679180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffc20a2f6790f0
Section       @ ffffc20a2f679240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffc20a2f679240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffc20a2f679138
Section       @ ffffc20a2f6792c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 6 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x000000005e6cf65e
  Misc.       : 0x000000005e6cf65e

You can try Driver Verifier again but I don't think this is being caused by a driver. I believe it's a defective CPU and the only way to test that is to replace it. Still worth giving Driver Verifier another try, you never know, we might get lucky.

Here is a similar BSOD problem on the Microsoft Community Forum. Read through it and you will see a bunch of things to check, like:

1. Ensure your temperatures are within standard and nothing's overheating. The temps you showed looked okay but worth keeping an eye on.

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How to Clear CMOS (AKA Reset BIOS Settings)

3. Ensure your BIOS is up to date. Yours currently:
BIOS Version V10.7
BIOS Release Date 07/22/2014
Check for update.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only thing left to do is replace your processor as it is faulty.