G73Jh - WHEA-Logger eventid 17

Hi Guys,

I've had my laptop since august last year, and its been doing great until just recently. For some reason my laptop started to crash (bsod) error 4b.
I was searching for some solution in this forum, and I came across upgrading my bios to 211 and vbios which i did. I then tried all the different release of drivers thats available. The crash continued until I install 10.10e drivers downloaded from guru 3d. Ever since that the laptop never crash even when I played all day long.

Skip forward 2 weeks since it last crash, yesterday I noticed that my laptop is throwing WHEA-Logger eventid 17 with such speed that it would fillup the log within seconds after it is cleared.

I've searched the internet for similar issue and found a temporary solutions to disable Diagnostic Policy Service to stop the error.

Does anyone here have any idea what might have caused the problems ?

I've contacted asus support and forwarded them the error details, but have not received anything back from them.

Any info or suggestion is greatly appreciated.

Thx

 

I had this problem. I had to RMA to get it fixed, as far as I can tell (frequenting the Intel forums) it's a motherboard/chipset problem caused by either an incompatability with the AMD GPUs or overheating chipset something or other.

It maxes out your disk activity read/write as well, IIRC and makes watching TV a stuttering mess if you're doing ANYTHING else at the same time.

OTOH, I did manage to get rid of it once (couldn't reproduce it) by installing JUST the driver package for the 5870m - not CCC or anything - I uninstalled all graphics drivers (and deleted them), restarted with the MS driver and forced (using device manager) a driver update.

Anyways, I don't remember exactly what caused it, but it would only happen to me when the graphics driver was installed, and the error was generated by some virtual device (couldn't find an appropriate dev_ID online anywhere).

My RMA story was TERRIBLE - a series of screwups - When I RMA'd it, they swapped my GPU for a different one - which fixed the problem - but there was no "fixed" vbios at the time, so I ended up with a bad GPU. Then I RMA'd it again, got a new mobo but the same GPU. RMA'd that, got a new GPU AND a new Mobo, but it appears the techs updated the bios in windows and it failed, because the laptop came back with the battery installed, and "resumed", but refused to start up after a windows update.

... Anyways, I finally have a working g73 again. That whole RMA process took a good 3 months, and this was after only 2 months of ownership - and when I got it back for the final time, I had to manually update my vbios because the techs flashed one of the non-working betas instead of the fixed one... *sigh*

 

ouch... thank you for sharing your experience with the error.
I too only experienced this problem when ATI driver is installed.
I tried a few different version of drivers from 10.1, 10.7, 10.11, 10.12, 10.10e, all gives the same error.
I even tried installing just the driver and nothing else ( i prolly read ur post in intel forum).
Currently I have dps service disable which stop the error from showing, but then again who knows what else would stop showing in event viewer because I disabled that service.

Man, I feel so discouraged from reading your post about the RMA process that you have to go through. I wonder if I should just leave it as is until it escalated to a real issue.

My system is stable the way it is now, its just the error filling the system error log, but disabling dps solved that problem..

I dunno, need more opinion

 

You could wait, but it might mean you have other problems that aren't being registered - so if you don't RMA it before the end of your warranty, then you'll be stuck with a laptop that throws up errors.

Just make sure it gets RMA'd before your warranty is over, that's all I'm saying. I wouldn't advise waiting until the end of your warranty period - because it'll bug you because YOU know it's there.

Try a fresh install. I know that daemon tools can cause that sort of error too.

Also, MY Rma occurred when there were a tonne of other RMAs happening - there was a vBios problem that hadn't been solved, and the techs wouldn't actually "fix" it, they'd just install drivers that were a year old (That didn't cause problems) and send it back.

 

Can you post the entire details text from one of these errors?

WHEA errors come from hardware but need to know the source(s).

 

Heres the error quoted directly from the event viewer:

A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus evice:Function: 0x0:0x3:0x0
Vendor ID evice ID: 0x8086:0xd138
Class Code: 0x30400

The details view of this entry contains further information.

---------------------------------------------------------\
Details
-------

- System

- Provider

[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}

EventID 17

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2011-01-13T03:42:30.277909300Z

EventRecordID 28033111

- Correlation

[ ActivityID] {DC986814-99BF-42E0-8170-64376344835D}

- Execution

[ ProcessID] 1600
[ ThreadID] 5984

Channel System

Computer ASUS-LAPTOP.dpmotorsnw.com

- Security

[ UserID] S-1-5-19


- EventData

ErrorSource 4
FRUId {00000000-0000-0000-0000-000000000000}
FRUText
ValidBits 0xdf
PortType 4
Version 0x101
Command 0x10
Status 0x407
Bus 0x0
Device 0x3
Function 0x0
Segment 0x0
SecondaryBus 0x0
Slot 0x0
VendorID 0x8086
DeviceID 0xd138
ClassCode 0x30400
DeviceSerialNumber 0x0
BridgeControl 0x0
BridgeStatus 0x0
UncorrectableErrorStatus 0x0
CorrectableErrorStatus 0x1
HeaderLog 00000000000000000000000000000000
Length 672

DCx,

Btw, how did u found out what was replaced during the RMA process ?
Does ASUS communicated with you what were they replacing before they shipped the laptop back to you ?

Thx

 

Cool thanks. Is there a friendlier version with the same info but text instead of IDs/codes (maybe details isn't what I should have asked for)??

Vendor ID 8086 is Intel, so CPU or Chipset (and anything attached to those: memory, PCI bus, USB controller, etc.), I would guess.

I would try (re)installing the latest Intel INF Update (for Mobile 5-series chipsets - see Chastity's link in the "Core Drivers" section of her Driver/App reference here) to make sure it's not just driver-related.

...and, remove the "Raw Data" line from that event text post so this page is readable please!

 

@MarkS: I frequently get 2 kinds of error at my Event Viewer->Windows Logs->System which are the following:

Error 1/13/2011 5:44:50 PM ACPI 13 None

: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

and

Warning 1/13/2011 7:21:11 PM ACPI 15 None

: The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.

I noticed this 2 errors that keeps showing up frequently when I was on bios 206. I've flashed to 211 and until now, it is still showing up. I've noticed that these errors are showing up everytime I'm changing my power profile using Power4Gear. Is this problem bad? Is this fixable without having to RMA?

 

They send you a repair summary with your laptop explaining what they did.

Nah, it's a power 4 gear problem.

 

I am getting the same error WHEA-Logger eventid 17;

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

in my event viewer (system file). Although my laptop doesn't crash. I haven't noticed any massive perfomance drop but I suspect there might be. Unless this is happening to everybody?

My bios is 209, stock vbios, and Catalyst 10.1.

 

Nope, not happening to everyone. I had this happen over the summer, and when I posted about it, there was no response.

 

How did your one stop? Did you find updating to the Beta Vbios (from Gary Key) to help?

 

Thought I'd mention (for search engine readers more than Asus users) that I'm also seeing the identical error -- on an HP 8540p i7 laptop with 12GB (in case that matters).

The connection may be that I think this device uses a Pegatron MBO, which is an Asus sister company.

For the uninitiated, this is a bugcheck that would have resulted in a BSOD in the past, but is being caught by Windows 7 before the crash.

An HP support analyst is surmising a driver problem in recovering from sleep mode, though I only allow the monitor to sleep on my computer (it's used for pro audio). While plausible, I am dubious about this diagnosis as there is no minidump to study from the frequent ID 17's thrown to the event log.

Component: PCI Express root port
Vendor ID: Device ID: 0x8086:0xd138
Class code: 0x30400

 

For those getting this error on the PCI Express bus...

Do you have Link State Power Management turned on for the PCI bus? If so, try turning it off (it's in the selected power plan's advanced settings).

 

A good tip.

In my case, it was already off.

In reviewing the settings, though, I noticed that USB Selective suspend setting was enabled, which it shouldn't be in my case; one of the numerous USB audio / MIDI drivers might get put to sleep.

Postscript: I made that small change and it didn't seem to help. Threw 7 of these errors in the space of 2 minutes.

 

7 errors in 2 minutes is better than the 10k I was getting per second, when it happened to me.

There's a theory going around that it's a problem cooling the northbridge (c2d boards) chipset (core i3/5/7 boards) that creates these problems... but people who experience the error on desktops can easily test their chipset temps and it's not always the case.

Basically, many problems can cause this error - figuring out what is causing it on our g73s may or may not help people on other platforms.

Nope. I had to RMA.

 

Just a quick updates, I've re-installed the OS with a fresh copy of Windows 7 x64, and all drivers from the drivers cd. Then I install all windows update.
I noticed the error dissapear and I dont have the WHEA-Logger filling up my system log anymore.

Skipp a few days later as I was playing an MMO game on the laptop, I had a BSOD, and my main OS drive dissapear from bios.

I've removed both hardrive and plugged them back in, before it would shows up in bios and windows would boot again.

In windows the system log is full and WHEA-Logger is back, so I called asus and arrange an RMA for them to fix it.

 

UPDATE
I reluctantly reinstalled Windows 7 x64 and it made no difference, so HP authorized an RMA on this 8540p (I think same or similar MBO as the Asus).

This Intel community post was relevant, though most there seem to be chasing an AMD graphics card issue (mine is NVidia). The last of four HP techs thought it was possibly an Nvidia 5100M issue.

Will advise when it comes back from repair.

 

Hey did someone get this error go away or fixed by Asus support?

From what I read in this blog it is a problem with mobo which ois produced by the same taiwanise manufacturer for asus and hp. Yes people with hp laptos kept getting this error too. Well I can tell you it is not a graphic card issue. I have put mine 5870m in my colleges' G73 and no WHEA event id 17. So definitely a problem with MOBO.
Another question is if it is worth fixing and will Asus support replace the mobo? Had anyone it's mobo replaced because on Whea eventID 17?
And if G73jh is throwing 17 like crazy (in tens a minute) does this mean mobo is going to die soon?

 

I Registered (even though I do not have a notebook yet), to say thank you, that answer was very very good - it NEVER dawned on me that the USB would be going to sleep to save power!.

I just set USB Selective suspend off, but this was a embedded checkbox option that was by no means what I thought was causing issues.

Again
Thank YOU!
Duftopia