po załadowaniu pulpitu Windows mam blue screena. Raport z Windbg:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121213-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
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Dec 12 12:16:08.796 2013 (GMT+1)
System Uptime: 0 days 0:00:38.500
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
......
Unable to load image RtHDMI.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtHDMI.sys
*** ERROR: Module load completed but symbols could not be loaded for RtHDMI.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, ae3c322a, f7932ae0, f79327dc}
Probably caused by : portcls.sys ( portcls!PcRegisterSubdevice+77 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ae3c322a, The address that the exception occurred at
Arg3: f7932ae0, Exception Record Address
Arg4: f79327dc, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwołuje się do pamięci pod adresem "0x%08lx". Pamięć nie może być "%s".
FAULTING_IP:
portcls!PcRegisterSubdevice+77
ae3c322a 8b4004 mov eax,dword ptr [eax+4]
EXCEPTION_RECORD: f7932ae0 -- (.exr 0xfffffffff7932ae0)
ExceptionAddress: ae3c322a (portcls!PcRegisterSubdevice+0x00000077)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004
CONTEXT: f79327dc -- (.cxr 0xfffffffff79327dc)
eax=00000000 ebx=8a362738 ecx=f7932bc8 edx=f7932bc8 esi=89ee9030 edi=00000000
eip=ae3c322a esp=f7932ba8 ebp=f7932bd0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
portcls!PcRegisterSubdevice+0x77:
ae3c322a 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwołuje się do pamięci pod adresem "0x%08lx". Pamięć nie może być "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000004
READ_ADDRESS: 00000004
FOLLOWUP_IP:
portcls!PcRegisterSubdevice+77
ae3c322a 8b4004 mov eax,dword ptr [eax+4]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from ae73a5d5 to ae3c322a
STACK_TEXT:
f7932bd0 ae73a5d5 00000000 ae577744 89fa24d8 portcls!PcRegisterSubdevice+0x77
WARNING: Stack unwind information not available. Following frames may be wrong.
f7932c84 ae7446ca 8a026348 8a4cf8c8 00000000 RtHDMI+0x3675d5
f7932ca8 ae74354a 8a362708 f7932d8c 8a4cf8c8 RtHDMI+0x3716ca
f7932cd0 ae5764a4 8a365008 00000001 00000005 RtHDMI+0x37054a
f7932d90 ae3d554e 8a403530 00000000 00000000 RtHDMI+0x1a34a4
f7932dac 805cff64 8a4b1250 00000000 00000000 RtHDMI+0x254e
f7932ddc 805460de ae3d54f2 8a2427d8 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: portcls!PcRegisterSubdevice+77
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: portcls
IMAGE_NAME: portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47e39d81
STACK_COMMAND: .cxr 0xfffffffff79327dc ; kb
FAILURE_BUCKET_ID: 0x7E_portcls!PcRegisterSubdevice+77
BUCKET_ID: 0x7E_portcls!PcRegisterSubdevice+77
Followup: MachineOwner
---------