• So, jetzt will ich auch mal... Habe meinen pc vor kurzem neu aufgesetzt, da auch damals dieses Problem auftrat, ich habe, wenn ich den PC anschalte, häufiger einen absturtz mit blue screen das passiert in der ersten stunde vllt 2 3 mal. aber nicht regelmäßig.
    debuginfos:

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


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

    Symbol search path is: C:\Dokumente und Einstellungen\markus\Eigene Dateien\Downloads\a-squared
    Executable search path is:
    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) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
    Debug session time: Thu Aug 13 10:09:53.640 2009 (GMT+2)
    System Uptime: 0 days 0:08:26.234
    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
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000C5, {70627375, 2, 1, 80544683}

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

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *** WARNING: Unable to verify timestamp for PCIIDEX.SYS
    *** ERROR: Module load completed but symbols could not be loaded for PCIIDEX.SYS
    *** WARNING: Unable to verify timestamp for atapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for atapi.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 ***
    *** ***
    *************************************************************************
    Probably caused by : PCIIDEX.SYS ( PCIIDEX+c91 )

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

    kd> analyze -v
    *** WARNING: Unable to verify timestamp for kmixer.sys
    *** ERROR: Module load completed but symbols could not be loaded for kmixer.sys
    *** WARNING: Unable to verify timestamp for srv.sys
    *** ERROR: Module load completed but symbols could not be loaded for srv.sys
    *** WARNING: Unable to verify timestamp for wdmaud.sys
    *** ERROR: Module load completed but symbols could not be loaded for wdmaud.sys
    *** WARNING: Unable to verify timestamp for mrxdav.sys
    *** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
    *** WARNING: Unable to verify timestamp for ndisuio.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
    *** WARNING: Unable to verify timestamp for avgntflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for dxg.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxg.sys
    *** WARNING: Unable to verify timestamp for JAWSVID.dll
    *** ERROR: Module load completed but symbols could not be loaded for JAWSVID.dll
    *** WARNING: Unable to verify timestamp for dcmc0d0.dll
    *** ERROR: Module load completed but symbols could not be loaded for dcmc0d0.dll
    *** WARNING: Unable to verify timestamp for dump_atapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
    *** WARNING: Unable to verify timestamp for avipbb.sys
    *** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
    *** WARNING: Unable to verify timestamp for ipnat.sys
    *** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
    *** WARNING: Unable to verify timestamp for mrxsmb.sys
    *** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
    *** WARNING: Unable to verify timestamp for rdbss.sys
    *** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    *** WARNING: Unable to verify timestamp for netbt.sys
    *** ERROR: Module load completed but symbols could not be loaded for netbt.sys
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *** WARNING: Unable to verify timestamp for ipsec.sys
    *** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
    *** WARNING: Unable to verify timestamp for Dxapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for Dxapi.sys
    *** 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 RtkHDAud.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
    *** WARNING: Unable to verify timestamp for update.sys
    *** ERROR: Module load completed but symbols could not be loaded for update.sys
    *** WARNING: Unable to verify timestamp for psched.sys
    *** ERROR: Module load completed but symbols could not be loaded for psched.sys
    *** WARNING: Unable to verify timestamp for ndiswan.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndiswan.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 parport.sys
    *** ERROR: Module load completed but symbols could not be loaded for parport.sys
    *** WARNING: Unable to verify timestamp for USBPORT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
    *** WARNING: Unable to verify timestamp for HDAudBus.sys
    *** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
    *** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS
    *** WARNING: Unable to verify timestamp for nv4_mini.sys
    *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
    *** WARNING: Unable to verify timestamp for Mup.sys
    *** ERROR: Module load completed but symbols could not be loaded for Mup.sys
    *** WARNING: Unable to verify timestamp for NDIS.sys
    *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
    *** WARNING: Unable to verify timestamp for Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    *** WARNING: Unable to verify timestamp for KSecDD.sys
    *** ERROR: Module load completed but symbols could not be loaded for KSecDD.sys
    *** WARNING: Unable to verify timestamp for sr.sys
    *** ERROR: Module load completed but symbols could not be loaded for sr.sys
    *** WARNING: Unable to verify timestamp for fltmgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
    *** WARNING: Unable to verify timestamp for ftdisk.sys
    *** ERROR: Module load completed but symbols could not be loaded for ftdisk.sys
    *** WARNING: Unable to verify timestamp for pci.sys
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    *** WARNING: Unable to verify timestamp for ACPI.sys
    *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
    *** WARNING: Unable to verify timestamp for isapnp.sys
    *** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
    *** WARNING: Unable to verify timestamp for ohci1394.sys
    *** ERROR: Module load completed but symbols could not be loaded for ohci1394.sys
    *** WARNING: Unable to verify timestamp for 1394BUS.SYS
    *** ERROR: Module load completed but symbols could not be loaded for 1394BUS.SYS
    *** WARNING: Unable to verify timestamp for MountMgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for MountMgr.sys
    *** WARNING: Unable to verify timestamp for VolSnap.sys
    *** ERROR: Module load completed but symbols could not be loaded for VolSnap.sys
    *** WARNING: Unable to verify timestamp for disk.sys
    *** ERROR: Module load completed but symbols could not be loaded for disk.sys
    *** WARNING: Unable to verify timestamp for CLASSPNP.SYS
    *** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
    *** WARNING: Unable to verify timestamp for wanarp.sys
    *** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
    *** WARNING: Unable to verify timestamp for arp1394.sys
    *** ERROR: Module load completed but symbols could not be loaded for arp1394.sys
    *** WARNING: Unable to verify timestamp for Cdfs.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
    *** WARNING: Unable to verify timestamp for nic1394.sys
    *** ERROR: Module load completed but symbols could not be loaded for nic1394.sys
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    *** WARNING: Unable to verify timestamp for serial.sys
    *** ERROR: Module load completed but symbols could not be loaded for serial.sys
    *** WARNING: Unable to verify timestamp for i8042prt.sys
    *** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
    *** WARNING: Unable to verify timestamp for cdrom.sys
    *** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
    *** WARNING: Unable to verify timestamp for redbook.sys
    *** ERROR: Module load completed but symbols could not be loaded for redbook.sys
    *** WARNING: Unable to verify timestamp for imapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for imapi.sys
    *** WARNING: Unable to verify timestamp for rasl2tp.sys
    *** ERROR: Module load completed but symbols could not be loaded for rasl2tp.sys
    *** WARNING: Unable to verify timestamp for raspppoe.sys
    *** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
    *** WARNING: Unable to verify timestamp for raspptp.sys
    *** ERROR: Module load completed but symbols could not be loaded for raspptp.sys
    *** WARNING: Unable to verify timestamp for msgpc.sys
    *** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
    *** WARNING: Unable to verify timestamp for termdd.sys
    *** ERROR: Module load completed but symbols could not be loaded for termdd.sys
    *** WARNING: Unable to verify timestamp for NDProxy.SYS
    *** ERROR: Module load completed but symbols could not be loaded for NDProxy.SYS
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for usbhub.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
    *** WARNING: Unable to verify timestamp for sysaudio.sys
    *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
    *** WARNING: Unable to verify timestamp for netbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for netbios.sys
    *** WARNING: Unable to verify timestamp for Fips.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Fips.SYS
    *** WARNING: Unable to verify timestamp for PartMgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for PartMgr.sys
    *** WARNING: Unable to verify timestamp for usbuhci.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys
    *** WARNING: Unable to verify timestamp for usbehci.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
    *** WARNING: Unable to verify timestamp for RTL8139.SYS
    *** ERROR: Module load completed but symbols could not be loaded for RTL8139.SYS
    *** WARNING: Unable to verify timestamp for mouclass.sys
    *** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
    *** WARNING: Unable to verify timestamp for kbdclass.sys
    *** ERROR: Module load completed but symbols could not be loaded for kbdclass.sys
    *** WARNING: Unable to verify timestamp for TDI.SYS
    *** ERROR: Module load completed but symbols could not be loaded for TDI.SYS
    *** WARNING: Unable to verify timestamp for ptilink.sys
    *** ERROR: Module load completed but symbols could not be loaded for ptilink.sys
    *** WARNING: Unable to verify timestamp for raspti.sys
    *** ERROR: Module load completed but symbols could not be loaded for raspti.sys
    *** WARNING: Unable to verify timestamp for vga.sys
    *** ERROR: Module load completed but symbols could not be loaded for vga.sys
    *** WARNING: Unable to verify timestamp for Msfs.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
    *** WARNING: Unable to verify timestamp for Npfs.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
    *** WARNING: Unable to verify timestamp for ssmdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
    *** WARNING: Unable to verify timestamp for USBSTOR.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS
    *** WARNING: Unable to verify timestamp for watchdog.sys
    *** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
    *** WARNING: Unable to verify timestamp for BOOTVID.dll
    *** ERROR: Module load completed but symbols could not be loaded for BOOTVID.dll
    *** WARNING: Unable to verify timestamp for rasacd.sys
    *** ERROR: Module load completed but symbols could not be loaded for rasacd.sys
    *** WARNING: Unable to verify timestamp for serenum.sys
    *** ERROR: Module load completed but symbols could not be loaded for serenum.sys
    *** WARNING: Unable to verify timestamp for ndistapi.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndistapi.sys
    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** WARNING: Unable to verify timestamp for kdcom.dll
    *** ERROR: Module load completed but symbols could not be loaded for kdcom.dll
    *** WARNING: Unable to verify timestamp for WMILIB.SYS
    *** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
    *** WARNING: Unable to verify timestamp for intelide.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelide.sys
    *** WARNING: Unable to verify timestamp for swenum.sys
    *** ERROR: Module load completed but symbols could not be loaded for swenum.sys
    *** WARNING: Unable to verify timestamp for USBD.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBD.SYS
    *** WARNING: Unable to verify timestamp for Fs_Rec.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
    *** WARNING: Unable to verify timestamp for Beep.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Beep.SYS
    *** WARNING: Unable to verify timestamp for mnmdd.SYS
    *** ERROR: Module load completed but symbols could not be loaded for mnmdd.SYS
    *** WARNING: Unable to verify timestamp for RDPCDD.sys
    *** ERROR: Module load completed but symbols could not be loaded for RDPCDD.sys
    *** WARNING: Unable to verify timestamp for avgio.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgio.sys
    *** WARNING: Unable to verify timestamp for dump_WMILIB.SYS
    *** ERROR: Module load completed but symbols could not be loaded for dump_WMILIB.SYS
    *** WARNING: Unable to verify timestamp for PCIIde.sys
    *** ERROR: Module load completed but symbols could not be loaded for PCIIde.sys
    *** WARNING: Unable to verify timestamp for Null.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Null.SYS
    *** WARNING: Unable to verify timestamp for dxgthk.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgthk.sys
    *** WARNING: Unable to verify timestamp for audstub.sys
    *** ERROR: Module load completed but symbols could not be loaded for audstub.sys
    Couldn't resolve error at 'nalyze -v'
    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is
    caused by drivers that have corrupted the system pool. Run the driver
    verifier against *** new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 70627375, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 80544683, address which referenced memory

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

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

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: PCIIDEX

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d

    BUGCHECK_STR: 0xC5_2

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt+6d683
    80544683 8913 mov dword ptr [ebx],edx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from 80544cef to 80544683

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80549bc0 80544cef 860383e0 8650f83c 00000001 nt+0x6d683
    80549c00 806d4a7f 85e36ef8 00000000 8650f7a8 nt+0x6dcef
    80549c1c f785bc91 865aa210 85e36ef8 00000000 hal+0x4a7f
    80549c3c f746aaff 8650f7a8 80552a20 805527c0 PCIIDEX+0xc91
    80549cac 80541b9d 865930a4 86593030 00000000 atapi+0x7aff
    80549cb0 865930a4 86593030 00000000 00000000 nt+0x6ab9d
    80549cb4 86593030 00000000 00000000 805527c0 0x865930a4
    80549cb8 00000000 00000000 805527c0 ffdffc50 0x86593030


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    PCIIDEX+c91
    f785bc91 ?? ???

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: PCIIDEX+c91

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: PCIIDEX.SYS

    BUCKET_ID: WRONG_SYMBOLS

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

    • Anzeige

    Hallo!

    Wenn du gerade an deiner Website arbeitest oder dein aktuelles Hosting überdenkst: Wir betreiben mit NetzLiving eine Hosting-Plattform, die speziell auf Performance, Sicherheit und einfache Verwaltung ausgelegt ist.

    • ✔️ Schnelle Ladezeiten (optimiert für WordPress, WoltLab & Co.)
    • ✔️ Deutsche Server & DSGVO-konform
    • ✔️ Persönlicher Support (kein 0815-Ticket-System)

    Mehr erfahren

  • Hi Markus,

    möglich, dass deine ntoskernel defekt ist. Dann kannst du wie ->hier unter Methode 3 beschrieben<- die Datei erneuern.

    Auch möglich, dass ein Hardwarekonflikt oder -defekt vorliegt. Dann würde ich zunächst per ersuch & Irrtum versuchen herauszufenden, wer der Täter ist. Denkbar für mich wären in der Reihenfolge der Wahrscheinlichkeit Netzteil, Arbeitsspeicher, Systemfestplatte oder Festplattencontroller der Hauptplatine.

    Gruß,
    Tunarus

  • ...noch ´ne Möglichkeit. Der Hinweis auf die Datei pciidex.sys in deiner Meldung könnte auch auf Laufwerksprobleme im Zusammenhang mit einem RAID Controller hindeuten. Bei dieser Datei handelt es sich um die PCI IDE Bus Driver Extension. Wenn du kein RAID verwendest, aber einen vorhandenen RAID Controller auf der Hauptplatine aktiviert hast, dann versuche mal testweise den RAID Controller im BIOS zu deaktivieren.

    Gruß,
    Tunarus

  • Hallo

    Ich tippe mal auf den RAM wenn er sporadisch einfriert :D

    mal mit memtest86 prüfen

    Festplatte einem drive fitness test mit einem Tool vom hersteller unterziehen oder zB mit HDTune

    ein anderes Netzteil würde ich auch mal prüfen wie Tunarus schon geschrieben hat

    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • Hallo

    Ein Versuch ist es wert :) dann stöpsel ihn mal ab

    und probier es aus :)

    was für Mucken macht er denn ?

    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • er brennt nicht mehr. komischerweise tritt das problem erst wieder seit kurzer zeit auf, ich hatte ihn ja neu gemacht und da war ales io erst mal. jetzt läufts ja auch wieder, ist nur wenn ich ihn anschalte, und auch nich immer. hab mal einen shoot vom gerätemanager gemacht
    View image: Unbenannt.gif

  • Hallo

    Der Gerätemanager sieht doch sauber aus :D

    bis auf den oberen Eintrag Andere Geräte

    klick mal auf das + davor und schau was sich noch da verbirgt :)

    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • ich hab ja erst vor 2 wochen neu instaliert.
    neues abbild
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: C:\Dokumente und Einstellungen\markus\Eigene Dateien\Downloads\a-squared
    Executable search path is:
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
    Debug session time: Thu Aug 27 15:07:34.953 2009 (GMT+2)
    System Uptime: 0 days 3:36:54.547
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c000001d, bf819e55, ba8cfc98, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    Probably caused by : win32k.sys ( win32k+19e55 )

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

  • Also entweder hast du dir in dieser Zeit irgendwie das System zerschossen oder es liegt ein Hardware Defekt vor.
    Sporadische Abstürze sind fast immer Netzteil oder Ram.
    Könnte auch das Board sein aber aufgrund der Fehler,die du hast glaub ich das nun weniger.
    Wenn die Festplatte stark fragmentiert ist oder fehlerhafte Sektoren hat,kann auch diese in Frage kommen.
    Lass doch mach chkdsk laufen.
    Wenn das nicht hilft,würde ich versuchen,den Pc erstmal nur mit einem Ram Modul zu betreiben,falls du zwei hast.

  • Hallo

    Videocontroller for Multimedia :D

    Hast du noch eine Steckkarte im rechner wie Fernsehkarte etc.....?

    Ansonsten mal die Grafikkarten Treiber CD einlegen und den Treiber aktualisieren

    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • Hallo

    Besorg dir mal ein Festplattendiagnosetool vom Hersteller der Festplatte

    Mit diesem kannst du den Gesundheitszustand mal checken

    Meistens sind sogar noch Feature Tools dabei womit man an der Leistungsschraube drehen kann :)

    Und überprüfe auch den RAM mit memtest86+

    Einen Virus denke ich können wir ausschließen wenn das system frisch aufgesetzt worden ist,vorausgesetzt du hast Schutzsoftware vor deinem ersten Besuch im Internet wieder aufgespielt :)

    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • Also treiber sind alle aktuell, hab die von pakat bell geladen.also virus können wir definitiv ausschließen :)
    1. hatte ich noch nie einen.
    2. wurde sp3 und updatepack von winfuture aufgespielt, und avira, befor das ding ins internet kam.
    Wegen der karte, muss ich erst schauen wie sieh heißt, treiber sind keine INstaliert, sie ist aber schon jahre lang drinnen und hat noch nie Probleme gemacht.

  • jepp, ich habe smart laufen lassen, das sagt ok, temps sind auch io. jetzt habe ich das diagnosetool von seagate geladen und lasse einen langen test durchlaufen. danach kommt memtest. dann muss ich erst mal mit everest schauen, wie meine fehrnsehkarte heißt, die hab ich schon 2 jahre net mehr benutzt und ich find keine Infos über den Namen.

  • Hallo

    Ja mit HDTune habe ich das schon gehabt

    Nach einer Gegenprüfung mit einem Herstellertool sah das dann anders aus.

    Die Festplatte war defekt

    @ markusg

    Hörst du bei der Festplatte ungewöhnliche Geräusche entweder ein kratzen oder klacken bzw einen höheren Ton (surren) ?

    Prüf auch mal ob die Festplatte ungewöhnlich warm wird durch fühlen oder auch die Temperaturen der Hardware mit Everest Home Edition auslesen.

    EDIT :MARKUS WAR SELBER SCHNELLER :D
    mfg sea

    Viele Grüße von sea
    ----------------------------------------------------------------------
    SUPPORTER DES MONATS FEBRUAR 2010 von PCVISIT
    ----------------------------------------------------------------------
    meine Homepage: http://www.pcdietmar.de

  • Nein, nichts der gleichen. temps sind auch io. 45 grad hab den pc heut auch gesäubert, ich werd nachher auch noch die temps für graka und cpu messen, weis aber net ob das so ne gute idee ist, wenn ic das alles während des tests mache.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!