שלום לכולם.

אולי תוכלו לעזור לי. יש לי קריסות חוזרות ונשנות עם חלונות כחולים.

ביצעתי ניתוח קבצי DUMP כמו שהוסבר כאן, וזה מה שקיבלתי (ניתוח של 3 קבצים):

אני צריך לדעת מה זה אומר.

תודה מראש ושבת שלום.

17.03.2006

*******************************************************************************

* *

* 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: 80521b50, The address that the exception occurred at

Arg3: b64bf97c, Trap Frame

Arg4: 00000000

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

nt!ObReferenceObjectByPointer+e

80521b50 394808 cmp [eax+0x8],ecx

TRAP_FRAME: b64bf97c -- (.trap ffffffffb64bf97c)

ErrCode = 00000000

eax=00080a24 ebx=00080a3c ecx=865eeca0 edx=00000000 esi=84754b00 edi=00000000

eip=80521b50 esp=b64bf9f0 ebp=b64bf9f0 iopl=0 nv up ei pl nz ac po cy

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217

nt!ObReferenceObjectByPointer+0xe:

80521b50 394808 cmp [eax+0x8],ecx ds:0023:00080a2c=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 805afe2b to 80521b50

STACK_TEXT:

b64bf9f0 805afe2b 00080a3c 00000000 865eeca0 nt!ObReferenceObjectByPointer+0xe

b64bfaa8 ee3d0632 00080a3c 00000040 00000000 nt!ObOpenObjectByPointer+0x23

b64bfb00 ee3cf91a 848974e0 00012037 24b40901 afd!AfdQueryHandles+0x121

b64bfc50 80574643 848974e0 00000001 0234ff2c afd!AfdFastIoDeviceControl+0x9a

b64bfd00 8056d326 00000c84 000002ac 00000000 nt!IopXxxControlFile+0x261

b64bfd34 8053c808 00000c84 000002ac 00000000 nt!NtDeviceIoControlFile+0x2a

b64bfd34 7c90eb94 00000c84 000002ac 00000000 nt!KiFastCallEntry+0xf8

WARNING: Frame IP not in any known module. Following frames may be wrong.

0234ff30 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: kb

FOLLOWUP_IP:

afd!AfdQueryHandles+121

ee3d0632 8945e4 mov [ebp-0x1c],eax

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: afd!AfdQueryHandles+121

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107eb5

FAILURE_BUCKET_ID: 0x8E_afd!AfdQueryHandles+121

BUCKET_ID: 0x8E_afd!AfdQueryHandles+121

Followup: MachineOwner

---------

---------

24.03.2006

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

BAD_POOL_CALLER (c2)

The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.

Arguments:

Arg1: 00000003, type of pool violation the caller is guilty of.

Arg2: 847d235c

Arg3: 86061900

Arg4: 860618c0

Debugging Details:

------------------

Unable to load image NVENETFD.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for NVENETFD.sys

*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys

*** WARNING: Unable to verify timestamp for NVNRM.SYS

*** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS

BUGCHECK_STR: 0xc2_3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from ec276db7 to 804f8925

STACK_TEXT:

f78a6de8 ec276db7 000000c2 00000003 847d235c nt!KeBugCheckEx+0x1b

f78a6e14 ec2507cb 847d235c f78a6e64 ec250726 tcpip!MdpFree+0x143

f78a6e20 ec250726 847d235c 00000000 84786798 tcpip!FreeDGHeader+0x20

f78a6e64 ec24c68e 857ab7e0 847d235c 00000000 tcpip!DGSendComplete+0xa1

f78a6e9c ec24c81d 86115448 00786798 00000000 tcpip!IPSendComplete+0x126

f78a6ec0 f70e9c1c 8633de70 851b57d8 00000000 tcpip!ARPSendComplete+0xf6

f78a6ee4 f1239b69 86131ad0 84786798 00000000 NDIS!ndisMSendCompleteX+0x8d

f78a6f04 f70e9c1c 8632e348 01786798 00000000 psched!ClSendComplete+0x67

f78a6f28 ec7f497e 85558130 84786798 00000000 NDIS!ndisMSendCompleteX+0x8d

WARNING: Stack unwind information not available. Following frames may be wrong.

f78a6f98 f5b2b8cf 84786798 f5b39620 8625a53c NVENETFD+0x397e

f78a6fd0 80540d5d 8625a4ec 857f6708 00000000 NVNRM+0x88cf

f78a6ff4 80540a2a b9fb4d44 00000000 00000000 nt!KiRetireDpcList+0x46

f78a6ff8 b9fb4d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a

80540a2a 00000000 00000009 bb835675 00000128 0xb9fb4d44

STACK_COMMAND: kb

FOLLOWUP_IP:

NVENETFD+397e

ec7f497e ?? ???

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 9

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NVENETFD+397e

MODULE_NAME: NVENETFD

IMAGE_NAME: NVENETFD.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4253b862

FAILURE_BUCKET_ID: 0xc2_3_NVENETFD+397e

BUCKET_ID: 0xc2_3_NVENETFD+397e

Followup: MachineOwner

---------

24.03.06

*******************************************************************************

* *

* 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: bf820d5d, The address that the exception occurred at

Arg3: b66f9ca8, Trap Frame

Arg4: 00000000

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

win32k!GetDesktopView+8

bf820d5d 8b803c010000 mov eax,[eax+0x13c]

TRAP_FRAME: b66f9ca8 -- (.trap ffffffffb66f9ca8)

ErrCode = 00000000

eax=00000000 ebx=bc513438 ecx=0007045a edx=bc510000 esi=e3671860 edi=bc6d6960

eip=bf820d5d esp=b66f9d1c ebp=b66f9d1c iopl=0 nv up ei pl zr na po nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

win32k!GetDesktopView+0x8:

bf820d5d 8b803c010000 mov eax,[eax+0x13c] ds:0023:0000013c=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf801682 to bf820d5d

STACK_TEXT:

b66f9d1c bf801682 00000000 8615ab30 b66f9d64 win32k!GetDesktopView+0x8

b66f9d40 bf808628 06c3f9b4 b66f9d64 8053c808 win32k!ValidateHwnd+0x96

b66f9d4c 8053c808 0007045a 00008002 00000000 win32k!NtUserPostMessage+0x39

b66f9d4c 7c90eb94 0007045a 00008002 00000000 nt!KiFastCallEntry+0xf8

WARNING: Frame IP not in any known module. Following frames may be wrong.

06c3f9c4 00000000 00000000 00000000 00000000 0x7c90eb94

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

win32k!GetDesktopView+8

bf820d5d 8b803c010000 mov eax,[eax+0x13c]

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!GetDesktopView+8

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!GetDesktopView+8

BUCKET_ID: 0x8E_win32k!GetDesktopView+8

Followup: MachineOwner

---------

[attachment deleted by admin]

ניסיתי למצוא את זה בגוגל, אבל לא מצאתי שום דבר מועיל...

זה מה שניסית לעשות...

When you try to change the Hardware Acceleration setting in the Display tool in Control Panel from None to Full

http://support.microsoft.com/?kbid=330187

קודם כל, תודה.

אם אני אוריד את הhardware acceleration זה לא יפגע בביצועים של כרטיס המסך ?

יש לי Leadtek 6600GT PCIX.

תיכנס ללינק שצירפתי.

תקרא את המאמר (מההתחלה עד הסוף...)

אם ה- SYMPTOMS שלו זהים לאלה שלך אז תסתכל על ה- RESOLUTION שהם מציעים...

אם זה לא זה אז תמשיך לחפש פתרון