BSOD 64bit, trenger hjelp inkluderer filedumps.

[Klovlid]

Hei!

 

Har hatt utallige blåskjermer og eg klikkar snart!

Har lest utallige forum, lest gjennom nvidia sine egne forum (som dei for såvidt aldri svarar på!!). MEN for å ikkje misse all hemning over min aggresjon, so må eg ha hjelp av en annen kyndig som kan lese gjennom loggane eg legger ved, ser at dei fleste BCcodes enter er 3b, d3 eller 50.

Er ufattelig irriterande sidan eg ser der er utallige andre i verden med samme problem, men ingen får hjelp av produsentane eller MS forsåvidt.

Ditte som kalles å dumpe halvfabrikat på markedet, men legger ved Minidump mappen og hardware oppsett fra Dxdiag + liste.

 

HK: Asus P5KC

CPU: Q6600 Intel

Skjermkort: BFG GF8800GTS 640MB

Minne: Corsair 6400 4GB

HD: Samsung SataII 250GB

Skjerm: Acer AL2216W

PSU: Corsair HX620W

 

PS:

Har kjørt memtest og fant ingenting der, vidare har eg gjennomgått utallige avinstalleringar av drivara for å finne feil med lite hell.

Vidare må det nemnast at det er spill som Titan Quest, Medal of Honor Airborn, Medieval 2, World in Conflict, o.l som eg får blåskjerm under. Får til tider også dette tilfeldig om natten når det kun er desktop + bakgrunnsprogrammer.

 

link til filer: Link til rar fil

 

Håper på svar fort, for frustrasjonen er begynt å kome.

Takk på forhånd.

Endret 22. september 2007 av Klovlid

[Bloody Mess]

Samsung HDD, ja... Kan være den som er problemet. Prøv med en annen disk (annet merke enn Samsung).

[Klovlid]

Samsung HDD, ja... Kan være den som er problemet. Prøv med en annen disk (annet merke enn Samsung).

9547198[/snapback]

 

Den tok ikkje eg heilt....

Samsung disken har ikkje akkurat slått meg skal vere feilen.

[Bloody Mess]

Mange som har hatt problemer med kombinasjonen P5K og Samsung HDD.

Endret 22. september 2007 av BTK

[Klovlid]

Mange som har hatt problemer med kombinasjonen P5K og Samsung HDD.

9548359[/snapback]

 

Fant ut av problemet.

Var en fin guide på nettet som ga meg løysinga, har ikkje link her så får ikkje linka til kilde.

 

Men her er i alle fall guiden på engelsk:

Funker for alle som har hatt problem med sine geforce kort i det siste, det som skjer er at Windows Update laster ned nokre gamle driverar som ikkje heilt blir fjerna ved reinstallering. Så dette fikser biffen viss du får en del blåskjermar.

 

Klikk for å se/fjerne innholdet nedenfor

Step 1.

Change the Windows Update settings so that it will not automatically install any drivers.

This is very important, if you don't change this setting then Windows Update will simply reinstall the driver again.

Click [sTART][CONTROL PANEL][WINDOWS UPDATE][CHANGE SETTINGS]

Change the setting so that it is: [Download updates but let me choose whether to install them].

 

Step 2.

Reboot into safe mode.

Do this by pressing [f8] when the computer is restarting.

 

Step 3.

Uninstall the video driver.

Click [sTART][CONTROL PANEL][PROGRAMS AND FEATURES]

Right click [NVIDIA DRIVERS] and choose [uninstall/change]. Follow the onscreen prompts to uninstall the driver.

 

 

Step 4.

Reboot into safe mode.

Once the nvidia driver is uninstalled, you will need to reboot again into safe mode. Be careful to try not to boot the computer into normal mode.

Boot into safe mode by pressing [f8] as the computer is restarting.

 

Step 5.

After the reboot, you will be prompted to install a new driver. Choose "Dont show this message again for this device".

 

Step 6.

Change the folder options so that you can see all the files.

From any Windows Explorer window, click [TOOLS][FOLDER OPTIONS].

 

Step 7.

From the view tab choose the following:

a.) Show hidden files and folders.

B.) Untick - Hide protected operating system files.

 

Step 8.

Ensure that you can see the file dates

Do this by clicking on a blank column and selecting date modified.

 

Step 9.

Navigate to c:\windows\system32

Sort the files by name.

Scroll down to the files which begin with the letters 'nv'

Select all the files which begin with the letters 'nv' and are dated 10th Feb 2007 10:48AM.

Delete the selected files.

DO NOT DELETE ANY FILES DATED 2ND NOVEMBER 2006. THESE ARE IMPORTANT OPERATING SYSTEM FILES.

 

Step 10

Repeat step 9 in the folder of c:\windows\system32\drivers

 

Step 11. (only for 64bit Vista)

Repeat step 9 in the folder of c:\windows\sysWOW64

 

Step 12

Install the driver which you downloaded from the nvidia website.

 

Endret 22. september 2007 av Klovlid

[Klovlid]

Funka visst dårlig allikavel, har en feil med svchost.exe som kjører under system!

 

Debug under.

Klikk for å se/fjerne innholdet nedenfor

 

Microsoft ® Windows Debugger Version 6.7.0005.1

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\Mini092207-06.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 Vista Kernel Version 6000 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6000.16514.amd64fre.vista_gdr.070627-1500

Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af50

Debug session time: Sat Sep 22 18:02:35.116 2007 (GMT+2)

System Uptime: 0 days 0:47:28.000

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 3B, {c000001d, fffff80001e8979a, fffff98017cba1e0, 0}

 

Probably caused by : ntkrnlmp.exe ( nt!PsLookupProcessByProcessId+3a )

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c000001d, Exception code that caused the bugcheck

Arg2: fffff80001e8979a, Address of the exception record for the exception that caused the bugcheck

Arg3: fffff98017cba1e0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

 

Debugging Details:

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

 

 

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

 

FAULTING_IP:

nt!PsLookupProcessByProcessId+3a

fffff800`01e8979a 0f8494000000 je nt!PsLookupProcessByProcessId+0xd4 (fffff800`01e89834)

 

CONTEXT: fffff98017cba1e0 -- (.cxr 0xfffff98017cba1e0)

rax=fffff880047c4b50 rbx=0000000000000000 rcx=fffffa8004757c10

rdx=0000000000000ed4 rsi=0000000000000001 rdi=fffffa80044fa2a0

rip=fffff80001e8979a rsp=fffff98017cbaa40 rbp=fffff98017cbaab8

r8=fffff88001fbe000 r9=0000000000000018 r10=0000000000000000

r11=fffff98017cbaa40 r12=0000000003bcf2c8 r13=000007fefc693796

r14=000007fefc693782 r15=0000000003bcf938

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286

nt!PsLookupProcessByProcessId+0x3a:

fffff800`01e8979a 0f8494000000 je nt!PsLookupProcessByProcessId+0xd4 (fffff800`01e89834) [br=0]

Resetting default scope

 

CUSTOMER_CRASH_COUNT: 6

 

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

 

BUGCHECK_STR: 0x3B

 

PROCESS_NAME: svchost.exe

 

CURRENT_IRQL: 0

 

LAST_CONTROL_TRANSFER: from fffff80001e6e45a to fffff80001e8979a

 

STACK_TEXT:

fffff980`17cbaa40 fffff800`01e6e45a : 00000000`00000000 fffff980`17cbaca0 00000000`00000001 fffff980`17cbaca0 : nt!PsLookupProcessByProcessId+0x3a

fffff980`17cbaa70 fffff800`01e6e2e3 : ffffb557`3eafcbd6 fffffa80`044fa2a0 00000000`03bcf938 000007fe`fc693782 : nt!PsOpenProcess+0x168

fffff980`17cbabe0 fffff800`01c4d673 : fffffa80`044fa2a0 00000000`03bcf6c0 fffffa80`044fa2a0 00000000`03bcf6c0 : nt!NtOpenProcess+0x33

fffff980`17cbac20 00000000`773604da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`03bcf228 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773604da

 

 

FOLLOWUP_IP:

nt!PsLookupProcessByProcessId+3a

fffff800`01e8979a 0f8494000000 je nt!PsLookupProcessByProcessId+0xd4 (fffff800`01e89834)

 

SYMBOL_STACK_INDEX: 0

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

IMAGE_NAME: ntkrnlmp.exe

 

DEBUG_FLR_IMAGE_TIMESTAMP: 46830f41

 

SYMBOL_NAME: nt!PsLookupProcessByProcessId+3a

 

STACK_COMMAND: .cxr 0xfffff98017cba1e0 ; kb

 

FAILURE_BUCKET_ID: X64_0x3B_nt!PsLookupProcessByProcessId+3a

 

BUCKET_ID: X64_0x3B_nt!PsLookupProcessByProcessId+3a

 

Followup: MachineOwner

---------

 

Endret 23. september 2007 av Klovlid