Maskinen restarter seg, hjelp med å forstå logger

[Bruktbilen]

Før var det bare en skjelden gang, fikset dette med at jeg skaffet skjermdrivere, men nå restarter den seg bare jeg rører browseren.

 

Noen som vet hva som er problem ved å se på det nedenfor?

 

Får de her error loggene(2 linjer hver) når jeg starter opp igjen:

 

 

BCCode : 100000be BCP1 : 7E41C96F BCP2 : 0DAA1025 BCP3 : F8950D5C

BCP4 : 0000000A OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 100000d1 BCP1 : 00000000 BCP2 : 00000002 BCP3 : 00000000

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : c2 BCP1 : 00000007 BCP2 : 00000CD4 BCP3 : 00000001

BCP4 : E2C391D0 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 1000000a BCP1 : 00DFF5C4 BCP2 : 000000FF BCP3 : 00000001

BCP4 : 804DA8D8 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 1000008e BCP1 : C0000005 BCP2 : BF80EB14 BCP3 : F3D00748

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 10000050 BCP1 : BF7B4F47 BCP2 : 00000000 BCP3 : BF7B4F47

BCP4 : 00000002 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 10000050 BCP1 : B89A0338 BCP2 : 00000000 BCP3 : BF80D3C6

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 10000050 BCP1 : B89A0338 BCP2 : 00000000 BCP3 : BF80D3C6

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

 

 

BCCode : 1000008e BCP1 : C0000005 BCP2 : BF81389C BCP3 : F49097FC

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

 

Endret 2. november 2008 av Bruktbilen

[Bllink]

Maskina blir ikke for varm da?

[Bruktbilen]

Kan jeg ikke tro...

 

Jeg pleier å ha maskinen på hele tiden, men den restarter seg om natta og ødelegger nedlastingen.

 

Når jeg derimot skrur maskinen av og skal starte den igjen så tar det rundt ganske mange forsøk før den starter opp, og når den endelig skrur seg på så kan den få anfall slik at den bare skrur seg av igjen.

 

Nå for eksempel er den fin, står og laster ned, men jeg lurer egentlig på hva feilmeldingene er. En løsning på problemet er jo å ikke skru av maskinen, men siden den restarter seg om natta så er jo det litt kjedelig.

[Hrodebert]

Kan være mye eller ingenting. Du skriver ikke noe om maskinvare. Kan du utdype dette?

[Bruktbilen]

NVIDIA GeForce2 Ti

AMD Duron prosessor 949MHz

512MB RAM

 

Akkurat nå restartet den seg uten at jeg rørte den, satt på laptopen...

 

Fikk:

BCCode : 1000008e BCP1 : C000001D BCP2 : BF02C370 BCP3 : F5AAC260

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

Endret 2. november 2008 av Bruktbilen

[Humbo]

Prøv å debugge minidump. Burde gje deg ein peikepinn på kva som tiltar.

[Bruktbilen]

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini110208-08.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) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp3_gdr.080814-1236

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Sun Nov 2 23:30:54.694 2008 (GMT+0)

System Uptime: 0 days 0:04:27.274

Loading Kernel Symbols

..........................................................................................

...........................

Loading User Symbols

Loading unloaded module list

.........

Unable to load image nv4_disp.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nv4_disp.dll

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000008E, {c0000005, bf017353, f4ac3514, 0}

 

Probably caused by : nv4_disp.dll ( nv4_disp+5353 )

 

Followup: MachineOwner

---------

 

>.>

 

Får skaffe noen nye drivere og se om de fungerer.

 

 

 

Detaljert:

 

kd> !analyze -v

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

* *

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

Arg3: f4ac3514, 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:

nv4_disp+5353

bf017353 f6412401 test byte ptr [ecx+24h],1

 

TRAP_FRAME: f4ac3514 -- (.trap 0xfffffffff4ac3514)

ErrCode = 00000000

eax=e1903178 ebx=e185241c ecx=000000e1 edx=00000000 esi=e1903010 edi=e15d8248

eip=bf017353 esp=f4ac3588 ebp=f4ac3648 iopl=0 nv dn ei pl nz na pe nc

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

nv4_disp+0x5353:

bf017353 f6412401 test byte ptr [ecx+24h],1 ds:0023:00000105=??

Resetting default scope

 

CUSTOMER_CRASH_COUNT: 8

 

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

 

BUGCHECK_STR: 0x8E

 

PROCESS_NAME: notepad.exe

 

LAST_CONTROL_TRANSFER: from bf8285bb to bf017353

 

STACK_TEXT:

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

f4ac3648 bf8285bb e15d8248 e185241c e185241c nv4_disp+0x5353

f4ac368c bf812d9c 00000000 e1852538 00000000 win32k!ExtTextOutRect+0x1d1

f4ac37d0 bf80c391 f4ac3908 7ffdf5b0 00000028 win32k!GreBatchTextOut+0xd0

f4ac3924 804de7be 000000cd 0007f95c 0007f97c win32k!NtGdiFlushUserBatch+0x11b

f4ac3940 80566b60 f4ac39fc 80566b96 f4ac39d0 nt!KiFastCallEntry+0xca

f4ac3a34 bf801703 821ddf88 00000002 00000000 nt!KeUserModeCallback+0x87

f4ac3a50 bf8087f2 e27f42b8 00000108 bbe40650 win32k!SetWakeBit+0xb2

f4ac3a7c f4ac3aa0 bf832e87 e1d4ea00 bbe49940 win32k!_PostMessage+0x179

f4ac3aa0 bf846d9a 00000004 00070136 bbe6ea20 0xf4ac3aa0

f4ac3abc bf83ab82 822152a8 00070136 bf83ab87 win32k!xxxSetTrayWindow+0x83

f4ac3ae4 bf83cca6 bf83ccb3 e2aeca48 f4ac3c38 win32k!xxxUpdateTray+0x11e

f4ac3b48 bf820867 81d87878 f4ac3b80 bf86aa8a win32k!xxxActivateThisWindow+0x498

f4ac3b54 bf86aa8a f4ac3b68 7fffffff f4ac3b7c win32k!PopW32ThreadLock+0x12

f4ac3b80 f4ac3c98 bf82203b bf822040 00002000 win32k!xxxProcessEventMessage+0x48a

f4ac3bbc 804dbe67 00000000 00000000 00000000 0xf4ac3c98

f4ac3c48 bf813d1b 00000002 f4ac3c8c 00000018 nt!KiInsertTimerTable+0x1b

f4ac3ccc bf803530 bbe71960 0000000f 00000000 win32k!SfnDWORD+0xa8

f4ac3d0c bf80ebe0 773f3dcf f4ac3d64 0007fe9c win32k!xxxDispatchMessage+0x1dc

f4ac3d58 804de7ec 0007fefc 0007fed4 7c90e4f4 win32k!NtUserDispatchMessage+0x39

f4ac3d58 7c90e4f4 0007fefc 0007fed4 7c90e4f4 nt!KiFastCallEntry+0xf8

0007fed4 00000000 00000000 00000000 00000000 0x7c90e4f4

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nv4_disp+5353

bf017353 f6412401 test byte ptr [ecx+24h],1

 

SYMBOL_STACK_INDEX: 0

 

SYMBOL_NAME: nv4_disp+5353

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nv4_disp

 

IMAGE_NAME: nv4_disp.dll

 

DEBUG_FLR_IMAGE_TIMESTAMP: 424ddded

 

FAILURE_BUCKET_ID: 0x8E_nv4_disp+5353

 

BUCKET_ID: 0x8E_nv4_disp+5353

 

Followup: MachineOwner

 

 

Edit: Hvordan finner man drivere til NVIDIA GeForce2 Ti? o_O Nvidia har ikke det som noe valg...

 

Edit2: Sånn, skaffet en ny driver og ser ut til å fungere normalt, lar den stå på i natt på nedlasting for å se om den krasjer.

Endret 2. november 2008 av Bruktbilen

[Bruktbilen]

Maskinen restartet seg igjen, men denne gangen var feilen:

 

Probably caused by : ntoskrnl.exe ( nt!READ_REGISTER_ULONG+6 )

 

..

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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.

 

Hva skal jeg gjøre?

 

 

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini110308-04.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) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp3_gdr.080814-1236

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Mon Nov 3 03:26:30.473 2008 (GMT+0)

System Uptime: 0 days 3:08:51.048

Loading Kernel Symbols

..........................................................................................

..........................

Loading User Symbols

Loading unloaded module list

.........

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 100000D1, {80dca8d8, ff, 0, 80dca8d8}

 

Probably caused by : ntoskrnl.exe ( nt!READ_REGISTER_ULONG+6 )

 

Followup: MachineOwner

---------

 

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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 kernel debugger is available get stack backtrace.

Arguments:

Arg1: 80dca8d8, memory referenced

Arg2: 000000ff, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 80dca8d8, address which referenced memory

 

Debugging Details:

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

 

 

READ_ADDRESS: 80dca8d8

 

CURRENT_IRQL: ff

 

FAULTING_IP:

+ffffffff80dca8d8

80dca8d8 ?? ???

 

CUSTOMER_CRASH_COUNT: 4

 

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

 

BUGCHECK_STR: 0xD1

 

PROCESS_NAME: BitLord.exe

 

LAST_CONTROL_TRANSFER: from 0cf70cb6 to 80dca8d8

 

FAILED_INSTRUCTION_ADDRESS:

+ffffffff80dca8d8

80dca8d8 ?? ???

 

STACK_TEXT:

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

f8950d38 0cf70cb6 8224d600 804d90ac badb0d00 0x80dca8d8

f8950d40 804d90ac badb0d00 f70cb644 8223580c 0xcf70cb6

f8950d44 badb0d00 f70cb644 8223580c 00000027 nt!READ_REGISTER_ULONG+0x6

f8950d4c 8223580c 00000027 00000026 f7ffa346 0xbadb0d00

f8950d50 00000000 00000026 f7ffa346 822357f0 0x8223580c

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!READ_REGISTER_ULONG+6

804d90ac c20400 ret 4

 

SYMBOL_STACK_INDEX: 2

 

SYMBOL_NAME: nt!READ_REGISTER_ULONG+6

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

IMAGE_NAME: ntoskrnl.exe

 

DEBUG_FLR_IMAGE_TIMESTAMP: 48a404ab

 

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!READ_REGISTER_ULONG+6

 

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!READ_REGISTER_ULONG+6

 

Followup: MachineOwner

---------

 

 

 

Endret 3. november 2008 av Bruktbilen