Seite 7 von 7 ErsteErste ... 567
Ergebnis 61 bis 65 von 65

Thema: Abstürze, Fatal Errors , Bluescreen (BSOD) usw. | Forums

  1. #61
    also...ich hab folgendes problem...
    unzwar stürzt sc:da immer an der gleichen stelle ab...unzwar in der dritten mission? (shanghai) wenn ich in das zimmer des doc soll und die papiere aus dem save holen soll...uzwar bevor man ins zimmer gehe,speicher das spiel ja automatisch ab...und da bleibt der einfach hängen...(bekomme dann immer ne visual c++ distib.. fehlermeldung)hab dann neugestartet(save und lvl)und immer das gleiche...und auch nur an dieser stelle...

    hab den neusten patch druff...frag net welchen :-) hab über den updater gepatcht..

    ich benutze vista 32 (home-Prem) sp1
    3gb ram
    amd x2 5000+(2,6ghz)+amd duel core opti...
    gforce 9800gt
    ...
    was ich vergessen hab...treiber sind ale up to date.. :-)








    ich hoffe mir kann jemand helfen...
    danke schon mal im vorraus

  2. #62
    Hi!
    Habe auch ein Bluescreen Problem - nach zwei bis drei Stunden zocken ist noch alles in Ordnung. Lasse ich dann aber den Rechner für ein paar Stunden in Ruhe kommt dieser Bluescreen:


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini010709-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Programme\Debugging Tools for Windows (x86)\Zeichen*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Jan 7 03:35:08.265 2009 (GMT+1)
    System Uptime: 4 days 11:34:17.887
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ................
    Loading User Symbols
    Loading unloaded module list
    ...................................
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {80f1cb4c, 1c, 1, 80502386}

    Probably caused by : ntkrpamp.exe ( nt!KiInsertTimerTable+4e )

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

    1: kd> !analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 80f1cb4c, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 80502386, address which referenced memory

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


    WRITE_ADDRESS: 80f1cb4c

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KiInsertTimerTable+4e
    80502386 894204 mov dword ptr [edx+4],eax

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    TRAP_FRAME: aa380c40 -- (.trap 0xffffffffaa380c40)
    ErrCode = 00000002
    eax=88f97b28 ebx=88f97a80 ecx=8055cb48 edx=80f1cb48 esi=88f97b10 edi=8055cb48
    eip=80502386 esp=aa380cb4 ebp=aa380cbc iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!KiInsertTimerTable+0x4e:
    80502386 894204 mov dword ptr [edx+4],eax ds:0023:80f1cb4c=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 80502386 to 805446f0

    STACK_TEXT:
    aa380c40 80502386 badb0d00 80f1cb48 88ba8290 nt!KiTrap0E+0x238
    aa380cbc 8050245b fffec780 ffffffff a7b0361a nt!KiInsertTimerTable+0x4e
    aa380cd8 804fa968 fffec780 ffffffff aa380d64 nt!KiInsertTreeTimer+0x7d
    aa380d0c 806160b9 00e8fb01 00000000 aa380d2c nt!KeDelayExecutionThread+0xee
    aa380d54 8054162c 00000000 00e8feb0 00e8fed8 nt!NtDelayExecution+0x87
    aa380d54 7c91e4f4 00000000 00e8feb0 00e8fed8 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00e8fed8 00000000 00000000 00000000 00000000 0x7c91e4f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiInsertTimerTable+4e
    80502386 894204 mov dword ptr [edx+4],eax

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiInsertTimerTable+4e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

    FAILURE_BUCKET_ID: 0xA_nt!KiInsertTimerTable+4e

    BUCKET_ID: 0xA_nt!KiInsertTimerTable+4e

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

  3. #63
    Ich hab ein halbes Jahr gebraucht um die Grafik so hin zu bekommen, dass ich wenigstens Sam sehen kann! Und jetzt komme ich in der ersten Mission bis zum 1. Mal Auftauchen und dann... Bluescreen, Systemneustart. Aus der Hilfe auf Seite 1 werde ich auch nicht schlau. Mit dem SAN-Tool heißt es immer ich soll den Dual-Core-Optimizer installieren und meinen Soundkartentreiber aktualisieren. Ich frag mich allersings... WIE OFT NOCH!!!!
    Ich hab die Anweisungen auf Seite 1 befolgt! Hier ein Ausschnitt aus der dumpfile Datei:

    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, b667d01e, b59ab70c, 0}

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

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

    *** WARNING: Unable to verify timestamp for portcls.sys
    *** ERROR: Module load completed but symbols could not be loaded for portcls.sys
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    *** WARNING: Unable to verify timestamp for sysaudio.sys
    *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
    Probably caused by : RtkHDAud.sys ( RtkHDAud+6301e )

    Followup: MachineOwner


    Also ich erkenne da einen Fehler mit der Soundkarte! Aber wieso? Treiber ist aktualisiert, Beschleunigung eingestellt.

    Bitte was soll ich noch alles machen?

    Über das SAN-Tool heißt es außerdem mein Chipsatz wird nicht erkannt! Da kann ich allerdings nichts machen! Ich finde einfach keine Treiber dafür!

    Langsam hab ich cht die Schnauze voll. Weiß jemand wie ich das Spiel endlich zum laufen bekomme?

  4. #64
    Bei mir stimmt im Ochotskischem Meer irgendwas mit dem OPSAT nicht.
    Sobald ich im OPSAT einen Menüpunkt auswähle, bestätige und daraufhin wieder zurück gehe, stürzt das Spiel mit folgender Meldung ab:





    In allen vorherigen Levels funktioniert das OPSAT einwandfrei. Wie's nach dem Level aussieht, weiß ich noch nicht, da ich das Level nicht schaffe ohne einmal auf's OPSAT zu schauen.

    Splinter Cell ist gepatched auf Version 1.02

    DXDIAG:
    <pre class="ip-ubbcode-code-pre"> Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.080814-1236)
    System Manufacturer: NVIDIA
    Processor: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz (4 CPUs)
    Memory: 2814MB RAM
    Page File: 889MB used, 5987MB available
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
    DxDiag Version: 5.03.2600.5512 32bit Unicode
    DirectX Files Tab: No problems found.
    Display Tab 1: No problems found.
    Sound Tab 1: No problems found.

    Display Devices
    Card name: NVIDIA GeForce 8800 GTS 512
    Manufacturer: NVIDIA
    Chip type: GeForce 8800 GTS 512
    Display Memory: 512.0 MB
    Current Mode: 1920 x 1200 (32 bit) (60Hz)
    Monitor: SyncMaster 245B/245BW/245BPlus(Digital)
    Driver Version: 6.14.0011.8120 (English)
    Driver Version: 5.12.0001.0646 (English)
    Driver Version: 5.10.0000.5497 (English)
    Driver Version: 5.12.0001.0646 (English)
    Driver Date/Size: 12/26/2008 00:08:00, 6168960 bytes
    DDraw Status: Enabled
    D3D Status: Enabled
    AGP Status: Enabled

    Sound Devices
    Description: Aureon 5.1 Fun Wave
    Description: Realtek HD Audio output
    Description: Realtek HD Audio Input
    Description: Realtek HD Digital input
    Description: Aureon 5.1 Fun Wave
    Driver Version: 5.12.0001.0646 (English)
    Driver Version: 5.10.0000.5497 (English)
    Driver Version: 5.12.0001.0646 (English)
    Date and Size: 10/1/2004 14:06:12, 373952 bytes
    Date and Size: 10/16/2007 17:38:30, 4615168 bytes
    Date and Size: 10/1/2004 14:06:12, 373952 bytes
    Driver Provider: TerraTec Electronic GmbH
    Driver Provider: Realtek Semiconductor Corp.
    HW Accel Level: Basic
    HW Accel Level: Full


    Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.5512 (German), 4/13/2008 19:40:46, 62976 bytes

    Drive: C:
    Free Space: 0.5 GB
    Total Space: 10.0 GB

    Drive: C:
    Model: SAMSUNG HD400LD

    Drive: D:
    Free Space: 11.1 GB
    Total Space: 365.0 GB

    Drive: D:
    Model: SAMSUNG HD400LD

    Drive: M:
    Free Space: 337.3 GB
    Total Space: 953.9 GB

    Drive: M:
    Model: WD 10EACS External USB Device

    Drive: X:
    Free Space: 866.7 GB
    Total Space: 923.1 GB

    Drive: X:
    Model: WDC WD10 01FALS-00J7B SCSI Disk Device

    Drive: G:
    Model: HL-DT-ST DVDRRW GSA-2164D USB Device



    Name: TerraTec Aureon 5.1 Fun
    Name: NVIDIA GeForce 8800 GTS 512
    Name: PCI Standard-PCI-zu-PCI-Brücke
    Name: PCI Standard-RAM-Controller
    Name: PCI Standard-PCI-zu-PCI-Brücke
    Name: PCI Standard-RAM-Controller
    Name: PCI Standard-Host-CPU-Brücke
    Name: NVIDIA nForce Serial ATA Controller
    Name: PCI Standard-PCI-zu-PCI-Brücke
    Name: NVIDIA Network Bus Enumerator
    Name: Microsoft UAA-Bustreiber für High Definition Audio
    Name: PCI Standard-PCI-zu-PCI-Brücke
    Name: Standard-Zweikanal-PCI-IDE-Controller
    Name: Standard erweiterter PCI-zu-USB universeller Hostcontroller
    Name: Standard OpenHCD USB-Hostcontroller
    Name: PCI Standard-RAM-Controller
    Name: NVIDIA nForce PCI System Management
    Name: PCI Standard-ISA-Brücke
    Name: Texas Instruments OHCI-konformer IEEE 1394-Hostcontroller
    Device ID: 0x0600

    G.723K</pre>

    UBI-SAN sagt zwar etwas von zu wenig Speicherplatz auf C:, veralteter Soundkarte und externen Medien, aber es ist wohl ziemlich unwarscheinlich, dass es daran liegt, oder?
    1. Bisher macht meine Soundkarte bei keinem anderen Spiel - auch den sog. "Next-Gen-Spielen" - keine Probleme.
    2. Was hat Splinter Cell mit meinem Speicherplatz auf C: bzw meiner Externen Festplatte zu schaffen? (Nichts!)
    3. Wenn ich mein externes USB-DVD-ROM-Laufwerk entferne, meckert SC rum, dass ich die SC Disc einlegen soll.

    Ich hoffe ich habe soweit zur Fehlerberichtserstattung alles richtig gemacht. Falls nicht bitte ich um Korrektur/-Anmerkungen.

    Vielen Dank schonmal im Voraus für die Hilfe.

  5. #65

    Registriert seit
    Feb 2009
    Beiträge
    1
    Ich habe auch das Problem das mein Rechner abstürzt, nur kann ich gerade mal 5 -10 Minuten spielen, dann kommt der Bluescreen.
    Die Treiber sind alle auf dem neusten Stand und SC ist auch die aktuellste Version.
    Könnt ihr mir weiter helfen?

    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, aaaea01e, a704e70c, 0}

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

    *** WARNING: Unable to verify timestamp for portcls.sys
    *** ERROR: Module load completed but symbols could not be loaded for portcls.sys
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    *** WARNING: Unable to verify timestamp for sysaudio.sys
    *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    ************************************************** ***********************
    ************************************************** *******************
    * 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Probably caused by : RtkHDAud.sys ( RtkHDAud+6301e )

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

    2: kd> g
    ^ No runnable debuggees error in 'g'
    2: kd> .restart /f

    Loading Dump File [C:\Dump\Mini022509-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 <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image 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 XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Feb 25 15:02:50.437 2009 (GMT+1)
    System Uptime: 0 days 0:34:40.295
    ************************************************** *******************
    * 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 <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image 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 RtkHDAud.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RtkHDAud.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, aaaea01e, a704e70c, 0}

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

    *** WARNING: Unable to verify timestamp for portcls.sys
    *** ERROR: Module load completed but symbols could not be loaded for portcls.sys
    *** WARNING: Unable to verify timestamp for ks.sys
    *** ERROR: Module load completed but symbols could not be loaded for ks.sys
    *** WARNING: Unable to verify timestamp for sysaudio.sys
    *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    ************************************************** ***********************
    ************************************************** *******************
    * 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Probably caused by : RtkHDAud.sys ( RtkHDAud+6301e )

Seite 7 von 7 ErsteErste ... 567

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •