GizmoBoy
Lieutenant
- Registriert
- Okt. 2006
- Beiträge
- 927
Hey,
ich kann den Bluescreen reproduzieren aber das geht jetzt nicht weil am pc gearbeitet wird.
Es tritt jedesmal auf, sobald man sich per Remote Desktop auf den Pc einwählt.
Anbei ist der Dump aber damit kann ich leider nichts anfangen, hoffe mal ihr könnt mir helfen.
Danke.
ich kann den Bluescreen reproduzieren aber das geht jetzt nicht weil am pc gearbeitet wird.
Es tritt jedesmal auf, sobald man sich per Remote Desktop auf den Pc einwählt.
Anbei ist der Dump aber damit kann ich leider nichts anfangen, hoffe mal ihr könnt mir helfen.
Danke.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {f65869a0, 0, bf839d67, 1}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vSolidFillRect1+b0 )
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: f65869a0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf839d67, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: f65869a0
FAULTING_IP:
win32k!vSolidFillRect1+b0
bf839d67 2311 and edx,dword ptr [ecx]
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: devenv.exe
LAST_CONTROL_TRANSFER: from bf839b9b to bf839d67
STACK_TEXT:
b3cbae54 bf839b9b b3cbb080 f65869a0 f63b407c win32k!vSolidFillRect1+0xb0
b3cbafd4 bf833fa1 bf839c5d b3cbb080 00000000 win32k!vDIBSolidBlt+0x19b
b3cbb040 bf831472 e1843008 00000000 00000000 win32k!EngBitBlt+0xe1
b3cbb09c bf813300 00000000 e747aef8 00000000 win32k!ExtTextOutRect+0x1d1
b3cbb1e0 bf80c5b8 b3cbb318 7ffdd1e4 00000028 win32k!GreBatchTextOut+0xd0
b3cbb334 8054085d 00000143 0012c5cc 0012c5d4 win32k!NtGdiFlushUserBatch+0x11b
b3cbb43c bf805754 00000000 00000000 bc41aa30 nt!KiFastCallEntry+0xcd
b3cbb44c bf8057b2 00000001 bc41aa30 bf82acbb win32k!HANDLELOCK::vLockHandle+0x75
b3cbb45c bf82ad9e b3cbb4e8 b3cbb4c4 80545d20 win32k!HANDLELOCK::vUnlock+0x20
b3cbb490 bf805a6a e64f7a80 00000004 bf813b00 win32k!RGNOBJ::bSwap+0x70
b3cbb49c bf813b00 00000002 bf82ab37 bc6e93b0 win32k!REGION::vDeleteREGION+0x14
b3cbb4a4 bf82ab37 bc6e93b0 bc78b220 b3cbb7b8 win32k!RGNOBJ::vDeleteRGNOBJ+0xc
b3cbb4dc bf827fbf 19041aa3 00000000 03041bde win32k!GreCombineRgn+0x202
b3cbb778 bf80ee36 bc78b220 0000000f 00000000 win32k!CalcWindowVisRgn+0x2c0
b3cbb79c bf82b8a5 bc78b220 0000000f 00000000 win32k!xxxSendMessage+0x1b
b3cbb7c8 bf82b775 bc78b220 00000001 bc78b220 win32k!xxxUpdateWindow2+0x79
b3cbb7e8 bf83b93b bc78b220 00000001 b3cbb81c win32k!xxxInternalUpdateWindow+0x6f
b3cbb7f8 bf8aafef bc78b220 b3cbb854 0012f710 win32k!xxxUpdateWindow+0xf
b3cbb81c bf8aaf7c 00000001 a6012bc8 00000001 win32k!xxxPrintWindow+0x7a
b3cbb840 8054088c 000513e0 a6012bc8 00000001 win32k!NtUserPrintWindow+0x6e
b3cbb840 7c90e514 000513e0 a6012bc8 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
91010bef 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!vSolidFillRect1+b0
bf839d67 2311 and edx,dword ptr [ecx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!vSolidFillRect1+b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49900328
FAILURE_BUCKET_ID: 0x50_win32k!vSolidFillRect1+b0
BUCKET_ID: 0x50_win32k!vSolidFillRect1+b0
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: f65869a0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf839d67, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: f65869a0
FAULTING_IP:
win32k!vSolidFillRect1+b0
bf839d67 2311 and edx,dword ptr [ecx]
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: devenv.exe
LAST_CONTROL_TRANSFER: from bf839b9b to bf839d67
STACK_TEXT:
b3cbae54 bf839b9b b3cbb080 f65869a0 f63b407c win32k!vSolidFillRect1+0xb0
b3cbafd4 bf833fa1 bf839c5d b3cbb080 00000000 win32k!vDIBSolidBlt+0x19b
b3cbb040 bf831472 e1843008 00000000 00000000 win32k!EngBitBlt+0xe1
b3cbb09c bf813300 00000000 e747aef8 00000000 win32k!ExtTextOutRect+0x1d1
b3cbb1e0 bf80c5b8 b3cbb318 7ffdd1e4 00000028 win32k!GreBatchTextOut+0xd0
b3cbb334 8054085d 00000143 0012c5cc 0012c5d4 win32k!NtGdiFlushUserBatch+0x11b
b3cbb43c bf805754 00000000 00000000 bc41aa30 nt!KiFastCallEntry+0xcd
b3cbb44c bf8057b2 00000001 bc41aa30 bf82acbb win32k!HANDLELOCK::vLockHandle+0x75
b3cbb45c bf82ad9e b3cbb4e8 b3cbb4c4 80545d20 win32k!HANDLELOCK::vUnlock+0x20
b3cbb490 bf805a6a e64f7a80 00000004 bf813b00 win32k!RGNOBJ::bSwap+0x70
b3cbb49c bf813b00 00000002 bf82ab37 bc6e93b0 win32k!REGION::vDeleteREGION+0x14
b3cbb4a4 bf82ab37 bc6e93b0 bc78b220 b3cbb7b8 win32k!RGNOBJ::vDeleteRGNOBJ+0xc
b3cbb4dc bf827fbf 19041aa3 00000000 03041bde win32k!GreCombineRgn+0x202
b3cbb778 bf80ee36 bc78b220 0000000f 00000000 win32k!CalcWindowVisRgn+0x2c0
b3cbb79c bf82b8a5 bc78b220 0000000f 00000000 win32k!xxxSendMessage+0x1b
b3cbb7c8 bf82b775 bc78b220 00000001 bc78b220 win32k!xxxUpdateWindow2+0x79
b3cbb7e8 bf83b93b bc78b220 00000001 b3cbb81c win32k!xxxInternalUpdateWindow+0x6f
b3cbb7f8 bf8aafef bc78b220 b3cbb854 0012f710 win32k!xxxUpdateWindow+0xf
b3cbb81c bf8aaf7c 00000001 a6012bc8 00000001 win32k!xxxPrintWindow+0x7a
b3cbb840 8054088c 000513e0 a6012bc8 00000001 win32k!NtUserPrintWindow+0x6e
b3cbb840 7c90e514 000513e0 a6012bc8 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
91010bef 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!vSolidFillRect1+b0
bf839d67 2311 and edx,dword ptr [ecx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!vSolidFillRect1+b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49900328
FAILURE_BUCKET_ID: 0x50_win32k!vSolidFillRect1+b0
BUCKET_ID: 0x50_win32k!vSolidFillRect1+b0
Followup: MachineOwner
---------
