To nie jest kod błędu (82C910AF) tylko jeden z parametrów wyjściowych (tzw argument) mogących bardziej precyzyjnie namierzyć problem. Kod błędu masz u samej góry BCCode: a oznacza zapis 0xc0000000A - format zapisu 0xc i kolejne 8 znaków.
Cytat:Proces lub sterownik trybu jądra próbował uzyskać dostęp do obszaru pamięci bez
autoryzacji. Ten błąd Stop zazwyczaj powodowany jest przez uszkodzone lub niekompatybilne urządzenie albo oprogramowanie. Nazwa będącego sprawcą sterownika urządzenia często ukazuje się w komunikacie o błędzie Stop i może dostarczyć ważnych wskazówek do rozwiązania problemu.
82C910AF - adres obszaru pamięci
V0700Vid.sys - sterownik który naruszył autoryzację.
Po mojemu w którymś momencie sterownik zwolnił zasób pamięci. Otrzymała go np gra. W momencie odpięcia i podpięcia sterownik coś porzchanił o próbował ponownie dostać się (zapisać coś lub odczytać) do tego samego segmentu pamięci co wcześniej.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\051812-14492-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0x82c1a000 PsLoadedModuleList = 0x82d634d0
Debug session time: Fri May 18 22: 14: 27.186 2012 (UTC + 2: 00)
System Uptime: 0 days 13: 57: 42.824
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82c910af}
Unable to load image \SystemRoot\system32\DRIVERS\V0700Vid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for V0700Vid.sys
*** ERROR: Module load completed but symbols could not be loaded for V0700Vid.sys
Probably caused by : V0700Vid.sys ( V0700Vid+44511 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82c910af, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d83848
Unable to read MiSystemVaType memory at 82d62e20
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeWaitForSingleObject+373
82c910af 8939 mov dword ptr [ecx],edi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 8ad2b9c4 -- (.trap 0xffffffff8ad2b9c4)
ErrCode = 00000002
eax=85913f1c ebx=85913f14 ecx=00000000 edx=00000000 esi=84cbc020 edi=84cbc0e0
eip=82c910af esp=8ad2ba38 ebp=8ad2ba98 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!KeWaitForSingleObject+0x373:
82c910af 8939 mov dword ptr [ecx],edi ds: 0023: 00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 82c910af to 82c5b65b
STACK_TEXT:
8ad2b9c4 82c910af badb0d00 00000000 82cade16 nt!KiTrap0E+0x2cf
8ad2ba98 9d3f0511 85913f14 00000000 00000000 nt!KeWaitForSingleObject+0x373
WARNING: Stack unwind information not available. Following frames may be wrong.
8ad2bac0 9d3edc0f 877d2c54 84db4900 8ad2baf0 V0700Vid+0x44511
8ad2bad0 90ea2438 877d2c54 84db4900 84db4a6c V0700Vid+0x41c0f
8ad2baf0 82c515be 85114020 84db4900 8ad2bb8c ks!CKsDevice: DispatchPnp+0x1ca
8ad2bb08 82df3049 85108c68 878e4b48 85108c68 nt!IofCallDriver+0x63
8ad2bb38 82edfd0f 85108c68 00000000 878e4b48 nt!IopSynchronousCall+0xc2
8ad2bb90 82cf62c2 85108c68 00000002 89bb1340 nt!IopRemoveDevice+0xd4
8ad2bbbc 82ed7a3d 0000000a 89bb1340 00000000 nt!PnpRemoveLockedDeviceNode+0x16c
8ad2bbd0 82ed7cf3 00000002 0000000a 00000000 nt!PnpDeleteLockedDeviceNode+0x2d
8ad2bc04 82edb6e7 85108c68 89bb1340 00000002 nt!PnpDeleteLockedDeviceNodes+0x4c
8ad2bcc4 82dcb34e 8ad2bcf4 00000000 a66dc108 nt!PnpProcessQueryRemoveAndEject+0x946
8ad2bcdc 82dd944e 00000000 8510e658 84cbc020 nt!PnpProcessTargetDeviceEvent+0x38
8ad2bd00 82c97a6b 8510e658 00000000 84cbc020 nt!PnpDeviceEventWorker+0x216
8ad2bd50 82e23056 00000001 a3d4cbd4 00000000 nt!ExpWorkerThread+0x10d
8ad2bd90 82ccb1a9 82c9795e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
V0700Vid+44511
9d3f0511 ? ?
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: V0700Vid+44511
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: V0700Vid
IMAGE_NAME: V0700Vid.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e67017a
FAILURE_BUCKET_ID: 0xA_V0700Vid+44511
BUCKET_ID: 0xA_V0700Vid+44511
Followup: MachineOwner
---------
Post: #2![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
Podziękowania od:
