Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Warning - HWEA-Logger - Event 17 ; every 3 seconds and counting...

31 Jul 2012   #1

Windows 7 x64
Warning - HWEA-Logger - Event 17 ; every 3 seconds and counting...


I have some unusual and unsolved pc freeze for 1 1/2 years now, always the same and has never been fixed, reformat, sent in, new drives, updates, everything. Just once in a while during normal use or almost always during the use of the flash player ( eg.) or scrolling through a long file list in the explorer; the result is a frozen screen and a sound like porcelain or metal crashing down an echoing staircase (same sound repeating). - But this is not about that, just so you know that there are unsolved issues.

Today (09:43) my pc just stopped and rebooted. And so I checked a few things and found my way to the event viewer, where a warning was displayed:

Warning - WHEA-Logger - Event 17

I went to 'view all instances' and saw that I had over 15000 warnings of the same occurrence since I started my pc on Sunday 12:31.

The last search for an event like this (mostly with 3-4 warnings only) are about 2 years old, therefore I am opening a new thread.

I tried a few things:
- Updated all drivers
- Did different virus scans (kaspersky deep scan still running)
- Checked CPU temperature and cooling system
- Manually checked for new programs /changes in system files etc.

The general display of the Warning itself is:

A corrected hardware error has occurred.

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

Busevice:Function: 0x0:0x3:0x0
Vendor IDevice ID: 0x8086:0x340a
Class Code: 0x30400

The details view of this entry contains further information.

The detail display is:

- <Event xmlns="Error">
- <System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />







<TimeCreated SystemTime="2012-07-31T11:17:18.048538100Z" />


<Correlation ActivityID="{1E578CFD-8BAF-422D-AA59-841D273F8EAD}" />

<Execution ProcessID="1488" ThreadID="2364" />



<Security UserID="S-1-5-19" />


- <EventData>
<Data Name="ErrorSource">4</Data>

<Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data>

<Data Name="FRUText" />

<Data Name="ValidBits">0xdf</Data>

<Data Name="PortType">4</Data>

<Data Name="Version">0x101</Data>

<Data Name="Command">0x10</Data>

<Data Name="Status">0x507</Data>

<Data Name="Bus">0x0</Data>

<Data Name="Device">0x3</Data>

<Data Name="Function">0x0</Data>

<Data Name="Segment">0x0</Data>

<Data Name="SecondaryBus">0x0</Data>

<Data Name="Slot">0x0</Data>

<Data Name="VendorID">0x8086</Data>

<Data Name="DeviceID">0x340a</Data>

<Data Name="ClassCode">0x30400</Data>

<Data Name="DeviceSerialNumber">0x0</Data>

<Data Name="BridgeControl">0x0</Data>

<Data Name="BridgeStatus">0x0</Data>

<Data Name="UncorrectableErrorStatus">0x0</Data>

<Data Name="CorrectableErrorStatus">0x1000</Data>

<Data Name="HeaderLog">00000000000000000000000000000000</Data>

<Data Name="Length">672</Data>

<Data Name="RawData">435045521002FFFFFFFF02000200000002000000A002000010110B001F070C140000000000000000000000000000000000 000000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DAF67C1048F98F5 A4096FCD0100000000000000000000000000000000000000000000000010010000D0000000010200000100000054E995D9C1 BB0F43AD91B44DCB3C6F35000000000000000000000000000000000200000000000000000000000000000000000000000000 00E0010000C00000000102000000000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000003 0000000000000000000000000000000000000000000000DF000000000000000400000001010000100007050000000086800A 3400040300030000000000000000000000000000000000000010E042012180000007010100023D3B00410001F180259000C0 0348010800010000000000000000000000000000000000000000000000000000000000010001150000000000000000102006 0000100000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000043010000000000000002000000000000A50601 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000 0000000000000000000000000000000000000000000000</Data>



Finishing this thread i now have 15962 warnings.....

Thx for your help, and I don't mind some tips regarding the the mentioned ongoing and unsolved problem in the beginning.

My System SpecsSystem Spec
31 Jul 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 64 Bit Home Premium SP1

For WHEA-Logger errors I would suspect chipset drivers.

See if there is an updated version on the manufacturer's website. Just download and execute the chipset driver once you find it. It will tell you if it is already installed.
My System SpecsSystem Spec
04 Aug 2012   #3

Windows 7 x64

Hi, thx for the reply, but as I said, I already checked and installed all of the latest drivers. Also did all windows updates too now, problem still persists.
My System SpecsSystem Spec

04 Aug 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 64 Bit Home Premium SP1

You should fill in your System Specs under your forum profile.

That way I could have easily seen if you have a add-on sound card and the model #.

Is it an on-the-motherboard sound chip or a dedicated sound card?

I'm focusing on the "freeze and scream" behavior. Which can be associated with the sound drivers.
My System SpecsSystem Spec
04 Aug 2012   #5

Windows 7 x64

thx again,

i updated my spec profile, and yes, there were always problems with the sound card(s). the microphone e.g. never worked. i get sound via speakers, but all other options/devices in the windows sound manager are gone and i cant get any back, he doesn't find any. in between the mic worked, even though it was not detected and could not been turned off, even when i muted it, it constantly recorded until i disabled it and then it was gone again, even from the list.

as i mentioned in the profile, i had sent it in, and it cant be the cables or they would have found it, i checked myself too. and i updated both on-board and SB. I also disabled one and then the other to try out different things., btw. if i disable on-board sound, then the SB doesn't work either, which escapes me, since it should substitute the on-board chip .

regarding the driver detective, yeah, he found like 19 out of date even though my other driver scanning program said i was up to date (sound related drivers were not found as out of date or missing).

one was this: intel ich10 family pci express root port 1 3a40; from 2006

which might explain my pci express root warning. what i don't get is, why would i have a 2006 driver in a 2010 bought pc when the latest version is 2009. and that it started having problem now, without any changes to the hardware/software. its not that the driver gets old and says one day" well, i don't wanna do it any longer unless you update me".

and why does a program like driver detective cost money ? and why cant i find the drivers on the manufacturers service pages... i mean, if i screw up, ok, but that drivers get out of date is hardly any users fault.

sorry for my venting, but if i buy a product it is supposed to work. i am really pissed, if i have to pay for this or that service every other week to keep the system clean, up to date, protected, efficient or else.

thx again tough.
My System SpecsSystem Spec
04 Aug 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 64 Bit Home Premium SP1

What you could be experiencing is a driver conflict. The drivers for both sound chips are fighting each other.

Normally it is best when adding a sound card to a system that has on-board sound (and almost all do today) is to disable the on-board sound chip in the system's BIOS or UEFI settings, then install the new sound card.

While it may not be necessary to uninstall the driver for the on board chip as long as it is disabled at the system level (Windows will not usually load drivers for non-existing hardware), I would remove the device from the Device Manager to remove the drivers before I disabled it in the BIOS.

Yours is now a complicated scenario. So you need to do things a bit differently. Here is what I suggest:
  • Go into the Device Manager and find your add-on card. Right click on it > remove (Uninstall) the card.
  • Shut down the computer. Then physically uninstall the card from the machine.
  • Restart > go to the Desktop > back to Device Manager
  • Find the on-board sound device and remove (Uninstall) that too. (If the device is already disabled in the BIOS settings then you will need to re-enable it first)
  • Restart > go immediately into the BIOS settings and disable the on-board sound chip. > restart into Windows
  • You will now have a clean system (no sound devices). Check Device Manager to be sure. You might now want to also run a program like DriverSweeper or CCleaner (or both) to really clean up any old driver fragments.
  • After checking and/or cleaning, restart one more time > then shut down.
  • Now install the add-on sound card and install it's drivers as instructed by the manufacturer.
Test that for a while. Remember: only the sound cards ports for speakers, mic will work. Do not try and use the ones connected to the motherboard, or case. They are not connected to anything.
My System SpecsSystem Spec

 Warning - HWEA-Logger - Event 17 ; every 3 seconds and counting...

Thread Tools

Similar help and support threads
Thread Forum
BSOD. event logger included No clue what is causing it, i tried resetting bios settings, reconnecting my RAM. Googled alot of things and i couldn't find anything of much help. If anyone could give me an indication of what the errors mean you would help me a lot. ...
BSOD Help and Support
Help~ whea-logger event id 17
Hi guys, i am constantly having this warning almost every second in event viewer... (15700+ warning and counting) it started since 9/12 and i don't know what i did.. I never had any problem until i played need for speed: shift today for the first time and it just hard froze on me. so i checked...
BSOD Help and Support
WHEA-Logger event 18/19 errors in Event Viewer (W7 Home Premium)
Hi, I was hoping somebody could offer an insight on the below, as searching around I've not found much to go on other than "overheating" Basically my laptop has been having very high temperatures for a long time (usually ~60C for CPU and often 100-110 for GPU...insanely high, in other words)...
Hardware & Devices
whea-logger event 18
Yesterday I started to get freeze on my computer mainly while playing video game or doing things related to video hardware. I'm suspecting a graphic card failures here, however, I can still play some games and it will work well under severe conditions and sometimes the computer just freeze up,...
BSOD Help and Support
Officially Google Free for 15 seconds and counting.
After reading the F*ck You, Google article on, Completly hating the way Google introduced Buzz, and recently changing my email address to email provider for the nicer UI. I have finally pressed the button to cancel my Google account not even 15 seconds ago from within my Google...
Chillout Room

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:01.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App