BSOD Win7 Minidump problems

cb5 · Aug 13, 2014

Hi,

Over the last year my windows 7 pc has been giving me all sorts of BSOD errors.
Often different error codes / messages.

As they have only happened maybe once or twice a week (I use my pc alot),
its something I've just learnt to live with.

Today after a windows update (15 items), my pc was crashing with BSOD errors every few minutes.
00000000124 or 1A or 0000000000A errors (i'm guessing on the number of 0's).

It wouldn't stay working long enough to search online for a minidump reader.
My pc stayed open just long enough for me to copy the minidump file to a usb stick.

A search on google on a seperate laptop lead me here.
I'm hoping someone can explain in simple terms what it means.
i.e. very likely the ram etc..

here is the link to the minidump:
https://dl.dropboxusercontent.com/u/71962278/081314-56893-01.zip

any help much appreciated

thanks

PS

managed to get my pc to run chkdsk to scan for errors (on a reboot), its been running for the last hour.
as its a 1tb drive it will take a while.
at least its encouraging it hasn't shutdown / crashed yet.

cb5 · Aug 13, 2014

i ran cpu-z to get more info.
could my pc be overclocked?

https://dl.dropboxusercontent.com/u/71962278/cpu-z spec results.zip

Patrick · Aug 13, 2014

Hi,

could my pc be overclocked?

According to the CPU-z info, it's not overclocked, no. Checking through WinDbg at the time of the crash shows the following:

Code:

[CPU Information]
~MHz = REG_DWORD 3604
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 58 Stepping 9
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Update Signature = REG_BINARY 0,0,0,0,12,0,0,0
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 1200000000

Your processor was running at 3604 MHz (3.6 GHz) at the time of the crash, which I believe is just Turbo Boost.

WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

Code:

BugCheck 124, {0, fffffa800fcdf028, be000000, 800400}

Code:

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

Error         : Internal timer (Proc 7 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x0000380003306418
  Misc.       : 0x000000000003ffff

An internal CPU timer failed, specifically on processor #7 and cache bank #3.

This is very likely a hardware issue, but please try the following first:

1. Uninstall AnyDVD ASAP, troublesome dated drivers.

2. Please remove and replace ESET with MSE for temporary troubleshooting purposes:

ESET removal - How do I uninstall or reinstall ESET Smart Security/ESET NOD32 Antivirus? - ESET Knowledgebase

MSE - Microsoft Security Essentials - Microsoft Windows

3.

Code:

7: kd> lmvm ssport
start             end                 module name
fffff880`03e31000 fffff880`03e39000   SSPORT     (deferred)             
    Image path: \??\C:\windows\system32\Drivers\SSPORT.sys
    Image name: SSPORT.sys
    Timestamp:        Thu Aug 11 19:07:32 2005

Your Samsung printer drivers are really old. Please either update them from Samsung's website, or if there's none available, please uninstall the software + disconnect the printer as it's no longer compatible.

4.

Code:

7: kd> lmvm LVUSBS64
start             end                 module name
fffff880`05291000 fffff880`0529d980   LVUSBS64   (deferred)             
    Image path: \SystemRoot\system32\drivers\LVUSBS64.sys
    Image name: LVUSBS64.sys
    Timestamp:        Sat Feb 03 13:05:16 2007

Your Logitech camera drivers are dated as well, update ASAP via Logitech's website.

If all of the above fails, there is only so much you can do with a bug check like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS) [Easy, 10 to 15 Min]

3. Ensure your BIOS is up to date.

4. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick

Jared · Aug 13, 2014

Can you follow these instructions as I need more files (more dumps).

https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html

Code:

7: kd> !errrec fffffa800fcdf028
===============================================================================
Common Platform Error Record @ fffffa800fcdf028
-------------------------------------------------------------------------------
Record Id     : 01cfb6c6173b0f0a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/13/2014 7:16:55 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000007

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

Local APIC Id : 0x0000000000000007
CPU Id        : a9 06 03 00 00 08 10 07 - bf e3 9a 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  @ fffffa800fcdf240

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

Error         : Internal timer (Proc 7 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x0000380003306418
  Misc.       : 0x000000000003ffff

The error is an internal timer which isn't very descriptive, this can be caused by lots of different things, to determine whether it's likely the CPU failing we would need more 0x124 dump files.
However, given there are 0x1A and 0xA bugchecks as well I'm leaning slightly towards bad RAM.

EDIT: Patrick beat me to it...
I suggest following Patrick's instructions first.

cb5 · Aug 13, 2014

ok many thanks

Patrick · Aug 13, 2014

Not a problem, keep us updated.

Regards,

Patrick

cb5 · Aug 16, 2014

* update *

Thanks Patrick / Jared for the advice.

(1) I had already begun doing the chkdsk & scannow stuff to check my os hard drive - didn't find any probelms.
(2) I also tried the various recovery / repair / last known good boot etc - but no luck, just kept rebooting.
(3) While waiting for a response to my 2nd post I decided to look at the bios - thinking my cpu was overclocked - I decided to try and reset it back to the factory default 'optimized BIOS defaults'.
(4) Then Patrick / Jared replied, unfortunately I couldn't get into windows to uninstall AnyDVD / ESET / SAMSUNG Print / Logitech camera drivers.
(5) Removed my hard drive(s) from the faulty pc and moved my files to an external usb hd.
(6) Eventually, after 2 hours managed to wipe the disk using DISKPART, only then would it let me install from dvd.
(7) Another 2 hours later and I managed to hunt down the various drivers, question marks (?) were appearing against various hardware in the device manager (usb etc).
(8) 155 updates / 858MB of windows update later - my pc had minimal software installed.
(9) Started to use my PC early this morning, it's now been running for about 14 hours without any BSOD's so far.

So far so good, I haven't tried to push my cpu as yet, in the next few days I'll try converting a few DVDS to MKV files.

Anyway, thanks for all your help :)

x BlueRobot · Aug 20, 2014

Thanks for the update, if any other problems then please let us know.

Search

Search

BSOD Win7 Minidump problems

cb5

New member

cb5

New member

Patrick

Sysnative Staff

Jared

Sysnative Staff, BSOD Kernel Dump Expert

cb5

New member

Patrick

Sysnative Staff

cb5

New member

x BlueRobot

Administrator