New
#1
Bsod whea_uncorrectable_error
Just got my new ram, experienced this same crash on my old ram a few days ago to. beginning to think my mobo is bad or sucks, here is the dump.
Just got my new ram, experienced this same crash on my old ram a few days ago to. beginning to think my mobo is bad or sucks, here is the dump.
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. 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 0x124 - what it means and what to try
Also please update the old drivers
How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
Thanks
Ken
Analysis
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\072910-14695-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;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50 Debug session time: Thu Jul 29 19:33:49.015 2010 (GMT-4) System Uptime: 0 days 2:16:38.686 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ .................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa80049aa028, b2674000, 175} Probably caused by : hardware Followup: MachineOwner ---------
Old drivers needing updating
Code:RTCore64.sys fffff880`06416000 fffff880`0641c000 0x00006000 0x42941d90 5/25/2005 02:39:12 usbfilter.sys fffff880`13e61000 fffff880`13e6d000 0x0000c000 0x49d5f587 4/3/2009 07:39:51 AtiPcie.sys fffff880`018a4000 fffff880`018ac000 0x00008000 0x4a005486 5/5/2009 11:00:22 spldr.sys fffff880`01485000 fffff880`0148d000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 spsys.sys fffff880`06200000 fffff880`06271000 0x00071000 0x4a085e7a 5/11/2009 13:20:58 GEARAspiWDM.sys fffff880`13e7e000 fffff880`13e8b000 0x0000d000 0x4a1151c0 5/18/2009 08:17:04 amdxata.sys fffff880`00eeb000 fffff880`00ef6000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
Are you overclocking? I see Riva Tuner installed, and you are getting a 0x124 error.
Make sure to reset all clock settings to defaults, and remove Riva Tuner.
I don't have riva installed but i had MSI after burner installed, i reverted my graphics card to stock. im just waiting to see if it does it again right now.
Well i spent a few hours playing L4D2 which is when it crashes usually happend before and same error, i did have my graphics card over clocked although i would not think it would cause a BSOD.