BSOD at user login screen with error 0x000000c4

[lenneth73]

Hi everybody,

I'd like to request some help for solving my BSOD problem. It happens after I enter my login credentials at the user login screen. Sometimes I don't even have time to type them in, and the BSOD happens.

The following is an outline of events in the past few days. Hopefully it can help.

• It has been a very long time since I installed new hardware. I believe the last one was the graphics card, which was installed last year. I have not installed any new programs in the last two days.
• Yesterday, I was playing a video game and suddenly the screen froze and the audio started buzzing. I restarted the computer and was greeted with a dialog "Windos has recovered from an unexpected shutdown."
• On that next restart, I was streaming some videos and once again the video stopped. This was the second BSOD in a day.
• Today, I could not get into Windows any more because of the BSOD at the login screen.

I have accomplished the System Specs form in my profile, and have attached the log information from DM Log Collector in the post. In addition, I am posting the following basic troubleshooting steps I have already performed. Hope it helps.

• I removed my PCI wireless card. A BSOD still happens.
• I removed my graphics card from its slot. The BSOD still happens.
• I performed a System Restore to a restore point last week, before the BSODs began. The BSOD still happens.
• Logging in to safe mode does not trigger a BSOD.
• Logging in to an alternative OS installed (Fedora 16) does not show any sign of critical errors, as far as I can see. (Not very experienced with any Linux distros however.) I'm not sure but perhaps this rules out a bad RAM chip.

Thank you for reading. Your help would be very much appreciated.

EDIT: I managed to stop the BSODs by disabling Driver Verifier (I'm not exactly sure why it was set to on). I don't know if there is still an underlying reason for the verifier failures though.

 

[koolkat77]

Welcome to the forum.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\debug-pc-07_12_2014_Sat_190839_10\071114-14133-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x83615000 PsLoadedModuleList = 0x8375e5b0
Debug session time: Thu Jul 10 23:15:03.802 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:07.254
Loading Kernel Symbols
..........................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8686b8fc, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

1: 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: 00000000, Machine Check Exception
Arg2: 8686b8fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8b91fcc4 836e686d 8686b8e0 8377d988 8377d980 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8b91fce4 836e7689 8377d980 8686b8e0 8377d9b0 nt!WheapProcessWorkQueueItem+0x56
8b91fd00 8369214b 8377d980 00000000 856dca70 nt!WheapWorkQueueWorkerRoutine+0x1f
8b91fd50 8381e141 00000001 a9a9ea9a 00000000 nt!ExpWorkerThread+0x10d
8b91fd90 836c5559 8369203e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------