Startet wider nicht; diesmal GraKa!?

[RedEagle]

Hi

Ich hatte vor einiger zeit (letzte Woche?) das Problem, das ich beim booten immer ein BSOD hatte, fehler waren einige Komponenten des CD-laufwerks-treiber. Diese habe ich deaktiviert und alles ging soweit (außer das laufwerk)

jetzt habe ich gestern das Problem gehabt, das ich ein "PF in non pages area" beim booten bekam. Heute kann ich wieder booten (keine ahnung warum es jetzt geht).
Allerdings kann meine Grafikkarte nicht gestartet werden.
Zudem kann ich den PC nicht mehr in den Standby-modus schalten (es handelt sich um eine OnBoard-GraKa)

Vorab:
OS möchte ich NICHT neu installieren,
Neuen GraKa-Treiber halte ich für weniger sinnvoll, da das Problem wohl nicht die GraKa ist, da selbiges Problem (bzw eins, mit selben ausmaßen) auch von den CD-Laufwerk veruhrsacht wurde.

Dieses Komische verhalten muss doch einen Grund haben?? Welchen?

ps.: windbg-ausgabe:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini061007-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 2
*** 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Sun Jun 10 11:15:57.625 2007 (GMT+2)
System Uptime: 0 days 0:00:14.203
*********************************************************************
* 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 2
*** 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 unloaded module list
.....
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {f7b8c000, 1, 80527360, 0}

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


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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f7b8c000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 80527360, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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

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


MODULE_NAME:  nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9c

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
 f7b8c000 

FAULTING_IP: 
nt+50360
80527360 8902             mov     [edx],eax

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from 00000000 to 80527360

STACK_TEXT:  
83f8ba38 00000000 0000000f 00000001 00000007 nt+0x50360


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID:  WRONG_SYMBOLS

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