BSOD terrorizing and hamstring my finals

Operating Systems & Open Source Windows
,
1

Greetings, everyone!

I'm coming to the end of the semester in my Design Engineering course, but I can't finish my work without a working computer. Granted, there are working computers at campus, but I have two monitors and more power, and the same software as they do.

The all-encompasing bluish hue first struck me last night, with the error message "WHEA_UNCORRECTABLE_ERROR". I called Microsoft to get an idea of why this was occurring, and the guy said it might be hardware related. (This was the most suitable sub-forum I could find, by the way.)

And thusly, I began troubleshooting by removing my graphics card and running display off of the processor. That didn't solve it, so I removed a stick of RAM. That didn't solve it either, so I moved the first stick to a new socket. To no avail, so I took the first stick and well... I tried most combinations. I called the online store from which I bought the parts, and the guy mentioned memtest, so I ran a few passes of that. 0 errors.

So I dove deeper into the search results for the error message, reading replies from all sorts of qualified personnel. Many claimed a fresh installation would do the trick, so I made a bootable stick from my Macbook with the latest thing from Microsoft and tried repairing. Halfway through 'preparing files' or something, the BSOD attacked again. Having backed up my stuff in safe mode earlier, I formatted the SSD and ran a clean installation.

BSOD!!!

Time to call in the cavalry (read: you).

I haven't touched the computer since the last BSOD, and it has cycled through the thing a few times, finally settling at the recovery dialogue.

I regret to say I don't have the dump files, but I can tell you they were all identical, and Bluescreenview listed two things as red: hal.dll and ntoskrnl.exe.

I can probably export some dump files for you to examine, but I also need to work. Just let me know! There's no way of knowing if the bluescreen will strike immediately after logging in, or five minutes later, but working is impossible.

Please, please, please help me!

@Novasty
@Dynamic_Gravity
@Commissar
@PhaseLockedLoop
@Peanut253

1 Like
2

What version of windows?
What build if windows 10?
What was the error code?

Is your processor overclocked?
Hardware specifications?
Is your firmware up to date?

3

Pc Specs! That would help a lot, whilst I am here, any overclocks?

4

Bah! Beat me to it!

5

I got ahead of myself, sorry. Figured I should get the message out asap!

It's Windows 10 Pro N 1703 15063.0.

The error code is always "WHEA_UNCORRECTABLE_ERROR".

My i5-7600K was overclocked to 5 GHz when I started, but it typically ran at below 60 °C. Reverting to default clock was one of my first actions.

Parts:
ASUS ROG Strix Z270G Gaming
Intel Core i5-7600K
Corsair Vengeance LPX 16GB 2133MHz DDR4
ASUS ROG STRIX-RX480-8G-GAMING
Intel 600P Series 256GB M.2
Corsair Hydro Series H60

6

In other news, we have a new record time without bluescreen. 15 minutes. Not touching it with a pole.

EDIT: 17 minutes and it died.

7

I've never come across the error, but the internet suggests it might be cause by overclocking and the CPU failing.

Might want to check that the CPU is failing or not. (don't know what the best way to do that is)

8

Since we don't have the dump files for me to examine, best assumption: Uninstall any ASUS software. That error has been associated with ASUS overclocking software before and drivers.

EDIT: If you have read my post regarding bluescreens, I called BlueScreenView a piece of shit because it doesn't provide enough relevant information. If possible please upload the dumps for us to look at.

9
10

Don't hestitate if you need more files. My computer is practically a self-going dump file generator at this point.

11

Can you do a memtest?

Loading Dump File [C:\Users******\Downloads\Dumps\Minidump\060117-3421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred symsrv*symsrv.dll*e:\localsymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: symsrv*symsrv.dll*e:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff80017c1d000 PsLoadedModuleList = 0xfffff80017f695a0
Debug session time: Thu Jun 1 12:47:31.773 2017 (UTC - 6:00)
System Uptime: 0 days 0:02:05.416
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
........

  • *
  • Bugcheck Analysis *
  • *

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffce8fcadaa028, f617e780, 40150}

Probably caused by : memory_corruption

Followup: memory_corruption

3: kd> !analyze -v

  • *
  • Bugcheck Analysis *
  • *

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: ffffce8fcadaa028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f617e780, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0701

BIOS_DATE: 12/28/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: STRIX Z270G GAMING

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce8fcadaa028

BUGCHECK_P3: f617e780

BUGCHECK_P4: 40150

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: ed0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: SearchFilterHo

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: NE***

ANALYSIS_SESSION_TIME: 06-01-2017 13:11:30.0728

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
ffffe4819696e6b8 fffff800184df5cf : 0000000000000124 0000000000000000 ffffce8fcadaa028 00000000f617e780 : nt!KeBugCheckEx
ffffe4819696e6c0 fffff80017e78fbd : ffffce8fcadaa028 ffffce8fc991c3e0 ffffce8fc991c3e0 ffffce8fc991c3e0 : hal!HalBugCheckSystem+0xcf
ffffe4819696e700 fffff800184dfaf8 : 0000000000000728 0000000000000003 0000000000000000 0000000000000000 : nt!WheaReportHwError+0x25d
ffffe4819696e760 fffff800184dfe58 : 0000000000000010 0000000000000003 ffffe4819696e908 0000000000000003 : hal!HalpMcaReportError+0x50
ffffe4819696e8b0 fffff800184dfd46 : ffffce8fc96e8870 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xe0
ffffe4819696e900 fffff800184dff8a : 0000000000000004 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xda
ffffe4819696e940 fffff800184e0120 : ffffce8fc96e8870 ffffe4819696eb70 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffe4819696e970 fffff80017d931bb : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40
ffffe4819696e9a0 fffff80017d92f2c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7b
ffffe4819696eae0 00007ffeb2399a05 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x1ac
000000a8a82fef20 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`b2399a05

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80017ca7e10-fffff80017ca7e11 2 bytes - nt!MiRemoveAnyPage+140
[ 80 fa:00 9e ]
2 errors : !nt (fffff80017ca7e10-fffff80017ca7e11)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE

TARGET_TIME: 2017-06-01T18:47:31.000Z

OSBUILD: 15063

OSSERVICEPACK: 0

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: 2017-03-17 22:40:44

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 1219

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_large

FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption

12

I ran one earlier and it didn't find any errors. Any particular settings I should use?

13

Try running 1 stick at a time to figure out which stick is the defective one.

1 Like
14

First stick in slot A2, running memtest with default settings.

15

An option you could do after the memtest. Try using your computer for an hour or two with one stick, then again with the other stick.

16

Approximately how long does a memtest for 8 gb take? Do they need complete runs?

17

I wouldn't know that answer, I rarely run memtest so I don't have a solid time for this. When I do, it is usually at work where it is the DELL built-in memtest which takes like 2~3hours for 8GB of memory.

18

Working on second out of four passes now, so it looks like ~15 mins per pass.

19

Almost finished with last pass. If there are no errors, would that rule out memory as the cause of the crashing?

20

I would still test the computer 1 stick at a time for about an hour or two for each. If it triggers on both, it may be a bad CPU.

1 Like