Mozzad

Skulle bare si som tidligere ansatt som fikk ny jobb et annet sted, er det mye mer dritt en hva artikkelen sier. Det er ikke bare IT-ledelsen, men også fagforeningen som har vært ubrukelige her.

Jeg har et Problem med min nye pc. når jeg Sitter og Spiller WoW så får jeg en blueScreen. jeg istallerte derfor Windbg og dette er hva jeg fikk som Text

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 7faacd70, af46c81c, 0}

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

Probably caused by : hardware

Followup: MachineOwner

---------

*** Possible invalid call from bfaf7743 ( nv4_disp+0xe3743 )

*** Expected target bfaacd70 ( nv4_disp+0x98d70 )

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)

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

Arg3: af46c81c, Trap Frame

Arg4: 00000000

Debugging Details:

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

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i "0x%08lx" refererte til adresse "0x%08lx". Minnet kunne ikke v re "%s".

FAULTING_IP:

+7faacd70

7faacd70 ?? ???

TRAP_FRAME: af46c81c -- (.trap 0xffffffffaf46c81c)

ErrCode = 00000010

eax=00000000 ebx=00000000 ecx=00000000 edx=00000201 esi=af46cc50 edi=00000001

eip=7faacd70 esp=af46c890 ebp=af46cc50 iopl=0 nv up ei pl zr na pe nc

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

7faacd70 ?? ???

Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Wow.exe

LAST_CONTROL_TRANSFER: from bfaf7748 to 7faacd70

POSSIBLE_INVALID_CONTROL_TRANSFER: from bfaf7743 to bfaacd70

TWO_BIT_ERROR: 1

STACK_TEXT:

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

af46c88c bfaf7748 bfb12f50 af46cc50 af46cb74 0x7faacd70

af46cc50 e1636ba8 00000000 00000000 00000690 nv4_disp+0xe3748

af46cd50 8054162c 1c400008 12400007 0019fb5c 0xe1636ba8

af46cd50 7c90e4f4 1c400008 12400007 0019fb5c nt!KiFastCallEntry+0xfc

0019fc98 00000000 00000000 00000000 00000000 0x7c90e4f4

STACK_COMMAND: .trap 0xffffffffaf46c81c ; kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: TWO_BIT_CPU_CALL_ERROR

Followup: MachineOwner

---------

*** Possible invalid call from bfaf7743 ( nv4_disp+0xe3743 )

*** Expected target bfaacd70 ( nv4_disp+0x98d70 )

Trenger Hjelp=)