BSOD: BugCheck 100000C5, eamon.sys, SupServ.exe

[cosik_ktosik]

Nie zaprzeczam że stare i tamto może pomóc ale i z dyskiem coś jest nie tak.

(C5) Current Pending Sector 100 100 0 3 warning

Przeskanuj także dysk na bad sektory (zakładka Error Scan), z wyłączoną opcją QuickScan lub jeśli to możliwe w MHDD. Na koniec zrób zdjęcie lub odczytaj i spisz prawą kolumnę i ją podaj.

[XMan]

Ja na sprawdzaniu dysku jestem
Nigdy nie miałem takiego problemu w życiu, widocznie mam szczęście
Tak więc posłuchaj rady którą podał p/w cosik_ktosik.
Mojej oraz innych również

Pozdrawiam.

[Mariosz]

Tak to wygląda.

+ kolejny bluescreen

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini071710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sat Jul 17 11:02:11.859 2010 (GMT+2)
System Uptime: 0 days 1:42:52.428
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {8ba0d2ef, 1, b8c0912e, 0}


Could not read faulting driver name
Probably caused by : kmixer.sys ( kmixer!SuperCopy+19e )

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

1: 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: 8ba0d2ef, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: b8c0912e, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  8ba0d2ef

FAULTING_IP:
kmixer!SuperCopy+19e
b8c0912e 0f7f10          movq    mmword ptr [eax],mm2

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from b8bfb30a to b8c0912e

STACK_TEXT: 
b9836ccc b8bfb30a 00000002 000001b9 000001b9 kmixer!SuperCopy+0x19e
b9836d50 b8be9e9d 820f3728 81b688d0 820f37e0 kmixer!MixOneBuff+0x6fa
b9836d84 b8bea2a7 000f3728 00000000 00000000 kmixer!MxWorker+0x1bd
b9836dac 80576316 820f3728 00000000 00000000 kmixer!MxPrivateWorkerThread+0xb7
b9836ddc 804ec6f9 b8bea1f0 820f3728 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
kmixer!SuperCopy+19e
b8c0912e 0f7f10          movq    mmword ptr [eax],mm2

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kmixer!SuperCopy+19e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kmixer

IMAGE_NAME:  kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254b3

FAILURE_BUCKET_ID:  0x50_kmixer!SuperCopy+19e

BUCKET_ID:  0x50_kmixer!SuperCopy+19e

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

[djkamil09061991]

Chyba sterownik dzwięku. Może spróbuj zaisnstalować inne.

[cosik_ktosik]

Są bad sektory. Można próbować remapować ale to wiąże się z czyszczeniem dysku (całkowitym), więc nie wiem czy możesz to zrobić. Jeśli dysk coś próbuje czytać z tego obszaru a akurat jest tam coś ważnego to bluescreen murowany.

[Mariosz]

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini071910-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Jul 19 11:25:06.750 2010 (GMT+2)
System Uptime: 0 days 1:31:02.458
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8056fb1c, b9ed8b0c, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpAllocateHandleTableEntry+165 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 8056fb1c, The address that the exception occurred at
Arg3: b9ed8b0c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
nt!ExpAllocateHandleTableEntry+165
8056fb1c 8b4804          mov     ecx,dword ptr [eax+4]

TRAP_FRAME:  b9ed8b0c -- (.trap 0xffffffffb9ed8b0c)
ErrCode = 00000000
eax=00000000 ebx=001f0001 ecx=00000000 edx=e31ba630 esi=e31ba60c edi=81ecf2b8
eip=8056fb1c esp=b9ed8b80 ebp=b9ed8b9c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!ExpAllocateHandleTableEntry+0x165:
8056fb1c 8b4804          mov     ecx,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  firefox.exe

LAST_CONTROL_TRANSFER:  from 8056fb94 to 8056fb1c

STACK_TEXT: 
b9ed8b9c 8056fb94 e31ba600 b9ed8bb4 001f0003 nt!ExpAllocateHandleTableEntry+0x165
b9ed8bb8 805742f0 e31ba600 b9ed8bec 00000000 nt!ExCreateHandle+0x19
b9ed8bfc 805744b9 81ffc9a8 001f0003 00000001 nt!ObpCreateUnnamedHandle+0x11a
b9ed8cf0 80574594 81ffc9a8 00000000 001f0003 nt!ObInsertObject+0xb0
b9ed8d48 804dd99f 0dbceff4 001f0003 00000000 nt!NtCreateEvent+0xc2
b9ed8d48 7c90e514 0dbceff4 001f0003 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0dbceff8 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExpAllocateHandleTableEntry+165
8056fb1c 8b4804          mov     ecx,dword ptr [eax+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpAllocateHandleTableEntry+165

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7aa6e6

FAILURE_BUCKET_ID:  0x8E_nt!ExpAllocateHandleTableEntry+165

BUCKET_ID:  0x8E_nt!ExpAllocateHandleTableEntry+165

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



BŁAGAM POMÓŻCIE... To już się staje na prawdę wkurzające a nie mam pomysłów co z tym zrobić ;/

[cosik_ktosik]

Pytałem się o możliwość czyszczenia dysku, czy byłbyś w stanie to zrobić? Stosowną instrukcję jak tego dokonać, przedstawię.