Windows 7: BSOD while gaming - Unknown_Module_ffffffff`ffffffff

Akoni · 09 Jul 2014

As the title states, BSOD and not sure of what the cause could be. Maybe someone can analize a dump file to see what's up?

That audio stutter loop crash is really annoying..

koolkat77 · 09 Jul 2014

Hi,

Seems like a hardware error.

Code:

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


Loading Dump File [C:\Users\USER\Downloads\minidump792014\070914-5896-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_ffffffff`ffffffff, Win32 error 0n2
Unable to add module at ffffffff`ffffffff
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344a890
Debug session time: Wed Jul  9 19:39:44.997 2014 (UTC + 6:00)
System Uptime: 1 days 17:54:34.825
Unable to load image Unknown_Module_ffffffff`ffffffff, Win32 error 0n2
Unable to add module at ffffffff`ffffffff
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to add module at ffffffff`ffffffff

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800db6e028, be200000, 5110a}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image

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

0: 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: fffffa800db6e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`04d40a98 fffff800`037fea3b : 00000000`00000124 00000000`00000000 fffffa80`0db6e028 00000000`be200000 : 0xfffff800`0327cbc0
fffff800`04d40aa0 00000000`00000124 : 00000000`00000000 fffffa80`0db6e028 00000000`be200000 00000000`0005110a : 0xfffff800`037fea3b
fffff800`04d40aa8 00000000`00000000 : fffffa80`0db6e028 00000000`be200000 00000000`0005110a fffffa80`0d7a7bd0 : 0x124


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Quote:

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

Akoni · 09 Jul 2014

Quote:

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

Think a driver could also be the cause?

At first I was worried it might be related to my cpu overclock, but I dialed that back and passed stress tests. The only things I could think of with hardware is either the usual suspect of RAM or my graphics card. That or heat. I hate 124 because it's so vague and not always an indicator of an actual fault with hardware being damaged.

I might run Prime 95 before going to bed later on and see if I wake up to a stable system. Passed stress tests before with Intel Burn Test, but this might be worth a shot.

Arc · 15 Jul 2014

The default bucket ID is the default. Same for all the cases. No decision can be framed based on it.

Still, there is a chance that the BSODs might be caused by any device driver, but the hardware is the primary place to search for the root of the issue in your case.

Follow the link given in post #2. Let us know about your advancement.