Bluescreen ohne Text, Event ID 6008

PerfiX

Little Overclocker

Registered: Oct 2006
Location: Hamburg
Posts: 76

05.11.2007 - 18:53

Hallo erstma,

ich hab ein ASUS X51R Noteebook mit Vista 32Bit.

Mitten im Betrieb oder regelmäßig, wenn ich große Dateien aus dem Internet lade kommt einfach ein Bluescreen ohne Text und der Rechner startet neu.

Der Eventlog von Vista sagt, dass ein Fehler mit der ID 6008 aufgetreten sei. Die ID scheint aber nur zu besagen, dass der Laptop einfach neu gestartet wurde wegen einem Fehler.

Hat einer von euch vll ne Ahnung, woran der Bluescreen liegen könnte?

tia

Sven

FrankEdwinWrigh

stuck on the outside

Registered: Nov 2002
Location: im 21. Jhdt.
Posts: 2507

06.11.2007 - 01:14

kann vieles sein. poste mal das dump aus x:\windows\minidump\

Mfg fEW

PerfiX

Little Overclocker

Registered: Oct 2006
Location: Hamburg
Posts: 76

06.11.2007 - 16:15

hier ist die dump vom letzen absturtz, ich kann damit nicht viel anfangen:

http://ags-server.de/wsftp_01/sven/Mini110507-02.dmp

tia

Bearbeitet von PerfiX am 06.11.2007, 16:17

FrankEdwinWrigh

stuck on the outside

Registered: Nov 2002
Location: im 21. Jhdt.
Posts: 2507

06.11.2007 - 18:47

[quote]
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Billie Joe Armstrong\Desktop\Mini110507-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 \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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ab0
Debug session time: Mon Nov 5 18:38:19.671 2007 (GMT+1)
System Uptime: 0 days 0:00:11.250
*********************************************************************
* 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 \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
Unable to load image \SystemRoot\System32\Drivers\Cdr4_xp.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Cdr4_xp.SYS
*** ERROR: Module load completed but symbols could not be loaded for Cdr4_xp.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8cafb05a, 8295d888, 8295d584}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : Cdr4_xp.SYS ( Cdr4_xp+305a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8cafb05a, The address that the exception occurred at
Arg3: 8295d888, Exception Record Address
Arg4: 8295d584, Context Record Address

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

MODULE_NAME: Cdr4_xp

FAULTING_MODULE: 81c00000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 431f4db7

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
Cdr4_xp+305a
8cafb05a f3ab rep stos dword ptr es:[edi]

EXCEPTION_RECORD: 8295d888 -- (.exr 0xffffffff8295d888)
ExceptionAddress: 8cafb05a (Cdr4_xp+0x0000305a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT: 8295d584 -- (.cxr 0xffffffff8295d584)
eax=00000000 ebx=8698f0e0 ecx=00000400 edx=00000100 esi=81c079ce edi=00000000
eip=8cafb05a esp=8295d950 ebp=8295d980 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
Cdr4_xp+0x305a:
8cafb05a f3ab rep stos dword ptr es:[edi] es:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8cafc3e7 to 8cafb05a

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8295d980 8cafc3e7 8687dd70 8698f028 88aa7000 Cdr4_xp+0x305a
8295d9b0 8cafc8b6 8687dd70 8594b030 8594bea8 Cdr4_xp+0x43e7
8295d9d0 81c0f3d1 8687dd70 00000000 8594bea8 Cdr4_xp+0x48b6
8295d9ec 81d5cb09 8678dce0 8cafc794 00000003 nt+0xf3d1
8295da14 81d588cd 8678dce0 8cafc794 00000001 nt+0x15cb09
8295daf0 81d5dd60 01000000 00000000 81d23d10 nt+0x1588cd
8295dcec 81c0f76a 84bc9a78 86749f78 8295dd38 nt+0x15dd60
8295dd44 81c6b50a 00000000 00000000 84bc52d8 nt+0xf76a
8295dd7c 81dafc5d 00000000 82956680 00000000 nt+0x6b50a
8295ddc0 81c9a196 81c6b40d 00000001 00000000 nt+0x1afc5d
00000000 00000000 00000000 00000000 00000000 nt+0x9a196

FOLLOWUP_IP:
Cdr4_xp+305a
8cafb05a f3ab rep stos dword ptr es:[edi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Cdr4_xp+305a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: Cdr4_xp.SYS

STACK_COMMAND: .cxr 0xffffffff8295d584 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
[/quote]

ist doch nicht so schwer zu finden (habs dir rot markiert)

deinstallier die roxio sony software, von der is das file .)
entweder ists nicht vista kompatibel oder es reicht eine neuinstallation (des programms)

Mfg fEW

PerfiX

Little Overclocker

Registered: Oct 2006
Location: Hamburg
Posts: 76

06.11.2007 - 23:16

jo danke dafür, hoffe es lag daran.

magst du mir noch verraten, mit welchem programm du die dump ausliest??

DANKE!!

Sven

that

Hoffnungsloser Optimist

Registered: Mar 2000
Location: MeidLing
Posts: 11338

06.11.2007 - 23:17

Zitat von PerfiX
magst du mir noch verraten, mit welchem programm du die dump ausliest??

Steht eh in der ersten Zeile.

Gibts AFAIK als "Debugging Tools for Windows" bei MS zum Download.

PerfiX

Little Overclocker

Registered: Oct 2006
Location: Hamburg
Posts: 76

06.11.2007 - 23:22

bin manchmal auch echt nen bissl dumm^^

danke für die hilfe, auf euch hier ist echt verlass!

FrankEdwinWrigh

stuck on the outside

Registered: Nov 2002
Location: im 21. Jhdt.
Posts: 2507

07.11.2007 - 13:07

genau .. http://www.microsoft.com/whdc/devto...ng/default.mspx

Mfg

PerfiX Little Overclocker Registered: Oct 2006 Location: Hamburg Posts: 76	05.11.2007 - 18:53 Hallo erstma, ich hab ein ASUS X51R Noteebook mit Vista 32Bit. Mitten im Betrieb oder regelmäßig, wenn ich große Dateien aus dem Internet lade kommt einfach ein Bluescreen ohne Text und der Rechner startet neu. Der Eventlog von Vista sagt, dass ein Fehler mit der ID 6008 aufgetreten sei. Die ID scheint aber nur zu besagen, dass der Laptop einfach neu gestartet wurde wegen einem Fehler. Hat einer von euch vll ne Ahnung, woran der Bluescreen liegen könnte? tia Sven
FrankEdwinWrigh stuck on the outside Registered: Nov 2002 Location: im 21. Jhdt. Posts: 2507	06.11.2007 - 01:14 kann vieles sein. poste mal das dump aus x:\windows\minidump\ Mfg fEW
PerfiX Little Overclocker Registered: Oct 2006 Location: Hamburg Posts: 76	06.11.2007 - 16:15 hier ist die dump vom letzen absturtz, ich kann damit nicht viel anfangen: http://ags-server.de/wsftp_01/sven/Mini110507-02.dmp tia Bearbeitet von PerfiX am 06.11.2007, 16:17
FrankEdwinWrigh stuck on the outside Registered: Nov 2002 Location: im 21. Jhdt. Posts: 2507	06.11.2007 - 18:47 [quote] Microsoft (R) Windows Debugger Version 6.8.0004.0 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Billie Joe Armstrong\Desktop\Mini110507-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 \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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ab0 Debug session time: Mon Nov 5 18:38:19.671 2007 (GMT+1) System Uptime: 0 days 0:00:11.250 ******************************************************************* * 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 \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 Unable to load image \SystemRoot\System32\Drivers\Cdr4_xp.SYS, Win32 error 0n2 * WARNING: Unable to verify timestamp for Cdr4_xp.SYS * ERROR: Module load completed but symbols could not be loaded for Cdr4_xp.SYS ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 8cafb05a, 8295d888, 8295d584} * 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 * * * ********************************************************************* ******************************************************************* * 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 : Cdr4_xp.SYS ( Cdr4_xp+305a ) Followup: MachineOwner --------- 1: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 8cafb05a, The address that the exception occurred at Arg3: 8295d888, Exception Record Address Arg4: 8295d584, Context Record Address 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 * * * ********************************************************************* ******************************************************************* * 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+ * ********************************************************************* MODULE_NAME: Cdr4_xp FAULTING_MODULE: 81c00000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 431f4db7 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden. FAULTING_IP: Cdr4_xp+305a 8cafb05a f3ab rep stos dword ptr es:[edi] EXCEPTION_RECORD: 8295d888 -- (.exr 0xffffffff8295d888) ExceptionAddress: 8cafb05a (Cdr4_xp+0x0000305a) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000001 Parameter[1]: 00000000 Attempt to write to address 00000000 CONTEXT: 8295d584 -- (.cxr 0xffffffff8295d584) eax=00000000 ebx=8698f0e0 ecx=00000400 edx=00000100 esi=81c079ce edi=00000000 eip=8cafb05a esp=8295d950 ebp=8295d980 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246 Cdr4_xp+0x305a: 8cafb05a f3ab rep stos dword ptr es:[edi] es:0023:00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 8cafc3e7 to 8cafb05a STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8295d980 8cafc3e7 8687dd70 8698f028 88aa7000 Cdr4_xp+0x305a 8295d9b0 8cafc8b6 8687dd70 8594b030 8594bea8 Cdr4_xp+0x43e7 8295d9d0 81c0f3d1 8687dd70 00000000 8594bea8 Cdr4_xp+0x48b6 8295d9ec 81d5cb09 8678dce0 8cafc794 00000003 nt+0xf3d1 8295da14 81d588cd 8678dce0 8cafc794 00000001 nt+0x15cb09 8295daf0 81d5dd60 01000000 00000000 81d23d10 nt+0x1588cd 8295dcec 81c0f76a 84bc9a78 86749f78 8295dd38 nt+0x15dd60 8295dd44 81c6b50a 00000000 00000000 84bc52d8 nt+0xf76a 8295dd7c 81dafc5d 00000000 82956680 00000000 nt+0x6b50a 8295ddc0 81c9a196 81c6b40d 00000001 00000000 nt+0x1afc5d 00000000 00000000 00000000 00000000 00000000 nt+0x9a196 FOLLOWUP_IP: Cdr4_xp+305a 8cafb05a f3ab rep stos dword ptr es:[edi] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Cdr4_xp+305a FOLLOWUP_NAME: MachineOwner IMAGE_NAME: Cdr4_xp.SYS STACK_COMMAND: .cxr 0xffffffff8295d584 ; kb BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- [/quote] ist doch nicht so schwer zu finden (habs dir rot markiert) deinstallier die roxio sony software, von der is das file .) entweder ists nicht vista kompatibel oder es reicht eine neuinstallation (des programms) Mfg fEW
PerfiX Little Overclocker Registered: Oct 2006 Location: Hamburg Posts: 76	06.11.2007 - 23:16 jo danke dafür, hoffe es lag daran. magst du mir noch verraten, mit welchem programm du die dump ausliest?? DANKE!! Sven
that Hoffnungsloser Optimist Registered: Mar 2000 Location: MeidLing Posts: 11338	06.11.2007 - 23:17 Zitat von PerfiX magst du mir noch verraten, mit welchem programm du die dump ausliest?? Steht eh in der ersten Zeile. Gibts AFAIK als "Debugging Tools for Windows" bei MS zum Download.
PerfiX Little Overclocker Registered: Oct 2006 Location: Hamburg Posts: 76	06.11.2007 - 23:22 bin manchmal auch echt nen bissl dumm^^ danke für die hilfe, auf euch hier ist echt verlass!
FrankEdwinWrigh stuck on the outside Registered: Nov 2002 Location: im 21. Jhdt. Posts: 2507	07.11.2007 - 13:07 genau .. http://www.microsoft.com/whdc/devto...ng/default.mspx Mfg

Bluescreen ohne Text, Event ID 6008

Forum Index > Software > Windows

PerfiX

FrankEdwinWrigh

PerfiX

FrankEdwinWrigh

PerfiX

that

PerfiX

FrankEdwinWrigh