Błąd 0000009c Przy Próbie Odczytu Dvd/rw

[Szib]

Mam następujący problem przy próbie odczytu plików z CD system się wiesza wywala niebieski ekran z zrzucaniem pamięci i kodem błędu:

 

0000009c, parametr 1 00000004, parametr 2 8053f0f0, parametr 3 b2000000, parametr 4 00070f0f.

 

Czy ktoś się oriętuje co to za błąd?

[Nyny]

Moze troche wiecej szczegołów podaj bo sam numer bledu nic nie mowi. Podaj jeszcze jaki komunikat wyskakuje podczas blue screena.

Wykonaj podstawowe czynnosci w takim przypadku:

-sprawdzic napiecia na zasilaczu miernikiem

-przeskanowac pamieci memtestem

-przeinstalowac lub zmienic sterowniki do karty graficznej, plyty glownej

-uruchomic komputer z podstawowymi podzespolami bez zbednych kart rozszerzen i kosci pamieci

-odkrecic sprzet jesli byl podkrecany, zmienszyc timingi dla pamieci

-przeskanowac kompa programami antywirusowy

-sprawdzic temperatury procesora, grafy chipsetu itp.

-przywrocic domysle ustawienia biosu

[Szib]

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini052405-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 \WINDOWS\system32\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) UP Free x86 compatible

Product: WinNt

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Tue May 24 14:24:12.000 2005 (GMT+2)

System Uptime: 0 days 0:38:53.588

*********************************************************************

* 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 \WINDOWS\system32\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 9C, {4, 8053f0f0, b2000000, 70f0f}

 

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

 

 

Followup: MachineOwner

---------

 

kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available (For example Intel

Pentium), the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel

Pentium Pro), the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

Arguments:

Arg1: 00000004

Arg2: 8053f0f0

Arg3: b2000000

Arg4: 00070f0f

 

Debugging Details:

------------------

 

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

 

 

MODULE_NAME: nt

 

FAULTING_MODULE: 804d4000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c

 

BUGCHECK_STR: 0x9C_IA32_AuthenticAMD

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

LAST_CONTROL_TRANSFER: from 0000009c to 805266db

 

STACK_TEXT:

8053f0ac 0000009c 00000004 8053f0f0 b2000000 nt+0x526db

 

 

STACK_COMMAND: .bugcheck ; kb

 

FOLLOWUP_NAME: MachineOwner

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

 

To analiza miniDump

[Nyny]

Z tego komunikat niestety nie odczytam nic wiecej jak ten nieszczesny numer bledu. Podczas blue screena powinienes miec jeszcze nazwe bledu ktory wystapil.

Zastosuj sie tez do czynnosci ktore napisalem