logo elektroda
logo elektroda
X
logo elektroda

Windows 10 BSOD in Wolfenstein: Enemy Territory (2003) - Graphics Driver & DirectX Issues

Myrasz 17397 10
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16570156
    Myrasz
    Level 20  
    Witam,
    Sprawa wygląda następująco: znajomy namówił mnie na powrót do gry z przed lat: Wolfenstein: Enemy Territory(2003 r.). Problem polega na tym, że po kilkunastu/kilkudziesięciu minutach, system wyrzuca BSOD jak poniżej:
    Windows 10 BSOD in Wolfenstein: Enemy Territory (2003) - Graphics Driver & DirectX Issues
    Z pliku .dmp (jak i z internetów) da się wyczytać, że chodzi o sterownik karty graficznej tudzież DirectX:
    Spoiler:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\xxx\Desktop\070117-27015-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 15063 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    Machine Name:
    Kernel base = 0xfffff801`cbe86000 PsLoadedModuleList = 0xfffff801`cc1d25a0
    Debug session time: Sat Jul 1 12:27:24.596 2017 (GMT+2)
    System Uptime: 0 days 2:14:29.360
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    Unable to load image \ SystemRoot \ System32 \ drivers \ dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module has been loaded for dxgkrnl.sys
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use! Analyze -v to get detailed debugging information.

    BugCheck 100000EA, {ffff8800dc1f97c0, 0, 0, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ************************************************** ******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y argument when starting the debugger. *
    * using .sympath and .sympath + *
    ************************************************** *******************
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y argument when starting the debugger. *
    * using .sympath and .sympath + *
    ************************************************** *******************
    Probably caused by: dxgkrnl.sys (dxgkrnl + 35f5b)

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

    I have the latest drivers for the graphics card. I switched to older versions (2015/2012). I also uninstalled the device and reinstalled - it did not work. BSOD only pops up in this game - the (new) newer titles work without a problem. CPU and GPU temperatures are around 40-45 deg. C during the game. I would like to add that the game was used last year (also holiday season) on W7 as well as on W10 (previous compilations) - it worked without any problems.

    Below is the specification of my old lady:
    Windows 10 Pro 64bit (build: 15063.413, version: 1703)
    ASUS P5-QLE
    Intel Core 2 Quad 6600 (~ 3.0 GHz)
    8 GB RAM
    AMD Radeon HD 7700 (PowerColor)
    Unimportant power supply, because there is nothing in this case, I think I saw it, on the "black list" - it has been used for 8 years and I have no problems with it. SMART disk is OK.
    I will be grateful for hints.
  • ADVERTISEMENT
  • #2 16571093
    kiss39
    Level 39  
    Myrasz wrote:
    Unimportant power supply, because there is nothing in this case, I think I saw it, on the "black list"


    It's your PC and I will say that such a PSU can damage the electronics, give the link, maybe you have not seen it and change your mind Black list of power supplies and renowned power supply brands

    Hardware

    Check how the power supply works under load, and more precisely its voltage on individual lines + 12V, + 5V, 3.3V. The power supply should meet certain voltage and fluctuation norms, as regards voltage standards, please visit Elektod at the Department - Computers -
    How to measure voltage with a meter?

    Voltage norms on individual lines.
    Windows 10 BSOD in Wolfenstein: Enemy Territory (2003) - Graphics Driver & DirectX Issues


    Software


    The reason for the appearance of BSOD may be several eg. One is to delete * .dll files from the library (files are related) to the system which happens frequently, the second option is top, e.g., incompatibility of files with new WIN7 / 8/10 systems

    Help can be properly compatible with Windows by choosing a game file with the extension *. exe PM> properties> "Compatibility" tab and select the appropriate system.

    Windows 10 BSOD in Wolfenstein: Enemy Territory (2003) - Graphics Driver & DirectX Issues
  • ADVERTISEMENT
  • #3 16571102
    Robert B
    Level 43  
    Myrasz wrote:
    Unimportant power supply, because there is nothing to do in this case,

    If you know best, why do you ask for help?
    Did you take measurements?
    https://www.elektroda.pl/rtvforum/topic1199202.html
    Have you checked the state of the capacitors on the board, card and power supply?
  • ADVERTISEMENT
  • #4 16571149
    Myrasz
    Level 20  
    @ kiss39 & @_robert_ B
    I take care of my equipment at the software and hardware level. For more than 20 years, the only parts that have failed were 2 graphics cards and 1x HDD. I dealt with the soft majority mostly alone or with the help of others. The number of famous C formats: , throughout this period, it is on the fingers of one hand.
    If something is wrong, and considering the power supply that I have - I always check the voltage - they are all normal from the beginning. The motherboard - due to its age, is also observed for capacitors, as well as for other possible damage.

    Robert B wrote:
    If you know best, why do you ask for help?

    The answer is simple: in this case, I simply know better, because before writing the thread I checked all the voltage of the power supply, I looked at the motherboard, I did SMART, RAM, load GPU \ CPU tests and in no case did I receive disturbing results. So I exclude the problem with hardware and the topic I founded in the software department, hoping that there will be someone who could have a similar problem or someone who has knowledge of how to solve my problem.

    @ kiss39 The compatibility mode was the first thing I checked - unfortunately it does not make a difference - BSOD occurs.
  • #5 16571182
    Robert B
    Level 43  
    Myrasz wrote:
    before writing the thread I checked all the voltage of the power supply, I looked at the motherboard, I did SMART, RAM, load GPU \ CPU tests and in no case did I receive any disturbing results.

    And such information should be included in the opening post, because no one here is a fortune teller to know what you have done and what knowledge you have about it.
    Since the problem concerns only one game, the reason may be a prosaic damage to one of its files.
    Voltage from the power supply is not everything. The reason may be pins, which you will not measure with a multimeter. The oscilloscope or substitute of the power supply remains hardware.
  • ADVERTISEMENT
  • #6 16571718
    kiss39
    Level 39  
    Robert B wrote:
    The reason may be pins, which you will not measure with a multimeter. The oscilloscope or substitute of the power supply remains hardware.

    - "SZPILKI", so these are these fluctuations, for example (from 12.18V to 12.23V) I associate well?
  • #7 16571846
    Robert B
    Level 43  
    These are not voltage fluctuations. Stilts or voltage peaks are short-lived and sharp. Not measurable with a multimeter and in poor power supplies can exceed the admissible values several times. They cause, at best, disruptions in the operation of the motherboard and other components, and in the worst case, their permanent damage.
    kiss39 wrote:
    (from 12.18V to 12.23V)

    :lol: You bet too little. I watched on an oscilloscope with values over 18V on the 12V line and over 9V on the 5V line.
    Measurements that the author has no idea about.
  • #8 16572310
    kiss39
    Level 39  
    I do not know if I am carefully measuring the voltage from my XFX TS 550 Watt, but it was such a difference: nothing happens to the PC.

    - on the desktop, 12.15V and 0.00V
    - under stress: 12.25V and 0.001V
  • #10 16574018
    kiss39
    Level 39  
    Robert B wrote:
    A meter or program?


    I checked the multimeter. When I have time, I will check the voltage again and record the results. As the voltage will vary a lot, I will ask Support XFX what they think about it.
  • #11 16574302
    Myrasz
    Level 20  
    Solution:
    I managed to deal with the problem - of course, as I suspected in 99.9999%, knowing the symptoms and describing them here - it was about soft, and more specifically about the return to the older graphics card drivers + DirectX re-installation.

    Offtopic at the end:
    I observe this forum for several years and I am always amused by people like p. Robert B. who with technical-electrical engineering or other professions are diligently looking for a problem in the intentional part of the PC power supply. I do not deny that it is not one of the most important parts, but a heavy one ... y n ... y - if all signs clearly indicate first on the need to verify the software:
    * .dmp file,
    * description of the problem by the author;
    It's hard for people to push nonsense about the power supply !?
    You have problems with the graphics card - check it (drivers, temperature, replace with another one, etc.).
    You have problems with the disk - make SMART, temperature, check in another computer, remap, etc.
    If after all other treatments there is still a problem - then you go to the power supply / motherboard ... Why complicate your life?
    Well, pity - I think I hurried up with this thread, but although others will find a solution here ... And if not, they will buy a new power supply.

Topic summary

The discussion revolves around a user experiencing a Blue Screen of Death (BSOD) while playing Wolfenstein: Enemy Territory (2003) on Windows 10. The user suspects issues with the graphics driver or DirectX, despite having the latest drivers installed. Various responses suggest checking hardware components, particularly the power supply unit (PSU) and its voltage stability under load. The user confirms that all hardware checks, including voltage measurements and temperature monitoring, show normal results. Ultimately, the user resolves the issue by reverting to older graphics card drivers and reinstalling DirectX, indicating that the problem was software-related rather than hardware-related.
Summary generated by the language model.
ADVERTISEMENT