W waggyman101 New member Joined Aug 25, 2015 Posts 3 Aug 25, 2015 #1 Hello, I have recently been getting a BSOD error. I have attached the SysnativeFileCollectionApp output folder. Below is my pc spec. · OS - Windows 10 · x64 · What was original installed OS on system? - Windows 7 Professional · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Free download of Windows 10 from Microsoft · Age of system (hardware) - 12 months · Age of OS installation - have you re-installed the OS? - 1 month · CPU - Intel i7 4790k · Video Card - NVIDIA GTX 770 (ASUS Direct CUii) · MotherBoard - Gigabyte Z97P-D3 · Power Supply - brand & wattage - Corsair 600W Builder Series · System Manufacturer - Custom Build · Exact model number (if laptop, check label on bottom) - N/A · Laptop or Desktop? - Desktop Please can you tell me where the fault lies and how to correct it? Many thanks, Regards, Andrew. Attachments SysnativeFileCollectionApp.zip 1.2 MB · Views: 1
Hello, I have recently been getting a BSOD error. I have attached the SysnativeFileCollectionApp output folder. Below is my pc spec. · OS - Windows 10 · x64 · What was original installed OS on system? - Windows 7 Professional · Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Free download of Windows 10 from Microsoft · Age of system (hardware) - 12 months · Age of OS installation - have you re-installed the OS? - 1 month · CPU - Intel i7 4790k · Video Card - NVIDIA GTX 770 (ASUS Direct CUii) · MotherBoard - Gigabyte Z97P-D3 · Power Supply - brand & wattage - Corsair 600W Builder Series · System Manufacturer - Custom Build · Exact model number (if laptop, check label on bottom) - N/A · Laptop or Desktop? - Desktop Please can you tell me where the fault lies and how to correct it? Many thanks, Regards, Andrew.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,185 Location %systemroot% Aug 25, 2015 #2 It appears that you may have been running the Prime95 stress test, what were the hardware temperatures during the test? Code: BugCheck 124, {0, ffffe001540b4028, be000000, 800400} Probably caused by : GenuineIntel A Stop 0x124 typically indicates some form of hardware issue or failure, this dump file particularly points to the processor. Code: 1: kd> !errrec ffffe001540b4028 =============================================================================== Common Platform Error Record @ ffffe001540b4028 ------------------------------------------------------------------------------- Record Id : 01d0df684f8c970c Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/25/2015 19:04:35 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001540b40a8 Section @ ffffe001540b4180 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 @ ffffe001540b40f0 Section @ ffffe001540b4240 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 @ ffffe001540b4240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001540b4138 Section @ ffffe001540b42c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 1 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff80079fc3651 Misc. : 0xfffff80079fc3651
It appears that you may have been running the Prime95 stress test, what were the hardware temperatures during the test? Code: BugCheck 124, {0, ffffe001540b4028, be000000, 800400} Probably caused by : GenuineIntel A Stop 0x124 typically indicates some form of hardware issue or failure, this dump file particularly points to the processor. Code: 1: kd> !errrec ffffe001540b4028 =============================================================================== Common Platform Error Record @ ffffe001540b4028 ------------------------------------------------------------------------------- Record Id : 01d0df684f8c970c Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/25/2015 19:04:35 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe001540b40a8 Section @ ffffe001540b4180 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 @ ffffe001540b40f0 Section @ ffffe001540b4240 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 @ ffffe001540b4240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001540b4138 Section @ ffffe001540b42c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 1 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff80079fc3651 Misc. : 0xfffff80079fc3651
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,185 Location %systemroot% Aug 25, 2015 #3 Another dump file: Code: BugCheck 50, {ffffe0010200005b, 0, fffff8009cb724a2, 2} Probably caused by : cpuz138_x64.sys ( cpuz138_x64+24a2 ) Code: 1: kd> lmvm cpuz138_x64 start end module name fffff800`9cb70000 fffff800`9cb7a000 cpuz138_x64 T (no symbols) Loaded symbol image file: cpuz138_x64.sys Image path: \??\C:\Users\Andrew\AppData\Local\Temp\cpuz138\cpuz138_x64.sys Image name: cpuz138_x64.sys Timestamp: Thu Oct 23 16:03:05 2014 (544918A9) CheckSum: 0000B4BC ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 The driver appears to belong to CPUID CPU-Z, and is may be why the Stop 0x124 BSOD was produced too, since this driver will typically hook into the ACPI tables to gather information about the processor and other hardware information. I would suggest looking for an update or removing the program, since I doubt this program is supported on Windows 10 systems - CPU-Z | Softwares | CPUID Code: 1: kd> .trap 0xffffd00020dfb3d0 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=ffffe00102000043 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8009cb724a2 rsp=ffffd00020dfb560 rbp=ffffd00020dfbb80 r8=ffffe001f88e8610 r9=000000000000000e r10=0000000020206f49 r11=ffffe001f8903780 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cpuz138_x64+0x24a2: fffff800`9cb724a2 488b4a18 mov rcx,qword ptr [rdx+18h] ds:ffffe001`0200005b=???????????????? It appears to be referencing an invalid memory address or not properly handling a memory access operation.
Another dump file: Code: BugCheck 50, {ffffe0010200005b, 0, fffff8009cb724a2, 2} Probably caused by : cpuz138_x64.sys ( cpuz138_x64+24a2 ) Code: 1: kd> lmvm cpuz138_x64 start end module name fffff800`9cb70000 fffff800`9cb7a000 cpuz138_x64 T (no symbols) Loaded symbol image file: cpuz138_x64.sys Image path: \??\C:\Users\Andrew\AppData\Local\Temp\cpuz138\cpuz138_x64.sys Image name: cpuz138_x64.sys Timestamp: Thu Oct 23 16:03:05 2014 (544918A9) CheckSum: 0000B4BC ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 The driver appears to belong to CPUID CPU-Z, and is may be why the Stop 0x124 BSOD was produced too, since this driver will typically hook into the ACPI tables to gather information about the processor and other hardware information. I would suggest looking for an update or removing the program, since I doubt this program is supported on Windows 10 systems - CPU-Z | Softwares | CPUID Code: 1: kd> .trap 0xffffd00020dfb3d0 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=ffffe00102000043 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8009cb724a2 rsp=ffffd00020dfb560 rbp=ffffd00020dfbb80 r8=ffffe001f88e8610 r9=000000000000000e r10=0000000020206f49 r11=ffffe001f8903780 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cpuz138_x64+0x24a2: fffff800`9cb724a2 488b4a18 mov rcx,qword ptr [rdx+18h] ds:ffffe001`0200005b=???????????????? It appears to be referencing an invalid memory address or not properly handling a memory access operation.
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Aug 26, 2015 #4 I've seen a few crashes caused by CPU-Z, it's not common but I've seen it happen a couple of times.
W waggyman101 New member Joined Aug 25, 2015 Posts 3 Aug 26, 2015 #5 Hello x BlueRobot, Thanks for the quick reply. I'm afraid CPU-Z is a red herring as I had removed it prior to sending you the BSOD details. Yes I did run Prime95. It displayed 7 tasks as I recall but about a minute into test 1 the pc locked up and I had to power off. The temperatures for the CPU show the 4 cores hitting 95 and 100 degrees. I have rerun Prime95 a further 2 times and the pc locks up between 1 and 5 minutes into the test. Hope this helps. Andrew,
Hello x BlueRobot, Thanks for the quick reply. I'm afraid CPU-Z is a red herring as I had removed it prior to sending you the BSOD details. Yes I did run Prime95. It displayed 7 tasks as I recall but about a minute into test 1 the pc locked up and I had to power off. The temperatures for the CPU show the 4 cores hitting 95 and 100 degrees. I have rerun Prime95 a further 2 times and the pc locks up between 1 and 5 minutes into the test. Hope this helps. Andrew,
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Aug 27, 2015 #6 It's locking up because your CPU is overheating. You need to bring those temperatures down. Although by the looks of things, it would appear the CPU has already been damaged. I recommend you just RMA the CPU.
It's locking up because your CPU is overheating. You need to bring those temperatures down. Although by the looks of things, it would appear the CPU has already been damaged. I recommend you just RMA the CPU.