BSOD Probably caused by : ctoss2k.sys

Wszelkie problemy komputerowe, których nie można jednoznacznie sklasyfikować do wybranego działu
lapaka

Użytkownik
Posty: 2
Rejestracja: 03 lip 2011, 11:48

BSOD Probably caused by : ctoss2k.sys

Post03 lip 2011, 12:02

Witam,

Ostatnio co jakiś czas dostaję Blue Screen'a, zdarza się to głównie przy długiej pracy komputera. Jedyne co ostatnio zmieniałem w komputerze to karta dźwiękowa. Z góry dziękuję za pomoc.

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`03445650
Debug session time: Sun Jul  3 10:55:53.109 2011 (UTC + 2:00)
System Uptime: 0 days 15:22:19.456
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff81bd1000, 0, fffff8000329c358, 5}

Unable to load image \SystemRoot\system32\drivers\ctoss2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ctoss2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys

Could not read faulting driver name
Probably caused by : ctoss2k.sys ( ctoss2k+5dde )

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

0: 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: ffffffff81bd1000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000329c358, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034af100
 ffffffff81bd1000

FAULTING_IP:
nt!MmProbeAndLockPages+118
fffff800`0329c358 410fb601        movzx   eax,byte ptr [r9]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dndclient.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a451530 -- (.trap 0xfffff8800a451530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000010e rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000010e rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329c358 rsp=fffff8800a4516c0 rbp=fffff8800a451850
 r8=fffffa8005980040  r9=ffffffff81bd1000 r10=000000000000010e
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
nt!MmProbeAndLockPages+0x118:
fffff800`0329c358 410fb601        movzx   eax,byte ptr [r9] ds:e260:ffffffff`81bd1000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000322a3cf to fffff8000327fd00

STACK_TEXT: 
fffff880`0a4513c8 fffff800`0322a3cf : 00000000`00000050 ffffffff`81bd1000 00000000`00000000 fffff880`0a451530 : nt!KeBugCheckEx
fffff880`0a4513d0 fffff800`0327de2e : 00000000`00000000 ffffffff`81bd1000 fffffa80`0638c400 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`0a451530 fffff800`0329c358 : 00000000`00000000 fffff800`03407348 00000000`00000000 00000000`00000801 : nt!KiPageFault+0x16e
fffff880`0a4516c0 fffff880`02f9fdde : fffffa80`05980010 fffff800`03291800 00000000`00000002 ffffffff`81bd1000 : nt!MmProbeAndLockPages+0x118
fffff880`0a4517d0 fffffa80`05980010 : fffff800`03291800 00000000`00000002 ffffffff`81bd1000 00000000`00000000 : ctoss2k+0x5dde
fffff880`0a4517d8 fffff800`03291800 : 00000000`00000002 ffffffff`81bd1000 00000000`00000000 fffffa80`09457ae0 : 0xfffffa80`05980010
fffff880`0a4517e0 fffffa80`08c7e3d0 : fffff880`0a451840 00000000`000007ff 00000000`ffffffff 00000000`00000003 : nt!IopFreeIrp+0x30
fffff880`0a451820 fffff880`0a451840 : 00000000`000007ff 00000000`ffffffff 00000000`00000003 fffff801`00000000 : 0xfffffa80`08c7e3d0
fffff880`0a451828 00000000`000007ff : 00000000`ffffffff 00000000`00000003 fffff801`00000000 fffff880`0a451830 : 0xfffff880`0a451840
fffff880`0a451830 00000000`ffffffff : 00000000`00000003 fffff801`00000000 fffff880`0a451830 ffff0000`0f7caf01 : 0x7ff
fffff880`0a451838 00000000`00000003 : fffff801`00000000 fffff880`0a451830 ffff0000`0f7caf01 ffff0000`0f7caf18 : 0xffffffff
fffff880`0a451840 fffff801`00000000 : fffff880`0a451830 ffff0000`0f7caf01 ffff0000`0f7caf18 fffffa80`067eae00 : 0x3
fffff880`0a451848 fffff880`0a451830 : ffff0000`0f7caf01 ffff0000`0f7caf18 fffffa80`067eae00 00000000`00000001 : 0xfffff801`00000000
fffff880`0a451850 ffff0000`0f7caf01 : ffff0000`0f7caf18 fffffa80`067eae00 00000000`00000001 fffff880`0a451a18 : 0xfffff880`0a451830
fffff880`0a451858 ffff0000`0f7caf18 : fffffa80`067eae00 00000000`00000001 fffff880`0a451a18 00000000`00000000 : 0xffff0000`0f7caf01
fffff880`0a451860 fffffa80`067eae00 : 00000000`00000001 fffff880`0a451a18 00000000`00000000 fffffa80`08c7e340 : 0xffff0000`0f7caf18
fffff880`0a451868 00000000`00000001 : fffff880`0a451a18 00000000`00000000 fffffa80`08c7e340 fffff880`0536813c : 0xfffffa80`067eae00
fffff880`0a451870 fffff880`0a451a18 : 00000000`00000000 fffffa80`08c7e340 fffff880`0536813c 00000000`00000027 : 0x1
fffff880`0a451878 00000000`00000000 : fffffa80`08c7e340 fffff880`0536813c 00000000`00000027 fffffa80`08d1de60 : 0xfffff880`0a451a18


STACK_COMMAND:  kb

FOLLOWUP_IP:
ctoss2k+5dde
fffff880`02f9fdde ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ctoss2k+5dde

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ctoss2k

IMAGE_NAME:  ctoss2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5b6f4d

FAILURE_BUCKET_ID:  X64_0x50_ctoss2k+5dde

BUCKET_ID:  X64_0x50_ctoss2k+5dde

Followup: MachineOwner

Awatar użytkownika
djkamil09061991

Globalny Moderator
Posty: 8250
Rejestracja: 18 lut 2009, 11:54
Lokalizacja: Wrocław
Kontaktowanie:

BSOD Probably caused by : ctoss2k.sys

Post03 lip 2011, 12:29

Jest to bsod spowodowany kartą creative, tak więc przeinstaluj sterowniki od niej

lapaka

Użytkownik
Posty: 2
Rejestracja: 03 lip 2011, 11:48

BSOD Probably caused by : ctoss2k.sys

Post03 lip 2011, 14:35

Dzięki za pomoc, przeinstalowałem sterowniki, i jak na razie żadnych BSOD :D



  • Reklama

Wróć do „Problemy”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 10 gości