Solved Random BSOD while working on PC

[Hella737]

Hi,
My system was built in September on a ASUS X99-WS/IPMI motherboard and Geforce GTX 980 Ti.
System is primarily used for high end video and graphic projects.
In the beginning there were frequent instances of freezing up just as the Windows 7 flash screen came up. After a few restarts the system would come up and seem to work. System was at the shop and came back after replacing a memory module.
A week or so later the BSODs started happen in random and it has continued without giving any clue other than:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000007
BCP2: FFFFFA801A082AE8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102315-15475-01.dmp
C:\Users\Hella\AppData\Local\Temp\WER-134582-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
_________________________________________________________________________
The only thing part from memory and GPU installed is a PCIe Hauppage Collussus 2 Video Capture card.
There are a number of hard drives installed and also I use a 10 TB NAS server for storage of projects.

Attached is a zip file with the information gathered from the system.

Any assistance would be greatley appreciated.
Thank you in advance,
Helge Larsen

 

[Boozad]

Hello Hella,

An interesting 0x124. Usually these generic STOP codes give us no indication of what the problematic piece of hardware is, however in your case we're in luck. If we run !errrec on the address of the WHEA_ERROR_RECORD structure we can see that it verifies your issue being prevalent at boot.

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: 0000000000000007, BOOT Error
Arg2: f[COLOR=Blue]ffffa8019ed46a8[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

11: kd> !errrec [COLOR=Blue]fffffa8019ed46a8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8019ed46a8
-------------------------------------------------------------------------------
Record Id     : 01d10075b87daa45
Severity      : Fatal (1)
Length        : 1304
Creator       : Microsoft
Notify Type   : [COLOR=Blue]BOOT Error Record[/COLOR]
Timestamp     : 10/6/2015 20:29:41 (UTC)
Flags         : 0x00000002 PreviousError

Looking further down the readout we see a PCI Express root port is being blamed. This is where we're in luck as it gives us a VenID and a DevID for the problematic device.

===============================================================================
Section 0     : [COLOR=Red]PCI Express[/COLOR]
-------------------------------------------------------------------------------
Descriptor    @ fffffa8019ed4728
Section       @ fffffa8019ed4770
Offset        : 200
Length        : 208
Flags         : 0x00000001 Primary
Severity      : Fatal

Port Type     : Root Port
Version       : 1.16
Command/Status: 0x0010/0x0000
Device Id     :
 [COLOR=Blue] VenId:DevId[/COLOR] : [COLOR=Red]8086:2f08[/COLOR]
  Class code  : 000604
  Function No : 0x00
  Device No   : 0x03
  Segment     : 0x0000
  Primary Bus : 0x00
  Second. Bus : 0x00
  Slot        : 0x0000
Sec. Status   : 0x0000
Bridge Ctl.   : 0x0000
Express Capability Information @ fffffa8019ed47a4
  Device Caps : 00000000 Role-Based Error Reporting: 0
  Device Ctl  : 0000 ur fe nf ce
  Dev Status  : 0000 ur fe nf ce
   Root Ctl   : 0000 fs nfs cs

AER Information @ fffffa8019ed47e0
  Uncorrectable Error Status    : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
  Uncorrectable Error Mask      : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
  Uncorrectable Error Severity  : 00062030 ur ecrc MTLP ROF uc ca cto FCP ptlp SD DLP und
  Correctable Error Status      : 00000000 adv rtto rnro dllp tlp re
  Correctable Error Mask        : 00002000 ADV rtto rnro dllp tlp re
  Caps & Control                : 00000000 ecrcchken ecrcchkcap ecrcgenen ecrcgencap fep
  Header Log                    : 00000000 00000000 00000000 00000000
  Root Error Command            : 00000000 fen nfen cen
  Root Error Status             : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
  Correctable Error Source ID   : 00,00,00
  Correctable Error Source ID   : 00,00,00

Chasing through your hardware we can see that it's your Intel Xeon E5 v3/Core i7 PCI Express Root Port 3:

Memory Address 0xFA500000-0xFA507FFF    
ASMedia XHCI 1.0 Controller    
Memory Address 0xFA500000-0xFA507FFF    
Intel(R) Xeon(R) E5 v3/Core i7 PCI Express Root Port 3 - [COLOR=Red]2F08[/COLOR]

As this shares a memory address with your ASMedia XHCI Controller I've looked at the driver date and it does appear to be old. Check your motherboard vendor for an updated version to see if this cures the issue, it may not as this is just a hunch but it's worth a try for the first round of troubleshooting.

asmtxhci     ASMEDIA XHCI Service   [COLOR=Red]25.07.2014[/COLOR] 04:15:34

This is also a strange one, seemingly blaming Sysinternals NotMyFault. Isn't that a book?

BugCheck D1, {fffff8a011379010, 2, 0, fffff8800ea0c385}

[COLOR=Red]*** WARNING: Unable to verify timestamp for myfault.sys
*** ERROR: Module load completed but symbols could not be loaded for myfault.sys[/COLOR]
Probably caused by : myfault.sys ( myfault+1385 )

 

[axe0]

Boozad, the 0x124 usually doesn't reveal enough when it is an Authentic error

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: [COLOR="Red"]Genuine[/COLOR]Intel

IMAGE_NAME:  [COLOR="red"]Genuine[/COLOR]Intel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

As you have noticed, it is a big difference

Few months later found out this is incorrect

 

[Pauly]

sysinternals have a tool to generate a blue screen and to my knowledge the output of that would indicate myfault.sys

Not sure about this either
View attachment 374337

 

[Hella737]

Thank you so much for your express response to my problem.
I did find an updated driver ASMEDIA XHCI Service dated new date is 02.12.2015 v. 116240.
In the middle of installing the driver I had new BSOD, but it did not generate a DUMP file.
So, I made a new dump file with "Not My Fault" trigger. I have attached this file in the new zip file, 102415-13182-01.dmp.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044

Additional information about the problem:
BCCode: d1
BCP1: FFFFF8A012079800
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800F40B385
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102415-13182-01.dmp
C:\Users\Hella\AppData\Local\Temp\WER-25272-0.sysdata.xml

After rebooting I reinstalled the new driver and so far it all looks good....
Funny thing is that the boot "freezes" for 2-3 seconds during the W7 flash screen and keyboard wired to USB 3 goes dead until the OS is loaded.
This is not new, but I was hoping a newer driver would fix that issue.
From your posting it seems logical to me that the new driver may fix my BSOD issue. But, I will wait a few days before I close the post, just in case.

Again, thank you for great support!!

 

[Boozad]

The NotMyFault crashes are not really of an use (thanks to Pauly for pointing that out) so no need run that again. I'd also take Pauly's advice and uninstall TweakBit, it's not going to be doing any good.

Test the system by using as normal and upload new logs if you experience any more BSODs. Hopefully that driver has sorted things out, if not we'll look at what you have installed in your PCI-e slots.

 

[Hella737]

I had another BSOD this morning. The PC was idle from my side, but running a cloud backup Acronis.
I also had reverted back to BIOS version 701 because that was one of the things I had upgraded to 803 at the time the BSODs started.
I have a Hauppauge Colossus 2 videocapture card in slot 1 and Gigabyte Geforce GTX 980 Ti in slot 3.
No other changes have been made since the last BSOD I sent in.
Attached is a new zip file from this morning.
If there is any other information needed, please let me know.
Thank you.

 

[Hella737]

I forgot to copy in the on-screen information, but here it is:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA801A13B028
BCP3: 00000000BA000000
BCP4: 0000000081000402
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102715-12402-01.dmp
C:\Users\Hella\AppData\Local\Temp\WER-28735-0.sysdata.xml

 

[Hella737]

Some additional information.
I installed Core Temp to see real-time temperatures because it was suggested on some other board.
Then I started p95 to load up to 100 %.
CPU Temps went high and it triggered another BSOD at about 95 DegC.
In BIOS I set max allowable temp to 100 and in the Corsair PSU Monitor I set it to high fan speed at 75 C.
Now idle temp is around 55-60 and at 100 & load CPU is at 65-75 DegC.
Can this have been the BSOD issue I have had all the time?


Again, thank you.

I hope this was it....

 

[Boozad]

Both 0x124s again, this time they're not pointing towards anything though. Given that the first batch of dumps were pointing towards a PCI-e issue I'd recommend removing the Hauppauge Colossus card and testing the system under normal usage.

 

[Hella737]

The system has now run for 3 days without any BSODs and I suggest that the issue was related to one of two things:
1. The out-dated driver ASMedia XHCI; or:
2. The fact that the CPU went into BSOD due to high temperatures.
I have now an updated driver installed and I have changed out the CPU licuid cooler to a Cooler Master Nepton 240M.
Idel temp now is 28-33 DegC and at 100 % load with p95 software it never went above 70 DegC.
If the BSOD occurs again I will then test without the Hauppauge in the PCI slot.

I am taken the chance to makr this issue as solved today.
I thank you very much for the assitance in solving the BSOD.