Blue Screen of Death, BIG problem!!!

Wtfunk · Sep 21, 2010

Hello,

Let me introduce myself, i'm Sander from the Netherlands, 23 years old and i'm experiencing a major problem. There is this BSOD I just can't get rid off. You guys probably all know this BSOD cause i'm not the only one with this problem. Anyway, this is the code: Problem signatureroblem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48Locale ID: 1043

I googled this error up, but it's so hard to find a good solution. It's very important for me that this problem is going to be fixed, cause I make professional music on this computer and I lost to many work due this BSOD. So please, please, please, HELP ME! Here is the link to my Minidump in .zip -> Minidump zip

Greets,

Sander

Tews · Sep 21, 2010

All of your .dmp files are reporting a 0x124 hardware error. This is a general hardware error, but does not specify exactly what piece of hardware is faulting... Please read this thread for possible solutions ... Stop 0x124 - what it means and what to try..

Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Code:

*******************************************************************************
*                                                                             *
*                        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: 85e6c024, Address of the WHEA_ERROR_RECORD structure.
Arg3: f609c000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 85f3f4dc, 0, 0}

Probably caused by : hardware

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

*******************************************************************************
*                                                                             *
*                        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: 85ecf024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b271c000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000175, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

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

These drivers are outdated and should be updated...

Code:

9018f000 90190420   ASACPI   ASACPI.sys   Thu Aug 12 22:52:52 2004 (411C2D04) ... Asus ATK0110 ACPI Utility (a known BSOD maker). ... [url=http://support.asus.com/download/download.aspx]ASUSTeK Computer Inc.-Support-[/url]
90871000 908b9000   netr61   netr61.sys   Thu Aug 24 23:55:21 2006 (44EE74A9) ... Most likely a Linksys Wireless Adapter (RaLink chipset) ... [url=http://www.linksysbycisco.com/US/en/support]Support and Services[/url]	
88c27000 88c4c000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9) ... nVidia Storage Drivers ... [url=http://www.nvidia.com/Download/index.aspx]Drivers - Download NVIDIA Drivers[/url]
88d64000 88d6d0c0   PxHelp20 PxHelp20.sys Mon Dec 10 18:48:39 2007 (475DD057) ... Sonic CD/DVD driver (used by many different CD/DVD programs) ... [url=http://www.carrona.org/pxhelp20.html]pxHelp20.sys programs[/url] ... Go to C:\Windows\System32\drivers and rename PxHelp20.sys to PXHelp20.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

Wtfunk · Sep 21, 2010

Thanks for the fast reply, I will try all of this and will let you know if it worked! Anyway, you made my day

zigzag3143 · Sep 21, 2010

Wtfunk said:
Hello,

Let me introduce myself, i'm Sander from the Netherlands, 23 years old and i'm experiencing a major problem. There is this BSOD I just can't get rid off. You guys probably all know this BSOD cause i'm not the only one with this problem. Anyway, this is the code: Problem signatureroblem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48Locale ID: 1043

I googled this error up, but it's so hard to find a good solution. It's very important for me that this problem is going to be fixed, cause I make professional music on this computer and I lost to many work due this BSOD. So please, please, please, HELP ME! Here is the link to my Minidump in .zip -> Minidump zip

Greets,

Sander

Hi and welcome. Thanks for the introduction

Your DMPs are being caused by hardware (BCC 124) Please read the below

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... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks

Ken

Tews · Sep 21, 2010

Be sure to let us know how it comes out...

cluberti · Sep 21, 2010

Tews said:
All of your .dmp files are reporting a 0x124 hardware error. This is a general hardware error, but does not specify exactly what piece of hardware is faulting...

Actually, that's not entirely true - it does, if you look at the error record (!errrec <param 2> from a stop 0x124). For example, the first dump in the minidump folder shows this:

Code:

0: kd> !errrec 85e6c024
...
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 85e6c134
Section       @ 85e6c2bc
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 0 Bank 0)
  Status      : 0xf609c00000000135
  Address     : 0x00000000001d5248
  Misc.       : 0x0000000000000000

It's an L1 cache error in Proc 0. Unfortuantely, the SMBIOS structures weren't in the memory captured in this dump so the sysinfo extension won't help us easily detect the CPU, but you can still look at the raw CPU info with !cpuinfo:

Code:

0: kd> !sysinfo cpuinfo
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

0: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 0 15,67,3 AuthenticAMD 3013 0000000000000000                   a01d7fff

From that (Family 15, Model 67, Stepping 3) we can deduce it's an Athlon64 X2 6000+ (~3GHz), and it's dual core. So, the first of the two cores has an L1 cache issue, so either the CPU is faulty, or there are BIOS issues. If the OP hasn't updated or touched the BIOS (or otherwise changed hardware, and thus any timings, before this occured), we can be fairly certain the CPU is going bad (it's not overclocked either, so that's another clue it's probably overheating or has been damaged by heat if it is the CPU). All of the other dumps show L1 cache errors as well, so it's pretty clear that CPU is reporting a bad L1 cache if nothing changed on the system before this started occurring.

Tews · Sep 21, 2010

Thanks for the additional info Cluberti!

Wtfunk · Sep 21, 2010

He Cluberti,

I've been monitoring my CPU's temperature and all the temperatures are stable(45-49 celsius), so that's not the problem I guess...I never tried to remove my CPU and never touched it. I will try the solutions mentioned above and will post the results this week(not experiencing a BSOD every day, mostly 2 times a week).

Wtfunk · Sep 26, 2010

Well, I tried the things Tews suggested like the SPTD uninstaller and the driver updates, but I still get this BSOD... Should I post more information or something, cause I reeeeeally want to get rid off this problem! Please help, thanks.

Anthony · Sep 26, 2010

System Specs would be nice. :huh:

Wtfunk · Sep 26, 2010

Time of this report: 9/26/2010, 15:55:35
Machine name: SANDER-PC
Operating System: Windows 7 Professional 32-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 12/04/07 17:14:27 Ver: 08.00.12
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2 CPUs), ~3.0GHz
Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
Page File: 1401MB used, 2692MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode

Display Devices
---------------
Card name: ATI Radeon HD 5600 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x68D8)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_68D8&SUBSYS_E151174B&REV_00
Display Memory: 1784 MB
Dedicated Memory: 1016 MB
Shared Memory: 767 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor Name: HP w2228h Wide LCD Monitor
Monitor Model: HP w2228h
Monitor Id: HWP2812
Native Mode: 1680 x 1050(p) (59.954Hz)
Output Type: HDMI

Wtfunk · Sep 26, 2010

Uploaded with ImageShack.us

Wtfunk · Sep 27, 2010

Anyone?.....

Tews · Sep 27, 2010

Please upload any NEW .dmp files..

Wtfunk · Sep 28, 2010

It just got a BSOD so this minidump files are superfresh:

Zippyshare.com - MiniDump 28-09-2010.zip

If you need some other information, just tell me!

Thanks

Wtfunk · Sep 29, 2010

Should I update my BIOS maybe?

cluberti · Sep 29, 2010

These BSODs signify a Machine Check Exception error, which means the hardware signified (via a standard messaging interface) to Windows via the processor driver that the system had an unrecoverable hardware error. Windows will bugcheck when it receives this (on purpose) so as to try and minimize data loss and potential hardware problems, and this is the bugcheck you're seeing. In looking at the bulk of the dump files and remembering I posted about this a week ago in this thread, it still looks like a CPU issue:

Code:

1: kd> !errrec 863f2024
...
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 863f2134
Section       @ 863f22bc
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : DCACHEL1_DRD_ERR (Proc 0 Bank 0)
  Status      : 0xf671c00000000135
  Address     : 0x0000000019124be8
  Misc.       : 0x0000000000000000
 
1: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 1 15,67,3 AuthenticAMD 3013 0000000000000000                   a01d7fff

I would always suggest updating your BIOS and resetting it to failsafe defaults, but after doing that, if the problem continues, you're probably out of luck short of returning the hardware for replacement from whomever sold it to you (or AMD directly, depending on warranty from the seller).

Wtfunk · Sep 29, 2010

Well, thanks for the help, I'm going to try the BIOS update and if that doesn't work there is one solution left and that is buying a brand new PC. Again, thank you!

cluberti · Sep 29, 2010

Always hate when that's the answer, but you can't fix a hardware problem from software (well, not easily, even when it can be worked around). If you have bad hardware and it's under warranty, it's always best to just replace it. Not worth taking the risk something else could go wrong later, even if you do manage to repair it.

ickymay · Sep 29, 2010

these drivers are still present in your latest .dmp files ?

giveio.sys 0x895f6000 0x895f6680 0x00000680 0x316334f5 04/04/1996 03:33:25
speedfan.sys 0x895dc000 0x895dd480 0x00001480 0x4516880f 24/09/2006 14:28:47
PxHelp20.sys 0x8902f000 0x890380c0 0x000090c0 0x475dd057 11/12/2007 00:48:39
TPkd.sys 0x89039000 0x89057000 0x0001e000 0x48c58483 08/09/2008 21:01:07

sptd.sys 0x88c2b000 0x88d1e000 0x000f3000 0x4ad245ea 11/10/2009 21:54:02

you need to do as tews suggested and completely remove them .............

Due to time constraints I'm sorry I can't devote more time to an in depth guidance with removal, but I'm confident other forum users may have time to help ?

before you give up on this machine if you can't backtrack on driver removal then I would simply do a fresh install and test your fresh install of windows with no other software installed and see if you still get these bluescreen issues

Blue Screen of Death, BIG problem!!!

New member

My Computer My Computer

At a glance

Professional Lurker

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Professional Lurker

My Computer My Computer

At a glance

Cat herder

My Computer My Computer

At a glance

Professional Lurker

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Professional Lurker

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Cat herder

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Cat herder

My Computer My Computer

At a glance

I like it GOO-ee

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer