Problem Cdrom.sys (minidump)

[Mlodyx]

Od jakiegoś miesiąca mam problem tego typu, że resetuje mi się komputer - początkowo następowało to przy włożeniu płyty do cdromu bądź zamontowaniu obrazu Daemonem natomiast ostatnio dzieje się to bez niczego poprostu następuje reset...

 

Przy pomocy WinDbg (Minidump) sprawdziłem i otrzymałem taki log:

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini021509-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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.exeWindows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTS PersonalMachine Name:Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0Debug session time: Sun Feb 15 12:59:40.525 2009 (GMT+1)System Uptime: 0 days 2:08:59.606********************************************************************** 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.exeLoading Kernel Symbols....................................................................................................................................................Loading User SymbolsLoading unloaded module list...............*** WARNING: Unable to verify timestamp for cdrom.sys*** ERROR: Module load completed but symbols could not be loaded for cdrom.sysUnable to load image CLASSPNP.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for CLASSPNP.SYS*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 100000D1, {f76f3036, 2, 0, f76f3036}***** Kernel symbols are WRONG. Please fix symbols to do analysis.*** 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 InCDPass.sys*** ERROR: Module load completed but symbols could not be loaded for InCDPass.sys*** WARNING: Unable to verify timestamp for InCDRm.sys*** ERROR: Module load completed but symbols could not be loaded for InCDRm.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									  ******																   ********************************************************************************************************************************************************																   ******																   ******	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 Cdfs.SYS*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS*** WARNING: Unable to verify timestamp for mfehidk.sys*** ERROR: Module load completed but symbols could not be loaded for mfehidk.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 : cdrom.sys ( cdrom+c036 )Followup: MachineOwner---------

a następnie wykonałem skorzystałem z Microsoft Symbol Server

(dodałem SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols)

i otrzymałem

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini021509-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 2600.xpsp_sp3_gdr.080814-1236Machine Name:Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0Debug session time: Sun Feb 15 12:59:40.525 2009 (GMT+1)System Uptime: 0 days 2:08:59.606Loading Kernel Symbols....................................................................................................................................................Loading User SymbolsLoading unloaded module list...............********************************************************************************																			 **						Bugcheck Analysis									**																			 ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 100000D1, {f76f3036, 2, 0, f76f3036}*** WARNING: Unable to verify timestamp for InCDPass.sys*** ERROR: Module load completed but symbols could not be loaded for InCDPass.sys*** WARNING: Unable to verify timestamp for InCDRm.sys*** ERROR: Module load completed but symbols could not be loaded for InCDRm.sys*** WARNING: Unable to verify timestamp for mfehidk.sys*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sysProbably caused by : cdrom.sys ( cdrom!CdRomReadWriteVerification+0 )Followup: MachineOwner---------

- czy ktoś mógłby poradzić jak pozbyć się tego błędu ?

 

Dziękuję, pozdrawiam.

Edytowane 15 Lutego 2009 przez Mlodyx

[v1ru5]

Zacząłbym od pozbycia się InCD (uninstall lub zamknięcie odpowiedniego procesu).