I just changed my cpu yesterday to a Core I7-7820x and I have gotten 3 screens of death since, is this a sign the processor is bad?
Hello Calhawk2000,
Welcome to Tenforums :)
Normally we would not jump to conclusions but given that you have just changed the CPU and the last two BSOD errors are hardware errors it does look likely to be a CPU problem.
Both x124 WHEA errors are indicating that the CPU is reporting an unknown error:
Code:6: kd> !errrec ffffd6065a146028 =============================================================================== Common Platform Error Record @ ffffd6065a146028 ------------------------------------------------------------------------------- Record Id : 01d30af6189a4a9f Severity : Fatal (1) Length : 864 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/1/2017 20:06:54 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffd6065a1460a8 Section @ ffffd6065a146180 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 : 0x0000000000050654 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffd6065a1460f0 Section @ ffffd6065a146240 Offset : 536 Length : 64 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 54 06 05 00 00 08 10 06 - bf fb fe 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 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffd6065a146138 Section @ ffffd6065a146280 Offset : 600 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 6 Bank 0) Status : 0xb200000000070005Code:3: kd> !errrec ffffce820a346028 =============================================================================== Common Platform Error Record @ ffffce820a346028 ------------------------------------------------------------------------------- Record Id : 01d30ba9f5c999bb Severity : Fatal (1) Length : 864 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/2/2017 16:33:04 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffce820a3460a8 Section @ ffffce820a346180 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 : 0x0000000000050654 Processor ID : 0x0000000000000003 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffce820a3460f0 Section @ ffffce820a346240 Offset : 536 Length : 64 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000003 CPU Id : 54 06 05 00 00 08 10 03 - bf fb fe 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 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffce820a346138 Section @ ffffce820a346280 Offset : 600 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 3 Bank 0) Status : 0xb200000000070005
I notice that it is not the same processor involved in the two errors, this makes me a little hesitant to immediately condemn the CPU so please run a CPU test to see if this can confirm the diagnosis (make sure you are not overclocking the CPU):
Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums
Warning
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
I ran prime95 for over 3 hours and no errors, now what do you think the problem could be?
I also forgot to say that the processor is not overclocked. It is running stock speed. I also have run memtest and no errors in the memory either.
Did you clean install WIndows 10 after changing the CPU? If not you might want to try that. Save you data first though.
Yes I have the latest BIOS, but I didn't do a clean install of windows.
One of the BSOD related drivers in windows error reporting was: iaStorAV.sys
The report is included in the code tags wrap.
Intel(R) SATA RAID Controller Driver
It was not listed in the win dbg as that was WHEA 124
This driver could be updated.
Code:8/2/2017 5:41 AM Windows Error Reporting Fault bucket AV_iastorav!TransportSrbExtension::isBypass, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0c0bbed2-166e-4608-aeea-7f5f0ab19773 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80a83f497f8 P4: ffff9900b5696908 P5: ffff9900b5696150 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080217-11906-01.dmp \\?\D:\Temp\Files\WER-13421-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAC.tmp.txt \\?\D:\Temp\Files\WER71F4.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_361cf5b7d975566c2d2fd0fe888d6cf2aee17b4c_00000000_cab_1a88735b Analysis symbol: Rechecking for solution: 0 Report Id: 54b919e9-1588-4965-a8b5-840afe9c6771 Report Status: 268435456 Hashed bucket:
Code:iaStorAV Intel(R) SATA RAID Con Intel(R) SATA RAID Con Kernel Manual Stopped OK FALSE FALSE 4,096 593,920 0 2/19/2015 7:08:39 AM C:\Windows\system32\drivers\iaStorAV.sys 4,096
iaStorAV.sys Intel Rapid Storage Technology SATA RAID Controller driver https://downloadcenter.intel.com/default.aspx
You could try a reset instead of a clean install or install the chipset drivers for your new system board.
See here: http://www.dowdandassociates.com/blo...g-motherboard/
It's for Windows 7 but the same process holds true for Windows 10.
1. Get the chipset drivers, expand them and place on a flash drive.
2 Boot your install DVD or flash drive, take the Repair your computer path then use
dism /image:c:\ /add-driver /Driver:X:\ /recurse
command to add the new chipset drivers then reboot and wait while the new drivers are install. Can take a while but it may boot properly. If you have problems, read the first response by Spriggan for a possible fix.
Something to think about at least.
I reinstalled Windows 10 Pro and it didn't crash until I had almost all of the drivers reinstalled then it crashed twice. Here is the dump files. What do you suggest now?
Quote