Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD (with increasing occurences after wiping ssd+reinstalling Win7)

4 Weeks Ago   #1
deviousrakun

Windows 7 Home Premiumx64
 
 
BSOD (with increasing occurences after wiping ssd+reinstalling Win7)

I have been experience blue screens for the last two weeks or so, usually while playing a game (during LoL) but not always. I was on Win10 at the time and had decided that, since I wanted to go back to 7 anyways, I could start fresh and then work from a blank slate if the blue screens kept happening, so I wiped my ssd and started new on 7. Unfortunately, they are still happening and with more frequency. I'm still pretty new to building computers so assessing one for a blue screen is giving me a lot of grief, I would really appreciate any help. I have attached the files as requested in the instructions, I tried using bluescreenviewer to perhaps understand what was happening better but it was blank; however, my event viewer has plenty of critical events in it.




Attached Files
File Type: zip HARM-PC-22_05_2019__65934_86.zip (254.5 KB, 2 views)
My System SpecsSystem Spec
.
4 Weeks Ago   #2
wither 2

Windows 7 Pro SP1 64 bit
 
 

Open the .zip file and go to System Information.

In Components, Problem Devices, you're missing a bunch of drivers.

I'm not sure why the log generated by the BSOD isn't there. Also, I don't see any significant problems in the Event log.
My System SpecsSystem Spec
4 Weeks Ago   #3
deviousrakun

Windows 7 Home Premiumx64
 
 

I really appreciate your answer. I'll try to download those drivers asap and get back to the thread!
My System SpecsSystem Spec
.

4 Weeks Ago   #4
deviousrakun

Windows 7 Home Premiumx64
 
 

I've downloaded a few one them, atm I still am missing the multimedia controller, the pci simple communications controller, and whatever... "not available" could be. I downloaded realtek high definition audio drivers but.. it says that high definition audio cannot start in system information. However, when I go to device manager there are two high definition audio devices and only one has an exclamation mark on it, is that normal?
My System SpecsSystem Spec
3 Weeks Ago   #5
deviousrakun

Windows 7 Home Premiumx64
 
 

I've had two blue screens since adding some of these drivers and now my mouse/keyboard lock for a good twenty seconds upon startup, here are the logs contained in a new zip..


Attached Files
File Type: zip HARM-PC-22_05_2019_163027_59.zip (575.5 KB, 2 views)
My System SpecsSystem Spec
3 Weeks Ago   #6
MrPepka

Windows 8.1 Enterprise x64
 
 

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
1st parameter - 0x0 = A machine check exception occurred.
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\052219-3463-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24441.amd64fre.win7sp1_ldr.190418-1735
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c39c90
Debug session time: Thu May 23 00:23:50.519 2019 (UTC + 2:00)
System Uptime: 0 days 0:02:54.721
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800db90028, bf800000, 124}

Probably caused by : GenuineIntel

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

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

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.24441.amd64fre.win7sp1_ldr.190418-1735

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0902

BIOS_DATE:  05/08/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z97-A

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: fffffa800db90028

BUGCHECK_P3: bf800000

BUGCHECK_P4: 124

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: d4d

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 19'00000000 (cache) 19'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  TrustedInstaller.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  05-23-2019 13:17:49.0883

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:  
fffff880`009b4bb8 fffff800`02fef9ef : 00000000`00000124 00000000`00000000 fffffa80`0db90028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`009b4bc0 fffff800`02b8ed2f : 00000000`00000001 fffffa80`0d2499a0 00000000`00000000 fffffa80`0d2499f0 : hal!HalBugCheckSystem+0x1e3
fffff880`009b4c00 fffff800`02fef6b4 : 00000000`00000728 fffffa80`0d2499a0 fffff880`009b4f90 fffff880`009b4f00 : nt!WheaReportHwError+0x26f
fffff880`009b4c60 fffff800`02fef006 : fffffa80`0d2499a0 fffff880`009b4f90 fffffa80`0d2499a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009b4db0 fffff800`02feeec1 : 00000000`00000004 00000000`00000001 fffff880`009b5010 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009b4df0 fffff800`02fe2e58 : fffff880`020198f0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009b4e20 fffff800`02aa07ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009b4e50 fffff800`02aa0629 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009b4f90 fffff880`010ba7b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x169
fffff880`020197f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetStartingCallbackNode+0x49


THREAD_SHA1_HASH_MOD_FUNC:  393c0921cd0787ec2d6550c770a971bcca7254ea

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5f0af362812aa4cdae6fde21a673fbfd1fca2bc5

THREAD_SHA1_HASH_MOD:  824014ab67f33da267d35cd670fcf5161e5b81bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

TARGET_TIME:  2019-05-22T22:23:50.000Z

OSBUILD:  7601

OSSERVICEPACK:  1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-04-19 04:08:54

BUILDDATESTAMP_STR:  190418-1735

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24441.amd64fre.win7sp1_ldr.190418-1735

ANALYSIS_SESSION_ELAPSED_TIME:  560

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

Followup:     MachineOwner
---------
Checking the second parameter with the !errrec command gives this result:
Code:
3: kd> !errrec fffffa800db90028
===============================================================================
Common Platform Error Record @ fffffa800db90028
-------------------------------------------------------------------------------
Record Id     : 01d510eca05ae782
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/22/2019 22:23:50 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800db900a8
Section       @ fffffa800db90180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800db900f0
Section       @ fffffa800db90240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb da 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  @ fffffa800db90240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800db90138
Section       @ fffffa800db902c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 3 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000043e4a7580
  Misc.       : 0x0000000000000086
According to Intel processor documentation, the Error field means that an error occurred while writing data (D = Data, L0 = Level 0, WR = Generic Write). Update BIOS (Z97-A BIOS & FIRMWARE | Motherboards | ASUS USA) to the newest version
My System SpecsSystem Spec
Reply

 BSOD (with increasing occurences after wiping ssd+reinstalling Win7)




Thread Tools




Similar help and support threads
Thread Forum
Restoring Only WIN7 after Wiping Hard Drive
Please forgive me, I'm sure that this has been covered in the past. I have an ACER desktop that I'm going to give away. It has WIN7 Home Premium in a recovery partition but no program disks. The hard drive is full of financial info so my plan was to do a system image and use DBAN to wipe...
General Discussion
Random BSOD 0x124 occurences
Hello, I've been plagued by a BSOD issue for quite a while already and ultimately I have failed to fix it by myself so I would like to ask for some help. As a sort of user-gathered information its probably important for me to mention the following things: 1) the BSOD always gives the same...
BSOD Help and Support
BSOD while playing LoL, affected avast!, BSOD when reinstalling Win7
Hello guys. Problem started quite recently, I bought a new computer a month ago, and everything was cool until it started giving me MANY BSODs affter one intitial BSOD while playing League Of Legends. After a first crash, Windows asked during boot if i want to run a recovery utility, and each...
BSOD Help and Support
BSOD 0x124 random occurences
Hey guys, I am currently putting up a new system and trying to determine what the cause of my BSOD is. I am running an MSI Z77A-G45 I7 3770K Ballistix 8GB DDR3 - 1600 OR Mushkin Enchanced 8GB 2X4GB PC3-10666 DDR3-1333 9-9-9-24 Dual Channel 560 GTX Gigabyte 3 TB WD Green 60 GB OCZ Agility...
BSOD Help and Support
Wiping out and Reinstalling Windows 7
I bought a HP G60 Laptop about a year and half ago. I have been wanting to wipe the computer out and re-install Windows 7. When I bought the laptop it didn't come with an install disc. My question is, is there any possible way to wipe out my laptop and re-install windows 7, and use the same...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 16:16.
Twitter Facebook