immer diese Bluescreens

ich hasse es .
hab heute schon wieder 3 bluescreens gehabt
einmal während dem zocken ,einmal während dem musikhören , und einmal war ich grad in emule drin .
erstens was kann ich dagegen machen ??
was kann man mit so einem bluescreen überhaupt anfangen (ausser sich zu ärgern!)
sind die bluescreens wech wenn ich dat xp neu installiere oder bringt das nix
nach dem bluescreen kommt fehlerbericht senden dann klicke ich senden, dann kommt ne HP von microsoft und sagt dass der prozzi irgendwie zu neu is fürs MOBO und ich das BIOS flashen soll ( MSI sagt dass ich net flashen muss!)
was soll ich jez tun weil langsam hab ich echt die schnauze voll von den bluescreens
thx

hab ich leider vergessen aber die bluescreens kommen bestimmt wieder
also das weiss ich auswendig steht was von interceptor.sys
kann das sein ?
aber ich mach auf jeden fall en foto
thx
absturzanalyse:
Alle Produkte
| Support
| Suche
| Microsoft.com Guide


Absturzanalyse | Firmen-Fehlerberichterstattung | Absturzanalyse weltweit
Die Browsersicherheitseinstellungen können die Sitefunktionalität beinträchtigen.

JavaScript und Cookies müssen aktiviert sein.
Es werden JavaScript und Cookies verwendet, um den Inhalt der Microsoft-Absturzanalyse richtig anzuzeigen.
Stellen Sie sicher, dass die Browsersicherheitseinstellungen die folgenden Anforderungen erfüllen, damit Sie den Fehlerbericht uploaden oder den Status eines anderen Berichts, den Sie bereits gesendet haben, überprüfen zu können:
JavaScript muss aktiviert sein.
Cookies müssen aktiviert sein.

Crash Cause Unknown: Consider BIOS Upgrade
Thank you for submitting an error report.
Problem Description
Microsoft is unable to determine what specifically caused the problem you reported.
Consider BIOS Upgrade
During the crash analysis, we noticed the BIOS version on this computer does not match the specifications for the processor that is installed on your computer. This can occur when a newer processor is installed on an older system board or older BIOS. Using a BIOS that does not support the installed processor can result in Windows system crashes. Please contact your computer manufacturer or motherboard manufacturer for an updated version of BIOS for your computer's processor.
Important: Upgrading the BIOS version may require moderate to advanced troubleshooting skills. If you are uncomfortable with performing these steps, you may want to consider consulting with paid technical support.
If your computer contains an Intel processor, you can use special utilities to identify your specific processor. Please click the following link for more information:
Intel Processor Identification Utility
List of BIOS Manufacturers
For a list of BIOS manufacturer websites, please see the following two Knowledge Base articles:
Websites von BIOS-Herstellern Teil 1 (A-Pi)
Websites von BIOS-Herstellern Teil 2 (Pr-Z)
Microsoft ist an Ihrer Meinung über die Windows-Fehlerberichterstattung interessiert, um Ihnen in Zukunft noch bessere Ergebnisse liefern zu können. Bitte nehmen Sie sich einen Augenblick Zeit, um an der folgenden anonymen Umfrage teilzunehmen.
An der Umfrage teilnehmen
Sie können diesen Fehlerbericht nachverfolgen. Klicken Sie dazu auf den entsprechenden Link. Sobald Lösungen zu diesem Problem gefunden werden, werden wir Sie darüber informieren.
Diesen Fehlerbericht nachverfolgen

© 2004 Microsoft Corporation. Alle Rechte vorbehalten. Rechtliche Hinweise | Datenschutzbestimmungen

hab mir irgendsoein debug tool von microsoft runtergeladen
des hat den bluescreen ausgewertet
ich hoffe des hilft euch weiter
thx
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090105-02.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 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c150
Debug session time: Thu Sep 1 12:59:57.484 2005 (GMT+2)
System Uptime: 0 days 0:00:45.183
*********************************************************************
* 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 1000007E, {c0000005, b7fbec92, f8b54c68, f8b54968}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image interceptor.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for interceptor.sys
*** ERROR: Module load completed but symbols could not be loaded for interceptor.sys
Probably caused by : interceptor.sys ( interceptor+8c92 )
Followup: MachineOwner
-

i9ch poste nochmal die anderen bluescreens wenns hilft !!
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090105-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 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c150
Debug session time: Thu Sep 1 12:57:55.609 2005 (GMT+2)
System Uptime: 0 days 2:24:06.318
*********************************************************************
* 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 D1, {1, 2, 0, f83b0c5e}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image PRISMA00.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for PRISMA00.sys
*** ERROR: Module load completed but symbols could not be loaded for PRISMA00.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Probably caused by : PRISMA00.sys ( PRISMA00+ac5e )
Followup: MachineOwner
-
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini082905-03.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 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c150
Debug session time: Mon Aug 29 19:57:42.000 2005 (GMT+2)
System Uptime: 0 days 0:00:39.695
*********************************************************************
* 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 1000007E, {c0000005, b7fb6c92, f8b4cc68, f8b4c968}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image interceptor.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for interceptor.sys
*** ERROR: Module load completed but symbols could not be loaded for interceptor.sys
Probably caused by : interceptor.sys ( interceptor+8c92 )
Followup: MachineOwner
-
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini082905-02.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 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c150
Debug session time: Mon Aug 29 15:55:57.250 2005 (GMT+2)
System Uptime: 0 days 0:00:38.960
*********************************************************************
* 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 1000007E, {c0000005, b7f5ec92, f8990c68, f8990968}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image interceptor.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for interceptor.sys
*** ERROR: Module load completed but symbols could not be loaded for interceptor.sys
Probably caused by : interceptor.sys ( interceptor+8c92 )
Followup: MachineOwner
-
sollte reichen
thx

ich schick sie dir per PM ok ?

Hm.,
die Nummer von Dir geht nicht. War’s vielleicht die falsche?
Hier eine Erklärung wie Du die richtige findest:

Hast Du auf Deinem Mainboard diese Version vom BIOS drauf?

doch die stimmt schon
aber irgendwie stimmt der [censored] link nicht
www.directupload.net/show/d/442/ssVAljn2.jpg

aaaaaaaaaaaaaaaaaaaah
doch jetzt
Informationsliste Wert
BIOS Eigenschaften
BIOS Typ Award
Award BIOS Typ Phoenix-Award BIOS v6.00PG
Award BIOS Nachricht W7012M7 V1.09 092903 15:35:00 MEDIONPC LN
Datum System BIOS 09/29/03
Datum Video BIOS 03/09/16

BIOS Hersteller
Firmenname Phoenix Technologies Ltd.
Produktinformation http://www.phoenix.com/en/products/default.htm
BIOS Aufrüstungen http://www.esupport.com/biosagent/ [...] fererid=40

Probleme und Hinweise
Hinweis Are you looking for a BIOS Upgrade? Contact eSupport Today!
thx

cpu-z kenn ich danke
(von den overclockingversuchen von thg )!
also des sagt version 6.00 PG
welche gefahr besteht eigentlcih beim BIOS flashen ??
thx

tosmos --> hab Dir eine PM geschickt