Windows 10: BSOD: Machine Check Exception (caused by hal.dll)

Hello, everyone. This is my first post on this site. Someone recommended me to come here to see if I could find a solution to my problem. I have been getting the BSOD crash for 8 days now, and it seems the problem goes beyond my knowledge. It all started 7-8 days ago, after running a Radeon Clean Install for my graphics drivers. After that, I had some issues, so decided to open my case to reseat the GPU, and then reset Windows (keeping my files). After the reset, Windows worked fine for about 20 minutes, and then started crashing, always giving me the "Machine Check Exception" BSOD. To make the long story short, I have reset and fresh-installed Windows about 5 times, and the issue still persists. I don't know what it is, but Bluescreenview says it's caused by "hal.dll" in System 32. I have tried everything under my knowledge regarding PCs. I have reseated the GPU, CPU (reapplied thermal paste), heatsink, RAM, even reconnected all cables inside the case. After the last fresh install (I did it yesterday), I managed to update most drivers, but now I can barely load my desktop, because it crashes while booting Windows. It's important the fact that it runs flawlessly in Safe Mode, and in BIOS. I'm right now typing this from Safe Mode. Please someone help me...

Note: You will most likely find in the file attached to this post that one of the minidump files reads the APC Index Mismatch BSOD. That one barely happens, it usually happens if I make radical changes, like disabling services, and stuff.

:)

 

Blue screen Machine check exception caused by hal.dll

Please upload no more than five copies of your dump files that were created during the last 14 days as shared files to your OneDrive with a link here.
No more than five files please.



Dump files are usually found at c:\windows\minidump. You may need to change your settings in Windows to be able to see the files. To show hidden files select the keyboard shortcut
Win+S, type Folder Options in the Search box and click Folder Options in the drop down menu. Select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and "Hide
protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.



What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please.

DriverView: Loaded Windows Drivers List



Please provide a copy of your System Information file.
To access your System Information file select the keyboard shortcut
Win+R, type msinfo32 and press the ENTER
key. Select File, Export and give the file a name noting where it is located.
Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for
the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. Reports in normal mode preferred. Please say if the report has been obtained in safe mode.



For help with OneDrive see paragraph 9.3:

gerrys template

 

Blue screen Machine check exception caused by hal.dll

I have a windows 10 laptop and it works fine,

But when i use word and i try to save a document my whole screen freezes for a sec and the blue screen comes up.

So the minidump said:

caused by driver: hal.dll

caused by address: hal.dll+364b1

It only crashes whenever i try to save. So is it my harddrive or something?

I don't know what to do.

 

Code: 0x0000009C: MACHINE_CHECK_EXCEPTION (10.05.2017 13:06:37) [Windows 10] CAUSED BY: intelppm.sys [10.07.2015] * Intel Processor driver * => Drivers & Software also at hal.dll (Hardware Abstraction Layer DLL. NO Driver) PROCESS: System Usual causes: Hardware error (similar to STOP 0x124)[/quote]
There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Download Speccy | Find your computer specs, free!

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting -http://pcsupport.about.com/od/fixthe.../clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus software installed).

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






Diagnostic Test

CPU TEST


Run 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.

For checking temperatures u can use SpeedFan:

SpeedFan
SpeedFan automatically searches your computer for informative chips: the hardware monitor chips. SpeedFan can display voltages, fan speeds and temperatures.

 

I recommend also uninstalling NORTON for testing purposes and use windows defender instead.
Norton(Symantec) Download and run Norton Removal Tool Norton Security Scan L: ftp://ftp.symantec.com/public/englis...ools/NSSRT.exe

 

Thanks for the reply.

Is it possible the CPU could just need to be reseated? The first time I reseated the GPU (before the crashes started), I accidentally pushed the heatsink (twice) and made it move a bit. I also dropped a screw onto the MOBO, but according to what I have read, it's very unlikely something like that could have damaged it.

The PC is relatively new (I built it on December 2016), and unless I actually damaged the CPU (I5-6600K) when I pushed the heatsink, I highly doubt it's faulty, considering I had never had a BSOD since I built the PC on December. It all started after that Radeon Clean Install made me open the case to try to reseat the GPU.

It has crashed over and over again, without any softwares installed at all (including Norton, and the ASUS utilities), so I believe it's safe to discard those.

I have reset the CMOS (several times), and UEFI BIOS are up to date. The temperature of the CPU is always somewhere between 35° Celsius, and 40° Celsius; and the temperature of the MOBO is always 32° Celsius. As for the GPU, I never check its temperature, and I will probably begin doing that from now on; however, I see its fans are working fine.

Something just happened 20 minutes ago, it finally crashed in Safe Mode while playing a PS1 game. First time ever it crashes in Safe Mode. Not sure specifically what caused it, but before it happened I had created the registries to allow audio in Safe Mode, and connected my sound system (speakers/subwoofer) to the front panel of the case (for the first time since I always connect it to my monitor), and that seemingly created a flagged driver in Device Manager. I had never tried to run the ePSXe program to play games in Safe Mode, and seemingly it was a bad idea. Do you still think the CPU is faulty?

 

When u say it happend without those software im relatively sure, that theres a hardware problem. It "could" be processor related, thats why I recommend running Prime95 and checking the temperatures at the same time.

Im still relatively new in the bluescreen analysis thematics. There are a few other important informations in the dump. Maybe another expert here in the forum can look more closely to it?:

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {0, fffff803f7e35ba0, 0, 0} Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 ) Followup: MachineOwner --------- 0: kd> !sym prompts;.reload;!analyze -v;!thread;!process;!irp 0;dps fffff803f7e1a000 fffff803f7e21000;!errrec ;.ecxr;lmev;lmlv;lmv;!sysinfo smbios;!sysinfo cpuspeed;q quiet mode - symbol prompts on Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 0000000000000000 Arg2: fffff803f7e35ba0 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 10.0.10240.16384 (th1.150709-1700) SYSTEM_MANUFACTURER: System manufacturer SYSTEM_PRODUCT_NAME: System Product Name SYSTEM_SKU: SKU SYSTEM_VERSION: System Version BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 3401 BIOS_DATE: 03/15/2017 BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC. BASEBOARD_PRODUCT: Z170 PRO GAMING/AURA BASEBOARD_VERSION: Rev X.0x DUMP_TYPE: 2 BUGCHECK_P1: 0 BUGCHECK_P2: fffff803f7e35ba0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BUGCHECK_STR: 0x9C_GenuineIntel CPU_COUNT: 4 CPU_MHZ: db0 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: A0'00000000 (cache) A0'00000000 (init) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f ANALYSIS_SESSION_HOST: ANALYSIS_SESSION_TIME: 05-11-2017 13:18:01.0061 ANALYSIS_VERSION: 10.0.14321.1024 amd64fre BAD_STACK_POINTER: fffff803f7e35b68 LAST_CONTROL_TRANSFER: from fffff803f5c3ae11 to fffff803f5dc2c20 STACK_TEXT: fffff803`f7e35b68 fffff803`f5c3ae11 : 00000000`0000009c 00000000`00000000 fffff803`f7e35ba0 00000000`00000000 : nt!KeBugCheckEx fffff803`f7e35b70 fffff803`f5c3b253 : 00000000`00000004 fffff803`f7e35e70 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5 fffff803`f7e35cc0 fffff803`f5c3b380 : ffffe001`e291a660 fffff803`f7e35ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12b fffff803`f7e35cf0 fffff803`f5dcc57b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff803`f7e35d20 fffff803`f5dcc331 : 00000000`00000000 fffff803`f5dcc2b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b fffff803`f7e35e60 fffff800`bb7d2778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171 fffff803`f7e20748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 31d690d534614e29d1a29a50237988b87615fcf0 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ae5050f7a40b0048579d1bfde2230d3d6e82a804 THREAD_SHA1_HASH_MOD: bb9e08fd5b39c99f51340253eeb3532652890f3c FOLLOWUP_IP: intelppm!MWaitIdle+18 fffff800`bb7d2778 c3 ret FAULT_INSTR_CODE: ccccccc3 SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: intelppm!MWaitIdle+18 FOLLOWUP_NAME: MachineOwner MODULE_NAME: intelppm IMAGE_NAME: intelppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 559f383b IMAGE_VERSION: 10.0.10240.16384 BUCKET_ID_FUNC_OFFSET: 18 FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle TARGET_TIME: 2017-05-10T16:15:21.000Z OSBUILD: 10240 OSSERVICEPACK: 16384 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2015-07-10 05:29:30 BUILDDATESTAMP_STR: 150709-1700 BUILDLAB_STR: th1 BUILDOSVER_STR: 10.0.10240.16384 ANALYSIS_SESSION_ELAPSED_TIME: 558 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle FAILURE_ID_HASH: {d82f1232-e6fd-ac41-d01e-ddeec73b684b} Followup: MachineOwner --------- GetPointerFromAddress: unable to read from fffff803f603b1c0 THREAD fffff803f604f740 Cid 0000.0000 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0 Not impersonating GetUlongFromAddress: unable to read from fffff803f5f89f38 Owning Process fffff803f604ea40 Image: Attached Process ffffe001e28e2840 Image: System fffff78000000000: Unable to get shared data Wait Start TickCount 6089 Context Switch Count 95507 IdealProcessor: 0 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address nt!KiIdleLoop (0xfffff803f5dc5920) Stack Init fffff803f7e20b90 Current fffff803f7e20b20 Base fffff803f7e21000 Limit fffff803f7e1a000 Call 0000000000000000 Priority 0 BasePriority 0 PriorityDecrement 0 IoPriority 0 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site fffff803`f7e35b68 fffff803`f5c3ae11 : 00000000`0000009c 00000000`00000000 fffff803`f7e35ba0 00000000`00000000 : nt!KeBugCheckEx fffff803`f7e35b70 fffff803`f5c3b253 : 00000000`00000004 fffff803`f7e35e70 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5 fffff803`f7e35cc0 fffff803`f5c3b380 : ffffe001`e291a660 fffff803`f7e35ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12b fffff803`f7e35cf0 fffff803`f5dcc57b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff803`f7e35d20 fffff803`f5dcc331 : 00000000`00000000 fffff803`f5dcc2b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b fffff803`f7e35e60 fffff800`bb7d2778 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171 (TrapFrame @ fffff803`f7e35e70) fffff803`f7e20748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18 GetPointerFromAddress: unable to read from fffff803f603b1c0 PROCESS ffffe001e28e2840 SessionId: none Cid: 0004 Peb: 00000000 ParentCid: 0000 DirBase: 001ab000 ObjectTable: ffffc00131e14000 HandleCount: <Data Not Accessible> Image: System VadRoot ffffe001e4210aa0 Vads 10 Clone 0 Private 22. Modified 19996. Locked 64. DeviceMap ffffc00131e16620 Token ffffc00131e16a60 ReadMemory error: Cannot get nt!KeMaximumIncrement value. fffff78000000000: Unable to get shared data ElapsedTime 00:00:00.000 UserTime 00:00:00.000 KernelTime 00:00:00.000 QuotaPoolUsage[PagedPool] 0 QuotaPoolUsage[NonPagedPool] 0 Working Set Sizes (now,min,max) (139, 50, 450) (556KB, 200KB, 1800KB) PeakWorkingSetSize 1424 VirtualSize 3 Mb PeakVirtualSize 11 Mb PageFaultCount 21829 MemoryPriority BACKGROUND BasePriority 8 CommitCharge 31 *** Error in reading nt!_ETHREAD @ ffffe001e297a300 [BIOS Information (Type 0) - Length 24 - Handle 0000h] Vendor American Megatrends Inc. BIOS Version 3401 BIOS Starting Address Segment f000 BIOS Release Date 03/15/2017 BIOS ROM Size 1000000 BIOS Characteristics 07: - PCI Supported 10: - APM Supported 11: - Upgradeable FLASH BIOS 12: - BIOS Shadowing Supported 15: - CD-Boot Supported 16: - Selectable Boot Supported 17: - BIOS ROM Socketed 19: - EDD Supported 23: - 1.2MB Floppy Supported 24: - 720KB Floppy Supported 25: - 2.88MB Floppy Supported 26: - Print Screen Device Supported 27: - Keyboard Services Supported 28: - Serial Services Supported 29: - Printer Services Supported 32: - BIOS Vendor Reserved BIOS Characteristic Extensions 00: - ACPI Supported 01: - USB Legacy Supported 08: - BIOS Boot Specification Supported 10: - Specification Reserved 11: - Specification Reserved BIOS Major Revision 5 BIOS Minor Revision 12 EC Firmware Major Revision 255 EC Firmware Minor Revision 255 [System Information (Type 1) - Length 27 - Handle 0001h] Manufacturer System manufacturer Product Name System Product Name Version System Version Serial Number UUID 00000000-0000-0000-0000-000000000000 Wakeup Type Power Switch SKUNumber SKU Family To be filled by O.E.M. [BaseBoard Information (Type 2) - Length 15 - Handle 0002h] Manufacturer ASUSTeK COMPUTER INC. Product Z170 PRO GAMING/AURA Version Rev X.0x Serial Number Asset Tag Feature Flags 09h 741062368: - 741062416: - ȾW;Ø Location Default string Chassis Handle 0003h Board Type 0ah - Processor/Memory Module Number of Child Handles 0 [System Enclosure (Type 3) - Length 22 - Handle 0003h] Manufacturer Default string Chassis Type Desktop Version Default string Serial Number Asset Tag Number Bootup State Safe Power Supply State Safe Thermal State Safe Security Status None OEM Defined 0 Height 0U Number of Power Cords 1 Number of Contained Elements 0 Contained Element Size 3 [Onboard Devices Information (Type 10) - Length 6 - Handle 0027h] Number of Devices 1 01: Type Video [enabled] 01: Description To Be Filled By O.E.M. [OEM Strings (Type 11) - Length 5 - Handle 0028h] Number of Strings 8 1 Default string 2 Default string 3 Edison 4 Default string 5 FFFFFFFFFFFFF 6 FFFFFFFFFFFFF 7 FFFFFFFFFFFFF 8 Default string [System Configuration Options (Type 12) - Length 5 - Handle 0029h] [Physical Memory Array (Type 16) - Length 23 - Handle 0044h] Location 03h - SystemBoard/Motherboard Use 03h - System Memory Memory Error Correction 03h - None Maximum Capacity 67108864KB Memory Error Inf Handle [Not Provided] Number of Memory Devices 4 [Memory Device (Type 17) - Length 40 - Handle 0045h] Physical Memory Array Handle 0044h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM_A1 Bank Locator BANK 0 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-3466C16-4GVK [Memory Device (Type 17) - Length 40 - Handle 0046h] Physical Memory Array Handle 0044h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM_A2 Bank Locator BANK 1 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-3466C16-4GVK [Memory Device (Type 17) - Length 40 - Handle 0047h] Physical Memory Array Handle 0044h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM_B1 Bank Locator BANK 2 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-3466C16-4GVK [Memory Device (Type 17) - Length 40 - Handle 0048h] Physical Memory Array Handle 0044h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM_B2 Bank Locator BANK 3 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-3466C16-4GVK [Memory Array Mapped Address (Type 19) - Length 31 - Handle 0049h] Starting Address 00000000h Ending Address 00ffffffh Memory Array Handle 0044h Partition Width 04 [Cache Information (Type 7) - Length 19 - Handle 004ah] Socket Designation L1 Cache Cache Configuration 0180h - WB Enabled Int NonSocketed L1 Maximum Cache Size 0100h - 256K Installed Size 0100h - 256K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type ParitySingle-Bit ECC System Cache Type Unified Associativity 8-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 004bh] Socket Designation L2 Cache Cache Configuration 0181h - WB Enabled Int NonSocketed L2 Maximum Cache Size 0400h - 1024K Installed Size 0400h - 1024K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type Multi-Bit ECC System Cache Type Unified Associativity 4-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 004ch] Socket Designation L3 Cache Cache Configuration 0182h - WB Enabled Int NonSocketed L3 Maximum Cache Size 1800h - 6144K Installed Size 1800h - 6144K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type Specification Reserved System Cache Type Unified Associativity Specification Reserved [Processor Information (Type 4) - Length 48 - Handle 004dh] Socket Designation LGA1151 Processor Type Central Processor Processor Family cdh - Specification Reserved Processor Manufacturer Intel(R) Corporation Processor ID e3060500fffbebbf Processor Version Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Processor Voltage 8bh - 1.1V External Clock 100MHz Max Speed 8300MHz Current Speed 3500MHz Status Enabled Populated Processor Upgrade Other L1 Cache Handle 004ah L2 Cache Handle 004bh L3 Cache Handle 004ch Serial Number Asset Tag Number Part Number To Be Filled By O.E.M. [Memory Device Mapped Address (Type 20) - Length 35 - Handle 004eh] Starting Address 00000000h Ending Address 003fffffh Memory Device Handle 0045h Mem Array Mapped Adr Handle 0049h Partition Row Position [Unknown] Interleave Position 01 Interleave Data Depth 02 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 004fh] Starting Address 00800000h Ending Address 00bfffffh Memory Device Handle 0046h Mem Array Mapped Adr Handle 0049h Partition Row Position [Unknown] Interleave Position 01 Interleave Data Depth 02 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 0050h] Starting Address 00400000h Ending Address 007fffffh Memory Device Handle 0047h Mem Array Mapped Adr Handle 0049h Partition Row Position [Unknown] Interleave Position 02 Interleave Data Depth 02 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 0051h] Starting Address 00c00000h Ending Address 00ffffffh Memory Device Handle 0048h Mem Array Mapped Adr Handle 0049h Partition Row Position [Unknown] Interleave Position 02 Interleave Data Depth 02 CPUID: "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz" MaxSpeed: 3500 CurrentSpeed: 3504[/quote]

 

Hi Xavier Enrique,

A next step would be to ensure that Windows is up to date, since the initial release of Windows 10 there have been a few feature versions released and several bugfixes implemented including for BSODs.
Upgrade to Windows 10 Windows 10 Installation Upgrade Tutorials

 

Hmm, I only fresh-installed it using my Windows 10 Pro DVD disc, so your suggestion sounds like a great idea. It might actually solve the issue. Only problem is, I believe it won't let me do the upgrade from Safe Mode, and Normal Mode always crashes. Is there a way to do it from Safe Mode?

 

You could try step 6, but instead boot from the media, *Arrow Upgrade to Windows 10 Windows 10 Installation Upgrade Tutorials

A warning, you may end up with a clean install since you cannot upgrade an already installed OS when booting from the media.

 

Nevermind guys, now it won't let me boot not even to Safe Mode, and I disconnected the SSD, GPU and Optical Drive, and it still freezes, even in BIOS... I either messed up the MOBO when I dropped a screw onto it, or I damaged the CPU when I went to reseat the GPU and accidentally hit the heatsink. Problem is I don't have spare parts to do tests. According to your experience, or according to the minidumps, what do you think it actually is? So I could try get a replacement part, since I believe both (MOBO and CPU) are under warranty (they are 5 months old only).

Question: Is there a chance it could be just a loose cable?

 

Depending on where a screw is dropped it may or may not be vital.

Could you check the CPU and socket for any damage?
What cooler do you use?


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

 

I did yesterday, and the pins on the CPU looked fine to me (I looked up pics on Google and compared), and also the socket looked fine (I compared it with pics of the same MOBO on Google as well). I use Gammaxx Deepcool 400 (it's pretty good, it keeps the CPU at 32ish° Celsius while it's idle)... I fear I cannot use that tool since my PC now won't even boot. I had submitted my specs when I registered to this site, but if you need them, I can just type them here:

CPU: I5-6600K
Motherboard: Z170 Pro Gaming Aura
PSU: EVGA G2L 850W
GPU: MSI Radeon RX 480 8GB
SSD: Samsung 850 Evo
Optical Drive: Asus Blu-ray BC12B1ST
UPS: Cyberpower 1500 VA 900W
Heatsink: Gammaxx Deepcool 400

The case is a Full-Tower case and has plenty of space for air flow.

 

Is there a chance that if the heatsink is not making good contact, or it's somehow loose, that itself could be the cause of the crashes?

 

The heat likely wouldn't move away from the CPU causing overheating if that would be the case, I assume you have placed it correctly last time you opened the case?

Do you know where you dropped a screw on the motherboard?