Windows 7: Random crashes have returned

ronski · 21 Mar 2012

A few days ago I posted here for problem with random crahes at startup. I removed old ASPI driver and disabled a strange IDE controller in device manager called ATWJYKUR IDE Controller. This seemed to fix my problem and so I decided to have a clean up. I ran disk cleanup etc. and then while running defrag, it did not complete and crashed again. This morning I started up and it's back again.
Not sure where to go from here.

Thanks again for any help

Ron.

Intel I7 3.2ghz
Asrock X58 motherboard
4gig Ram
ATI radeon 5800 video
OEM windows 7 32bit professional

Vir Gnarus · 22 Mar 2012

If you're noticing a strange IDE controller then it may be suspect of a rootkit infection. They will register virtual drive devices or even controllers in order to safely harbor their internal code in a virtual partition that's away from the prying eyes of AV engines. You'll want to check up with the security team here at SF in the appropriate forum to see about the best approach regarding this. Concerning rootkits, manual removal for a novice or even letting AV engines attempt to clean it for you is not recommended.

Anyways, I do notice at least a large number of PCI Express WHEA errors in that there's some failure on your PCI Express controller hub. The solitary crashdump also is a WHEA-produced BSOD caused by your PCI Express hub. If you have any PCI Express cards installed, they may be the cause of it, but most likely the hub itself is faulty, in which case you'll need to replace the motherboard.

I did some googling and found that others with ASRock X58 boards have reported WHEA errors too coming from the same thing. Commonly installing driver updates from the Intel site on the ICH10R and X58 chipsets did the trick.

ronski · 22 Mar 2012

Thanks for the reply,

yes I was very suspect about an IDE controller that cannot be found with google, I will follow up with a visit to appropriate site here.

I have only the video card installed now as I removed all hardware in attempt to isolate the problem and have now installed the latest Intel drivers, in fact, I ran 'slim drivers' to identify any out of date ones, but noted them and went to the official sites to download.

I have done all the memtest things and you are probably right, the motherboard will have to go, Not much good on the net about it and the X68 seems a better option.

will keep you informed,

Thanks again,

Ron.

Vir Gnarus · 22 Mar 2012

I found more information. If I'm looking at it right, the SD bit was set for this specific PCI-E error. SD means Surprise Down, as in it was reported by the controller that the link established between the PCI-E card and the controller hub was lost. Unfortunately this can be rather broad, in that it could mean either the card or the motherboard was responsible for losing the connection. There's also the possibility of dust or something else that's stuck in the PCIE slot, or that the card is not flush and correctly inserted into the slot. Make sure that isn't the case, otherwise, given the complaints from others about this board, I'd lean more to the controller being responsible.

Analysts:

Code:

3: 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: 00000004, PCI Express Error
Arg2: 869348d4, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000
Arg4: 00000000

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  a

STACK_TEXT:  
80e4cb2c 8341afcd 00000124 00000004 869348d4 nt!KeBugCheckEx+0x1e
80e4cb68 83506fc4 869334e1 869348d4 8691bc10 hal!HalBugCheckSystem+0xab
80e4cb9c 8c7ce609 8691b638 8690a780 80e4cd20 nt!WheaReportHwError+0x230
80e4cbb4 8c7cf088 869344b4 00000000 8691b638 pci!ExpressRootPortAerInterruptRoutine+0x1e7
80e4cbd8 8c7cf264 8690a780 86934008 80e4cbfc pci!ExpressRootPortInterruptRoutine+0x1a
80e4cbe8 834a9cff 8690a780 86934008 00000001 pci!ExpressRootPortMessageRoutine+0x10
80e4cbfc 83474ded 8690a780 86934008 80e4cc28 nt!KiInterruptMessageDispatch+0x12
80e4cbfc 93be45d6 8690a780 86934008 80e4cc28 nt!KiInterruptDispatch+0x6d
WARNING: Stack unwind information not available. Following frames may be wrong.
80e4cc98 8349ada4 888d8d48 80e35800 80e30000 intelppm+0x15d6
80e4cd20 834985ad 00000000 0000000e ab16ab16 nt!PoIdle+0x524
80e4cd24 00000000 0000000e ab16ab16 8bdf8bdf nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

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

3: kd> !errrec 869348d4
===============================================================================
Common Platform Error Record @ 869348d4
-------------------------------------------------------------------------------
Record Id     : 01cd07d8bce4740f
Severity      : Fatal (1)
Length        : 672
Creator       : Microsoft
Notify Type   : PCI Express Error
Timestamp     : 3/22/2012 3:06:44 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : PCI Express
-------------------------------------------------------------------------------
Descriptor    @ 86934954
Section       @ 869349e4
Offset        : 272
Length        : 208
Flags         : 0x00000001 Primary
Severity      : Recoverable

Port Type     : Root Port
Version       : 1.1
Command/Status: 0x4010/0x0507
Device Id     :
  VenId:DevId : 8086:340a
  Class code  : 030400
  Function No : 0x00
  Device No   : 0x03
  Segment     : 0x0000
  Primary Bus : 0x00
  Second. Bus : 0x00
  Slot        : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ 86934a18
  Device Caps : 00008021 Role-Based Error Reporting: 1
  Device Ctl  : 0107 ur FE NF CE
  Dev Status  : 0003 ur fe NF CE
   Root Ctl   : 0008 fs nfs cs

AER Information @ ffffffff86934a54
  Uncorrectable Error Status    : 00000020 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  : 00062010 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        : 00000000 adv rtto rnro dllp tlp re
  Caps & Control                : 00000005 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

===============================================================================
Section 1     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 8693499c
Section       @ 86934ab4
Offset        : 480
Length        : 192
Flags         : 0x00000000
Severity      : Informational

Proc. Type    : x86/x64
Instr. Set    : x86
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000006

Looked up VenID:DevID on PCIDatabase.com. Turned up with the client's Intel 7500 Chipset PCIe Root Port which is part of the ICH10 Intel Southbridge chipset.

I then went to MSDN and looked up any structure information related to PCI Express and AER (Advanced Error Reporting). The results came up with 3 possible structures. Because this was a report sent by the Root Port (you can tell in the WHEA error by the Port Type), the structure we want is PCI_EXPRESS_ROOTPORT_AER_CAPABILITY. Then I looked at the structure details related to Uncorrectable Error Status as it should tell us the current status of the error that was triggered. In the WHEA record, it shows us that SD is capitalized, meaning the bit related to that is set, so we should look for details on what "SD" most likely means. Result in the article is "Surprise Down". Googling this showed that it means a report that there was a sudden connection loss between the card and the controller.

ronski · 22 Mar 2012

Thanks again for your continued help, I will now strip and do a thorough clean. After months of this I am ready to at least change the motherboard, maybe clean install of everything. Can you recommend a quality board?

You guys are amazing,

Ron.

Vir Gnarus · 23 Mar 2012

I personally can't find any problems with ASRock in general. For the price, they are very good quality boards. Of course, with any manufacturer there's always going to be the inevitable defect that slips through QA/QC. Though if there's a number of reports of problems with that particular model, bumping it up to the x68 may improve on it (there may be issues in general with the x58 Intel chipset).

ronski · 23 Mar 2012

I now have fully stripped and rebuilt the motherboard, cleaned and dusted everything. There was quite a lot of dust and I considered opening the video card up to clean but couldn't get the cover off.

Anyway, all back together and running fine, no crashes since for around 24 hours now. Forcing many different types of restarts. Let's hope that it was just that. Interestingly, I found that the power on/off switch wire and the reset button were both connected to plugs on the compro TV card and not the motherboard. and even more surprising was a sticker on the TV card that reads, 'turn power to pc off for 30 seconds should computer suffer from constant restarts'. Very suspicious. We will see how it performs without this pci card for a while.

Thanks again for all your help, I will give it a couple of days, if all good, then I will mark this as solved.

best regards.

Ron.

Vir Gnarus · 26 Apr 2012

UPDATE: Private correspondence with this individual has confirmed the cause was indeed the TV Tuner card, a VideoMate Vista T750F PCI card. Note that this is not a PCI-E card but a PCI card, but the same controller reports for both PCI-E and PCI bus.

Windows 7: Random crashes have returned

Random crashes have returned problems?