Windows 7 Multiple Errors

Aedaric

Aedaric

New Member
Joined
Aug 1, 2013
Below are some of the errors I've received.

Code: 
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    a
  BCP1:    000000000000002B
  BCP2:    0000000000000002
  BCP3:    0000000000000000
  BCP4:    FFFFF80002CCE723
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\080113-23587-01.dmp
  C:\Users\Aedaric\AppData\Local\Temp\WER-60013-0.sysdata.xml

-----------------------------

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    3b
  BCP1:    00000000C0000005
  BCP2:    000000000000001B
  BCP3:    FFFFF88018CB6EF0
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\080113-24944-01.dmp
  C:\Users\Aedaric\AppData\Local\Temp\WER-246122-0.sysdata.xml
 

Attachments

  • Minidump.zip
    126.6 KB · Views: 229
I haven't been able to determine when/where it causes crashes but it's getting quite frustrating. I've also received an 0x00000124 error code in the past. This error I received multiple times. The 0x0000002B and 3B were the last most recent.
 
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: 0000000000000000, Machine Check Exception
Arg2: fffffa800fe03028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`03108b58 fffff800`02c1da3b : 00000000`00000124 00000000`00000000 fffffa80`0fe03028 00000000`be000000 : nt!KeBugCheckEx
fffff880`03108b60 fffff800`02de0443 : 00000000`00000001 fffffa80`0fe06a60 00000000`00000000 fffffa80`0fe06ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`03108ba0 fffff800`02c1d700 : 00000000`00000728 fffffa80`0fe06a60 fffff880`03108f30 fffff880`03108f00 : nt!WheaReportHwError+0x263
fffff880`03108c00 fffff800`02c1d052 : fffffa80`0fe06a60 fffff880`03108f30 fffffa80`0fe06a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03108d50 fffff800`02c1cf0d : 00000000`00000008 00000000`00000001 fffff880`03108fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03108d90 fffff800`02c10e88 : 00000000`00000000 fffff880`03100180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03108dc0 fffff800`02cc84ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03108df0 fffff800`02cc8353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03108f30 fffff880`05deb9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03128b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

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


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).

My suggestion is to run a memory test (http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer), check that your cpu/gpu processor fan are operating normally, perhaps even reseat your processor and make sure the heatsink is making good contact. I've never ran into this particular error myself however.
 
I ran the test with Windows 7's tool two days ago and I do not believe it found any errors as it immediately reboot.

I haven't received the 124 error in two days. But the 03b and 02b I received today alone.

I guess the dump didn't properly go?
 
Can an admin please move this to the BSOD section? I read "Windows 7 Support" and immediately posted here, failed to read further.

Thank you!
 
Thank you!

So I ran MemTest86+ for three passes and had zero issues with my system. I also ran Prime95 for three hours with zero errors and/or crashes.

I attached the latest minidump file from my crash today. I don't know what caused this one, as I wasn't doing anything in particular at the time.

Any ideas? Also---CPU temp never went above 81 C during the test using the stock Intel fan and heatsink.
 

Attachments

  • 080413-24726-01.zip
    37.3 KB · Views: 248
Some free anti-virus software is known to cause BSOD. What are you using for that? You should look at what programs are starting when you first boot up.

Let's find out what's running when we start Windows 7:
Go to Start -> Search -> msconfig -> "Startup" tab.

Look for anything thats not from Microsoft Corporation that may be unusual or unused. Do not try to disable your anti-virus software this way.

Also, we get closer with some hint. This could be a legacy driver at fault. No way to be sure.

Let's thoroughly check the event log for errors:
Check Event Viewer. Go to Start -> Search -> ev

Scan through Application and System for errors around the time of the crash. I would consider auditing the programs you have on the computer and considering anything that might install third party drivers. This can include security bundles, DVD/CD burning suite, and especially old software.

What can bring down the whole system? Ultimately, if its not a hardware or configuration issue, the device drivers interact with the hardware abstraction layer to tell Windows how to handle the hardware on your system. Some drivers are virtualized components that are used for virtual devices needed to run some software. Digital Rights Management is known to do this, with programs like iTunes, yet enough people use that in Windows that it would not normally crash your system.

The reason anti-virus is suspect is because it operates at the highest layers of your system to prevent unauthorized activities. A malfunction in this software can bring down the entire system in a kernel level event. I would audit the software, determine whats not used, but running, and remove it. I would also look for outdated drivers and seek some updates.

Recommendations:

  • Uninstall your anti-virus
  • Identify programs running using msconfig (System Configuration) and taskmgr (Task Manager).
  • Uninstall unnecessary software by performing an audit of unused software.
  • Thoroughly clean using CCleaner. If having difficulty fully uninstalling software, use Revo Uninstaller.
  • Be sure to check c:\program files (x86)\ and c:\program files\ for software thats not listed in Control Panel.
  • Use Event Viewer (ev) to look for errors right before the crash.
  • Consider updating all of the essential drivers on your system (NIC, Graphics, Audio, Chipset)
  • Try using Reliability Monitor to find patterns with the crashes. Start -> Search -> cmd -> perfmon /rel
Be mindful that 9 times out of 10 its your anti-virus or some program that heavily interacts with the operating system, even while you are doing something else. It is usually a third-party program that is running "most of the time", where you seldom think, what if this thing has a memory leak or a problem while its running in resident memory with direct access to my hardware abstraction layer and kernel-level security? Well, usually that's the anti-virus.

This is a process of elimination method that can help. If you see any I/O or write back cache errors in Event Viewer its the hard drive. Speaking of which, if your computer is going to crash all the time:

Go to Start -> Computer -> Right-click on C: -> Properties -> Hardware - Double Click on Hard Drive -> Change Settings (requires elevation) ->

Removal Policy:
  • Set to quick removal, if possible
  • Uncheck "Enable writing cache on the device"

Every time the system crashes you may be subject to data loss. This will reduce your main drive performance, somewhat, but reduce the risk of data loss during this time of instability.
 
Thanks for the quick reply. Unfortunately I typically don't run an AV. I've had maybe two viruses(that I knew about) in the 15 years I've built my own systems.

The computer was crashing after a clean install when I upgraded the motherboard and processor from my previous computer. Memory, power supply, video card are all know working without issues from my previous computer (2+ years on that one). As for third party software--I don't typically use it unless I need to. There are no higher level requirements for any of it.


The following is everything that happened during the 08/0930 crash:

Also, I do not know which drivers it's failing to load because there is nothing showing under Device Manager as "Unknown or Missing".


Code: 
Log Name:      System
Source:        EventLog
Date:          8/4/2013 9:30:18 AM
Event ID:      6008
Task Category: None
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      Aedaric-PC
Description:
The previous system shutdown at 9:28:23 AM on ‎8/‎4/‎2013 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:18.000000000Z" />
    <EventRecordID>12589</EventRecordID>
    <Channel>System</Channel>
    <Computer>Aedaric-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>9:28:23 AM</Data>
    <Data>‎8/‎4/‎2013</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>67167</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DD0708000000040009001C0017007301DD070800000004000E001C0017007301600900003C000000010000006009000000000000B00400000100000000000000</Binary>
  </EventData>
</Event>

Code: 
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          8/4/2013 9:30:19 AM
Event ID:      1001
Task Category: None
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      AEDARIC-PC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800f6f9028, 0x00000000be000000, 0x000000000100110a). A dump was saved in: C:\Windows\Minidump\080413-24726-01.dmp. Report Id: 080413-24726-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:19.000000000Z" />
    <EventRecordID>12593</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>AEDARIC-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000124 (0x0000000000000000, 0xfffffa800f6f9028, 0x00000000be000000, 0x000000000100110a)</Data>
    <Data Name="param2">C:\Windows\Minidump\080413-24726-01.dmp</Data>
    <Data Name="param3">080413-24726-01</Data>
  </EventData>
</Event>

Code: 
Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          8/4/2013 9:30:06 AM
Event ID:      41
Task Category: (63)
Level:        Critical
Keywords:      (2)
User:          SYSTEM
Computer:      Aedaric-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:06.059620300Z" />
    <EventRecordID>12594</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Aedaric-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">292</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0xfffffa800f6f9028</Data>
    <Data Name="BugcheckParameter3">0xbe000000</Data>
    <Data Name="BugcheckParameter4">0x100110a</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>


Code: 
Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Date:          8/4/2013 9:30:08 AM
Event ID:      219
Task Category: (212)
Level:        Warning
Keywords:    
User:          SYSTEM
Computer:      Aedaric-PC
Description:
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>219</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>212</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:08.524424600Z" />
    <EventRecordID>12596</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="104" />
    <Channel>System</Channel>
    <Computer>Aedaric-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DriverNameLength">24</Data>
    <Data Name="DriverName">ACPI\PNP0A0A\2&amp;daba3ff&amp;1</Data>
    <Data Name="Status">3221226341</Data>
    <Data Name="FailureNameLength">14</Data>
    <Data Name="FailureName">\Driver\WUDFRd</Data>
    <Data Name="Version">0</Data>
  </EventData>
</Event>


Code: 
Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Date:          8/4/2013 9:30:13 AM
Event ID:      219
Task Category: (212)
Level:        Warning
Keywords:    
User:          SYSTEM
Computer:      Aedaric-PC
Description:
The driver \Driver\WUDFRd failed to load for the device USB\VID_03F0&PID_0036&MI_01\7&14e6ff09&0&0001.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>219</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>212</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:13.454033300Z" />
    <EventRecordID>12611</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="80" />
    <Channel>System</Channel>
    <Computer>Aedaric-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DriverNameLength">45</Data>
    <Data Name="DriverName">USB\VID_03F0&amp;PID_0036&amp;MI_01\7&amp;14e6ff09&amp;0&amp;0001</Data>
    <Data Name="Status">3221226341</Data>
    <Data Name="FailureNameLength">14</Data>
    <Data Name="FailureName">\Driver\WUDFRd</Data>
    <Data Name="Version">0</Data>
  </EventData>
</Event>

Code: 
Log Name:      Security
Source:        Microsoft-Windows-Eventlog
Date:          8/4/2013 9:30:19 AM
Event ID:      1101
Task Category: Event processing
Level:        Error
Keywords:      Audit Success
User:          N/A
Computer:      Aedaric-PC
Description:
Audit events have been dropped by the transport.  0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Eventlog" Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
    <EventID>1101</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>101</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4020000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-04T14:30:19.974844700Z" />
    <EventRecordID>6964</EventRecordID>
    <Correlation />
    <Execution ProcessID="296" ThreadID="1240" />
    <Channel>Security</Channel>
    <Computer>Aedaric-PC</Computer>
    <Security />
  </System>
  <UserData>
    <AuditEventsDropped xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
      <Reason>0</Reason>
    </AuditEventsDropped>
  </UserData>
</Event>
 
Aedaric said:
The computer was crashing after a clean install when I upgraded the motherboard and processor from my previous computer.
Code: 
The driver \Driver\WUDFRd failed to load for the device USB\VID_03F0&PID_0036&MI_01\7&14e6ff09&0&0001.



The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1.
Click to expand...


These two are significant. This refers to Windows User Driver Framework under the Windows Driver Foundation. USB and ACPI would be related to the chipset/motherboard. What kind of motherboard is this? From the crash dump I see this is a genuine Intel processor. You should be using the latest Intel INF Update.
 
An ASUS Z87-PRO with an i4770k processor. I did have the latest INF drivers from Intel, as well as the latest drivers for my GTX 690.
 
Interesting thread...
You didn't mention whether or not you used an existing *used* hard drive or a new one when you upgraded your Motherboard and CPU. According to what you wrote in Post #8: "Any ideas? Also---CPU temp never went above 81 C during the test using the stock Intel fan and heatsink." If your system is running above 72 C (160 F) at ANY time, under load or not it is running TOO HOT!! There is a good chance you overtemped your internal electronics; specifically your Motherboard/CPU and your hard drive. If this is the case, and no one else in the thread mentioned the hard drive, you could be fighting a faulty (cooked!) hard drive. :(

The Motherboard/CPU could also be the culprit, but as hard drives are about 1/3 the cost to replace of a new Motherboard, I'd definitely start there. Prior to replacing your hard drive, make sure you backup all your critical data to another external hard drive, flash drive, or cd/dvd. Since you've been building systems for 15 yrs., I'm guessing you already know this. I always suggest it anyway as a general precaution. Also, ASUS Motherboards are top-notch and they are more resistent to overtemping than many of their cheaper competitors.

If you have a used hard drive and not new (you'll let us know which?), you'll want to run diagnostics either way here, it's more likely it's been overtemped in your previous system or setup just due to age. If it's older than 3 yrs. old, it's a candidate for failure/replacement. I suggest you use UBCD linux tool set by Benjamin Burrows at http://www.ultimatebootcd.com/download.html. This toolset can tell you a lot about your Motherboard/CPU and your hard drive. Specifically, the overtemp situation. If you use PartEd Magic, and use Disk Health (GSmart Control), go into the Attributes and Error Log tabs, they will give you temperature specs. These will tell you the highest temp your hard drive has endured since you owned it, and that's also the approx. temp your Motherboard/CPU endured as well. If over 72 C at any time; it's been overtemped. Even if it's a brand new drive, if you have inadequate ventilation and air flow in your case, perhaps you need a new case, or improved fan velocity to bring that temp back down. :thumbs_up:

Hope my suggestions lead you in the right direction.

BIGBEARJEDI
 
Thanks for the responses all! I'll do what you mentioned regarding checking other temperatures. As for overtemping the CPU, the only research I've found regarding Haswell processors is anything over 100 C is dangerous and usually very unlikely. I'm not saying that's right, but I haven't found anything to mention otherwise. My case has seven fans, four are 120mm fans and three 80mm fans. Other components in the case according to HWMonitor never rose above 30C. I'm off to work now however I'll post tonight what the UBCD/PartEd Magic discover.

Also, I thought I put it in my CPU Specs, however the hard drives are also from my older computer and I run two 2.5" drives in RAID0.
 
You must log in or register to reply here.

Similar threads

Asko
Windows 7 BlueScreen BCCODE: 1a
Replies
1
Views
4K
kemical
kemical
Dudamesh
Windows 7 Occasional Bluescreen but always forced restart
Replies
2
Views
5K
Dudamesh
Dudamesh
J
Server 2008 R2 Insufficient System Resources to Complete Requested Service
Replies
4
Views
2K
jctst714
J
TheApoc
Windows 7 BSOD with toshiba Laptop
Replies
3
Views
8K
kemical
kemical
M
Windows 10 New System build with multiple BSODs
Replies
3
Views
2K
kemical
kemical
Back
Top Bottom