Wolfenstein 2009: WHEA-Logger Event ID: 18 crash

Page 1 of 2 12 LastLast

  1. Posts : 38
    Windows 7 x64 Ultimate
       #1

    Wolfenstein 2009: WHEA-Logger Event ID: 18 crash


    This is the first game I'm trying in Windows 7 (it's the RTM). The settings are maxed. After a while it crashes on a black screen, with "Out of range" message on the monitor sometimes.
    The only way I got the game working was by installing the DirectX 9 that came on the DVD, otherwise the game kept on telling me it misses some D3D9 stuff. This worried me, but Dxdiag seems to report DirectX 11 fully functional.
    Also, my videocard (it's speeds are stock) is heating very much with this game (88-90 Celsius), but this should be just fine with HD 4850. The fan also spins like crazy, in XP it never raised above 8700 rpm (which should be ok as far as I know), in this game + Win 7 it's going into 11000...
    The CPU, a stock E7200 (2533 MHz) also heats up a lot - 55 Celsius (compared to other games in XP that I played), even if it never goes past 75% usage. Unreal (last ver.) engine games use it 100% and it stays on 50 Celsius. The CPU fan also spins like crazy for a game, 2200 rpm. In XP it never got past 1900 rpm in games, only in testing/benchmarking.
    I tested the CPU (and memory) stability with Linpack (57-60 Celsius max), OCCT, and Everest too. The values I mention come from .csv files Everest is logging. The system is stable under the stress tests. As a matter of fact, the Wolfenstein gave my Win 7 the only BSODs and crashes.
    Thank you for your help.


    The actual event:

    Log Name: System
    Source: Microsoft-Windows-WHEA-Logger
    Date: 20.08.2009 18:13:24
    Event ID: 18
    Task Category: None
    Level: Error
    Keywords:
    User: LOCAL SERVICE
    Computer: toyz
    Description:
    A fatal hardware error has occurred.

    Reported by component: Processor Core
    Error Source: Machine Check Exception
    Error Type: Bus/Interconnect Error
    Processor ID: 0

    The details view of this entry contains further information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
    <EventID>18</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2009-08-20T15:13:24.455631500Z" />
    <EventRecordID>14117</EventRecordID>
    <Correlation ActivityID="{EF43DFD1-3165-450E-BF69-4D1017AD5B54}" />
    <Execution ProcessID="1424" ThreadID="2272" />
    <Channel>System</Channel>
    <Computer>toyz</Computer>
    <Security UserID="S-1-5-19" />
    </System>
    <EventData>
    <Data Name="ErrorSource">3</Data>
    <Data Name="ApicId">0</Data>
    <Data Name="MCABank">5</Data>
    <Data Name="MciStat">0xf200001034000e0f</Data>
    <Data Name="MciAddr">0x0</Data>
    <Data Name="MciMisc">0x0</Data>
    <Data Name="ErrorType">10</Data>
    <Data Name="TransactionType">256</Data>
    <Data Name="Participation">3</Data>
    <Data Name="RequestType">0</Data>
    <Data Name="MemorIO">3</Data>
    <Data Name="MemHierarchyLvl">3</Data>
    <Data Name="Timeout">0</Data>
    <Data Name="OperationType">256</Data>
    <Data Name="Channel">256</Data>
    <Data Name="Length">928</Data>
    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A00300000B0D0F0014080914000000000000000000000 0000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE 14913BBA46475B8A821CA0102000000000000000000000000000000000000000000000058010000C00000000102000001000 000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000 00000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D000000000000000000000 0000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF 94257459C33565E5CC3F7E800000000000000000000000000000000010000000000000000000000000000000000000000000 0007F01000000000000000204000003000076060100000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000700000000000 000000000000000000076060100000802009DE30800FFFBEBBF0000000000000000000000000000000000000000000000000 000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0E606000000000000000000000000000 000000000000000000000000000000000000000000001000000010000007DAD8BBBA821CA010000000000000000000000000 000000000000000050000000F0E0034100000F20000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000</Data>
    </EventData>
    </Event>
      My Computer


  2. Posts : 1
    Windows XP SP3
       #2

    The same thing happens to me quite oftenly, and only when I play Wolfenstein 09. It really heats up my GPU and most of the time my PC ends crashing in a BSOD. I don't know what this game does to stress the computer that hard, no other game does it. I do hope they release a patch for it, to make it playable. It's a pity really. I even bought an additional case cooler, but not even that helped in the end
      My Computer


  3. Posts : 7,878
    Windows 7 Ultimate x64
       #3

    Hmmmm....that doesn't sound good. I just picked up the game tonight and was debating between the PC version and the 360 and I went with the PC version. Hopefully I won't experience all of these problems.
      My Computer


  4. Posts : 1
    Windows 7
       #4

    I do not have any problems with this game so far.
      My Computer


  5. Posts : 12,364
    8 Pro x64
       #5

    I must admit I don't have any problems either and despite it being a heavily GPU dependant game, it actually runs a lot cooler those some games
      My Computer


  6. Posts : 7,878
    Windows 7 Ultimate x64
       #6

    I've been playing it for about an hour on my PC and haven't noticed any issues. Think my video card was around 60 Celsius and it had the fan running at 60%...but box seemed stable. I noticed my Q9550 core temps were only showing mid 30's when I exited out of the game. I'm idling now between 24 and 29 Celcius on my 4 cores. My GPU hovers right around 42 Celcius.
      My Computer


  7. Posts : 12,364
    8 Pro x64
       #7

    These are some screenshots of my Everest logs after running Wolfenstein for a few hours-

    Single Card:
    Wolfenstein 2009: WHEA-Logger Event ID: 18 crash-wolf-single.png

    Dual Card:
    Wolfenstein 2009: WHEA-Logger Event ID: 18 crash-wolf-s-double.png

    As you can see, the GPU does most of the work, but the temps are still relatively cool (both GPUS are overclocked as well)

    It's not a particularly demanding game.
      My Computer


  8. Posts : 38
    Windows 7 x64 Ultimate
    Thread Starter
       #8

    Thank you all for your replies!


    Update:

    1. The game played ok on lower resolution (1680x1050) for a few hours. It is starting to seem like a temperature issue.
    2. With FurMark at 1080p, 8xAA, my system ran for hours in the hottest part of the day (35 Celsius), max temp is like 96-98 Celsius.
    3. What seems to bring down my GPU is the lights on a scene. Whenever BJ looks ar one or moves around it, GPU fan start spinning like crazy.
    4. It's damn unusual that the error reported by the OS is a CPU one, although it seems that the GPU is having problems.
    5. It seems that Win 7, Catalyst 9.8 or who knows what is having problems monitoring/adjusting temps.
    6. If I have time I'll try posting a csv graph of the temps during a 1080p session and a 1680x1050 one.
      My Computer


  9. Posts : 38
    Windows 7 x64 Ultimate
    Thread Starter
       #9

    Still crashes, even at 1680x1050


    I promised I'll post some palpable data, so here I am with 2 Everest monitoring logs that should say a lot about what is happening in my system.
    The game crashed at 1680x1050 too after a few hours, but the temps were reasonable and in no way high for a E7200 or a HD 4850, you can take a look for yourselves. This crash happened once on the ATI driver and once on the exe file, both problems were recovered by Windows (no rebooting necessary like the 1080p processor issue described in the first post).
    I am playing now the game in Administrator mode and with Vista (no SP selected) compatibility, and I managed to achieve two clean runs of 2-4 hours each. I certainly hope this is a Wolfenstein issue, and Windows 7 is 100% ready for gaming :)
    Attached Thumbnails Attached Thumbnails Wolfenstein 2009: WHEA-Logger Event ID: 18 crash-crash-log-1080p.png   Wolfenstein 2009: WHEA-Logger Event ID: 18 crash-crash-log-1650x1050.png  
      My Computer


  10. Posts : 12,364
    8 Pro x64
       #10

    toyo said:
    Update:


    5. It seems that Win 7, Catalyst 9.8 or who knows what is having problems monitoring/adjusting temps.
    After looking at those temps, the card is running warm - within specs -but still warm.

    It may be worthwhile creating a profile and manually increasing your cards fan speed, however that's probably not be the issue.

    The game shouldn't need to run in compatibility or admin though. I haven't had any problems with this game (so far)

    Have you installed your motherboards chipset drivers?

    Are you overclocking?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 21:32.
Find Us