blå skjerm pga skjermkort drivere?

eXt3 · 29. mars 2008

hei.

for noen dager siden fikk jeg blåskjerm og jeg fikk blåskjerm selv om jeg restartet pcen flere ganger, jeg gikk inn i safe mode å slettet skjermkort driverne å prøvde å restarte pcen, pcen fungerte som den skullle untatt at hele skrivebordet er grått å ingen av ikonene som skal være der vises. jeg prøvde å laste ned nye skjermkort drivere fra http://www.nvidia.com men når jeg restartet pcen fikk jeg blå skjerm. så jeg slettet de nye skjermkort driverne via safe mode, å pcen fungerte som vanlig untatt det grå skrivebordet å ingen ikoner.

er skjermkortet ødelagt? eller hva er feil?

hvordan få ordnet det?

blå skjerm kode: STOP: 0x0000008E (0xc0000005,0x8a0031FB,0x8829f9b4,0x00000000)

skjermkort: xfx nvidia 8800gtx

operativsystem: win vista home premium.

Endret 29. mars 2008 av nretnek

DeadManWalking · 29. mars 2008

Ved blåskjerm burde man alltid kjøre memtest86 for å utelukke ramen, windows skylder på det programmet som skriver til det ødelagt område i minnet.

snippsat · 29. mars 2008

Memtest86+ 2.01

Den feilen lager en minidump(se guide øverst på siden)

eXt3 · 29. mars 2008

testet med memtest86+. 0 errors .

andre ting jeg kan sjekke?

takker for svar

Endret 29. mars 2008 av nretnek

fenderebest · 29. mars 2008

Du bør naturligvis feilsøke blåskjermen med Windbg. Guide for hvordan denne brukes finner du ovenfor.

eXt3 · 29. mars 2008

testet med windbg.

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Loading Dump File [C:\Windows\Minidump\Mini032908-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: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6000.16575.x86fre.vista_gdr.071009-1548

Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10

Debug session time: Sat Mar 29 15:01:33.449 2008 (GMT+1)

System Uptime: 0 days 0:04:42.224

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

.......

Unable to load image \SystemRoot\system32\DRIVERS\nv4_mini.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, b3f52857, 83677350, 8367704c}

Probably caused by : nv4_mini.sys ( nv4_mini+cf857 )

Followup: MachineOwner

---------

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

Arg3: 83677350, Exception Record Address

Arg4: 8367704c, Context Record Address

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

FAULTING_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

EXCEPTION_RECORD: 83677350 -- (.exr 0xffffffff83677350)

ExceptionAddress: b3f52857 (nv4_mini+0x000cf857)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 000000b8

Attempt to read from address 000000b8

CONTEXT: 8367704c -- (.cxr 0xffffffff8367704c)

eax=00000000 ebx=859c6a30 ecx=00000001 edx=859e0a3c esi=85a04000 edi=859e0950

eip=b3f52857 esp=83677418 ebp=00000002 iopl=0 nv up ei pl zr na pe nc

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

nv4_mini+0xcf857:

b3f52857 ff90b8000000 call dword ptr [eax+0B8h] ds:0023:000000b8=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac

Unable to read MiSystemVaType memory at 821117e0

000000b8

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 00000000 to b3f52857

STACK_TEXT:

83677414 00000000 859f6000 85a04000 859c6a30 nv4_mini+0xcf857

FOLLOWUP_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+cf857

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 453482ab

STACK_COMMAND: .cxr 0xffffffff8367704c ; kb

FAILURE_BUCKET_ID: 0x7E_nv4_mini+cf857

BUCKET_ID: 0x7E_nv4_mini+cf857

Followup: MachineOwner

---------

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

Arg3: 83677350, Exception Record Address

Arg4: 8367704c, Context Record Address

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

FAULTING_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

EXCEPTION_RECORD: 83677350 -- (.exr 0xffffffff83677350)

ExceptionAddress: b3f52857 (nv4_mini+0x000cf857)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 000000b8

Attempt to read from address 000000b8

CONTEXT: 8367704c -- (.cxr 0xffffffff8367704c)

eax=00000000 ebx=859c6a30 ecx=00000001 edx=859e0a3c esi=85a04000 edi=859e0950

eip=b3f52857 esp=83677418 ebp=00000002 iopl=0 nv up ei pl zr na pe nc

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

nv4_mini+0xcf857:

b3f52857 ff90b8000000 call dword ptr [eax+0B8h] ds:0023:000000b8=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac

Unable to read MiSystemVaType memory at 821117e0

000000b8

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 00000000 to b3f52857

STACK_TEXT:

83677414 00000000 859f6000 85a04000 859c6a30 nv4_mini+0xcf857

FOLLOWUP_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+cf857

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 453482ab

STACK_COMMAND: .cxr 0xffffffff8367704c ; kb

FAILURE_BUCKET_ID: 0x7E_nv4_mini+cf857

BUCKET_ID: 0x7E_nv4_mini+cf857

Followup: MachineOwner

---------

1: kd> !analazye -v

No export analazye found

kan noen si hva feilen er?

fenderebest · 29. mars 2008

Selvsagt...som du ser av kræsjdumpen ser det ut til at skjermkort miniport driveren går tom for minne da den referer til Nullpekende referanser i minnet.

Sett først og fremst opp windows til å generere en Kjerneminnedump slik at du kan feilsøke minnet nærmere om problemet skulle gjennoppstå.

Deretter kan du bruke Process Explorer for å prøve å søke etter minnelekasjer i kjerneminnet.

eXt3 · 29. mars 2008

satt opp kjerneminnedump.

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6000.16575.x86fre.vista_gdr.071009-1548

Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10

Debug session time: Sat Mar 29 15:01:33.449 2008 (GMT+1)

System Uptime: 0 days 0:04:42.224

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

.......

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, b3f52857, 83677350, 8367704c}

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

Probably caused by : nv4_mini.sys ( nv4_mini+cf857 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

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.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: b3f52857, The address that the exception occurred at

Arg3: 83677350, Exception Record Address

Arg4: 8367704c, Context Record Address

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

FAULTING_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

EXCEPTION_RECORD: 83677350 -- (.exr 0xffffffff83677350)

ExceptionAddress: b3f52857 (nv4_mini+0x000cf857)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 000000b8

Attempt to read from address 000000b8

CONTEXT: 8367704c -- (.cxr 0xffffffff8367704c)

eax=00000000 ebx=859c6a30 ecx=00000001 edx=859e0a3c esi=85a04000 edi=859e0950

eip=b3f52857 esp=83677418 ebp=00000002 iopl=0 nv up ei pl zr na pe nc

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

nv4_mini+0xcf857:

b3f52857 ff90b8000000 call dword ptr [eax+0B8h] ds:0023:000000b8=????????

Resetting default scope

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

READ_ADDRESS: 000000b8

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from b3f6b9e0 to b3f52857

STACK_TEXT:

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

83677450 b3f6b9e0 85a04000 b3ec7adb 859f601c nv4_mini+0xcf857

83677458 b3ec7adb 859f601c b3f03b71 00000001 nv4_mini+0xe89e0

83677460 b3f03b71 00000001 b3f53b3c 859c6a30 nv4_mini+0x44adb

83677468 b3f53b3c 859c6a30 00000010 b3f53b5b nv4_mini+0x80b71

83677474 b3f53b5b 00000001 859a8008 859c6a30 nv4_mini+0xd0b3c

8367748c b3ec7ab6 8572bcc0 00000002 00000000 nv4_mini+0xd0b5b

836774d4 b3fbaaeb 8587b008 b41f7a84 0000000f nv4_mini+0x44ab6

836774f4 b3f02059 859c6a30 859e0950 00000007 nv4_mini+0x137aeb

83677504 b3f0393b 85a04000 858d7ac8 859a4a70 nv4_mini+0x7f059

8367751c b3ee42ea 859c6a30 915e8823 859f03a0 nv4_mini+0x8093b

00000000 00000000 00000000 00000000 00000000 nv4_mini+0x612ea

FOLLOWUP_IP:

nv4_mini+cf857

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+cf857

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 453482ab

STACK_COMMAND: .cxr 0xffffffff8367704c ; kb

FAILURE_BUCKET_ID: 0x7E_nv4_mini+cf857

BUCKET_ID: 0x7E_nv4_mini+cf857

Followup: MachineOwner

---------

jeg klarte ikke å bruke Process Explorer:/

er det mulig å få fikset dette evt. hvordan?

fenderebest · 29. mars 2008

Når du åpner opp kjerneminnedumpen skriv !vm i kommandolinjen og post det som kommer opp.

eXt3 · 29. mars 2008

når jeg skrev !vm:

*** Virtual Memory Usage ***

Physical Memory: 523760 ( 2095040 Kb)

Page File: \??\C:\pagefile.sys

Current: 2402240 Kb Free Space: 2207556 Kb

Minimum: 2402240 Kb Maximum: 3528352 Kb

Available Pages: 324068 ( 1296272 Kb)

ResAvail Pages: 478895 ( 1915580 Kb)

Locked IO Pages: 0 ( 0 Kb)

Free System PTEs: 283410 ( 1133640 Kb)

Modified Pages: 22118 ( 88472 Kb)

Modified PF Pages: 22074 ( 88296 Kb)

NonPagedPool Usage: 12338 ( 49352 Kb)

NonPagedPool Max: 387513 ( 1550052 Kb)

PagedPool 0 Usage: 14004 ( 56016 Kb)

PagedPool 1 Usage: 6313 ( 25252 Kb)

PagedPool 2 Usage: 597 ( 2388 Kb)

PagedPool 3 Usage: 514 ( 2056 Kb)

PagedPool 4 Usage: 709 ( 2836 Kb)

PagedPool Usage: 22137 ( 88548 Kb)

PagedPool Maximum: 523264 ( 2093056 Kb)

Shared Commit: 16040 ( 64160 Kb)

Special Pool: 0 ( 0 Kb)

Shared Process: 2969 ( 11876 Kb)

PagedPool Commit: 22152 ( 88608 Kb)

Driver Commit: 6949 ( 27796 Kb)

Committed pages: 232959 ( 931836 Kb)

Commit limit: 1103137 ( 4412548 Kb)

Total Private: 170971 ( 683884 Kb)

040c svchost.exe 14492 ( 57968 Kb)

03f4 svchost.exe 14353 ( 57412 Kb)

0ce0 avgcc.exe 12104 ( 48416 Kb)

01c0 avgamsvr.exe 11996 ( 47984 Kb)

0454 avgrssvc.exe 11701 ( 46804 Kb)

0dd8 msnmsgr.exe 10997 ( 43988 Kb)

085c SearchIndexer.e 10340 ( 41360 Kb)

0114 explorer.exe 9193 ( 36772 Kb)

0350 svchost.exe 7867 ( 31468 Kb)

055c svchost.exe 3809 ( 15236 Kb)

0108 setup.exe 3783 ( 15132 Kb)

0fc8 wmpnetwk.exe 3707 ( 14828 Kb)

03b4 svchost.exe 3424 ( 13696 Kb)

065c svchost.exe 3361 ( 13444 Kb)

0460 audiodg.exe 2960 ( 11840 Kb)

0d20 sidebar.exe 2918 ( 11672 Kb)

0704 Setup.exe 2555 ( 10220 Kb)

0ac0 WmiPrvSE.exe 2374 ( 9496 Kb)

0794 taskeng.exe 2361 ( 9444 Kb)

0bb4 MSASCui.exe 2337 ( 9348 Kb)

0be8 CTXFISPI.EXE 2229 ( 8916 Kb)

04c4 svchost.exe 1872 ( 7488 Kb)

054c sidebar.exe 1839 ( 7356 Kb)

0b28 TrustedInstalle 1666 ( 6664 Kb)

063c spoolsv.exe 1431 ( 5724 Kb)

0484 SLsvc.exe 1372 ( 5488 Kb)

0b34 KHALMNPR.exe 1322 ( 5288 Kb)

0004 System 1173 ( 4692 Kb)

0e0c SetPoint.exe 1074 ( 4296 Kb)

0c4c CTXFIHLP.EXE 947 ( 3788 Kb)

02d8 svchost.exe 931 ( 3724 Kb)

0820 svchost.exe 921 ( 3684 Kb)

0ff0 drvinst.exe 878 ( 3512 Kb)

0224 lsass.exe 821 ( 3284 Kb)

0dbc GoogleToolbarNo 816 ( 3264 Kb)

01c4 MONyog.exe 809 ( 3236 Kb)

0314 svchost.exe 797 ( 3188 Kb)

0c44 CTHELPER.EXE 794 ( 3176 Kb)

0d70 WmiPrvSE.exe 793 ( 3172 Kb)

0cd4 LGDevAgt.exe 690 ( 2760 Kb)

0218 services.exe 668 ( 2672 Kb)

0fb4 setup.exe 664 ( 2656 Kb)

0ec4 unsecapp.exe 639 ( 2556 Kb)

0230 lsm.exe 583 ( 2332 Kb)

0ccc GrooveMonitor.e 530 ( 2120 Kb)

0190 AppleMobileDevi 512 ( 2048 Kb)

02c0 winlogon.exe 495 ( 1980 Kb)

01f4 csrss.exe 493 ( 1972 Kb)

0d2c ehtray.exe 490 ( 1960 Kb)

0804 svchost.exe 486 ( 1944 Kb)

0d80 wmpnscfg.exe 474 ( 1896 Kb)

0210 avgupsvc.exe 471 ( 1884 Kb)

09cc taskeng.exe 466 ( 1864 Kb)

0778 dwm.exe 422 ( 1688 Kb)

01bc csrss.exe 419 ( 1676 Kb)

083c svchost.exe 353 ( 1412 Kb)

01e8 wininit.exe 324 ( 1296 Kb)

0cbc hpwuSchd2.exe 322 ( 1288 Kb)

0c98 PIFSvc.exe 310 ( 1240 Kb)

0400 PIFSvc.exe 289 ( 1156 Kb)

027c avgrssvc.exe 282 ( 1128 Kb)

0f58 ehmsas.exe 268 ( 1072 Kb)

0ca4 jusched.exe 263 ( 1052 Kb)

0a2c usnsvc.exe 258 ( 1032 Kb)

073c svchost.exe 212 ( 848 Kb)

04d0 svchost.exe 198 ( 792 Kb)

0408 CTSVCCDA.EXE 190 ( 760 Kb)

0178 smss.exe 83 ( 332 Kb)

0710 NVUninst.exe 0 ( 0 Kb)

fenderebest · 30. mars 2008

Kjør !memusage og post denne infoen:

Compiling memory usage data (99% Complete).

Zeroed: 0 ( 0 kb)

Free: 0 ( 0 kb)

Standby: 0 ( 0 kb)

Modified: 0 ( 0 kb)

ModifiedNoWrite: 0 ( 0 kb)

Active/Valid: 523885 (2095540 kb)

Transition: 0 ( 0 kb)

Bad: 0 ( 0 kb)

Unknown: 0 ( 0 kb)

TOTAL: 523885 (2095540 kb)

eXt3 · 30. mars 2008

!memuage:

Compiling memory usage data (99% Complete).

Zeroed: 0 ( 0 kb)

Free: 425 ( 1700 kb)

Standby: 323643 (1294572 kb)

Modified: 22118 ( 88472 kb)

ModifiedNoWrite: 97 ( 388 kb)

Active/Valid: 177418 (709672 kb)

Transition: 217 ( 868 kb)

Bad: 0 ( 0 kb)

Unknown: 0 ( 0 kb)

TOTAL: 523918 (2095672 kb)

fenderebest · 30. mars 2008

Hmm besynderlig...det virker jo som det er mer en nok minne...om du deaktiverer AVG fungerer det da?

Ellers kan du prøve å skrive:

u nv4_mini+cf857

Og poste det som kommer opp?

Eventuellt prøve andre drivere?

Endret 30. mars 2008 av fenderebest

eXt3 · 30. mars 2008

hjalp ikke å deaktivere avg.

u nv4_mini+cf857:

Probably caused by : nv4_mini.sys ( nv4_mini+cf857 )

Followup: MachineOwner

---------

1: kd> u nv4_mini+cf857

nv4_mini+0xcf857:

b3f52857 ff90b8000000 call dword ptr [eax+0B8h]

b3f5285d 83f805 cmp eax,5

b3f52860 1bc0 sbb eax,eax

b3f52862 f7d8 neg eax

b3f52864 0fafc5 imul eax,ebp

b3f52867 09442460 or dword ptr [esp+60h],eax

b3f5286b 837c242800 cmp dword ptr [esp+28h],0

b3f52870 7417 je nv4_mini+0xcf889 (b3f52889)

prøvd driverene som følgte med skjermkortet og prøvd med drivere lastet ned fra nettsiden.

fenderebest · 30. mars 2008

Litt merkelig egentlig-det som er problemet er at:

nv4_mini-(Som jeg gjetter er Miniport driveren til skjermkortet ditt, sjekk forresten dette selv på maskinen din slik at du er sikker at den tilhører skjermkortet ditt)

Bruker funksjonen: cf857

Som kaller på en peker på addressen: 000000b8

(Som er et ugyldig område av minnet som ikke brukes)

Og det er dette som "trigger" feilen.

Siden det bestandig er samme funksjon som peker mot den samme addressen er problmet mest sannsynlig IKKE i hardware men i software. Som regel skyldes det at drivere bruker lave addresser at de ikke har nok minne men det virker jo som det er rikelig med minne igjen.

Jeg klarer dessverre ikke å få noe mer ut av dette uten å se på dette selv, beklager!

Endret 30. mars 2008 av fenderebest

blå skjerm pga skjermkort drivere?

Anbefalte innlegg

Lenke til kommentar

Videoannonse

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Populær nå

Hvem er aktive 0 medlemmer