Ny PC med mange små problemer [LØST]

[Aak1]

Jeg har kjøpt meg ny PC nettopp, og bygd den selv.

 

Club Geforce 8600GT 512mb RAM

Asus P5K Pro

4x 1gb croshair RAM

Quad Core Q6600

 

Windows XP 32 bit

 

 

Jeg er litt frustrert siden jeg har hatt en del småproblemer. Den fyser ofte i 2-5 minutter når jeg minimerer og til og med avlsutter spill (CS Source, Team Fortress). Når jeg spiller BF2 og joiner en server vil ikke musa virke. Tastaturet virker bare halvveis, jeg får ikke til å trykke på esc eller noen ingame knapper, men alt+tab, alt+f4 og ctrl+alt+delete fungerer. Så jeg får slått av spillet. Jeg har også fått blåsjerm i BF2 en gang. Det var etter denne blåsjermen at musa og tastaturet ikke ville fungere ingame. I tillegg har det hendt seg at windows har vært trengt å laste opp, og at PC-en fryser fra mindre krevende aplikasjoner som f.eks msn. (sjelden)

 

CPU temp idle: 15-20 C

GPU temp idle: 35 C

Hovedkort temp idle: 30

 

Jeg regner med at loading temp ikke er kritisk høyt.

 

EDIT: jeg kjører også dual-screen - etter jeg disabla dualscreen og lukket alle programmene mine gikk det greit å minimere spill uten frysing, men har fortsatt problemer med BF2. Uansett så skal jo PC-en klare å kjøre flere programmer + dualscreen uten å fryse ved minimering og avslutting av spill

Endret 24. mars 2008 av Aak1

[Duqe]

Det er kun 64bit OS som støtter 4GB ram, kanskje det som forårsaker problemene dine?

[fenderebest]

Om du har en blåskjerm på lager kan du sjekke denne i Windbg! Veilednining for hvordan man bruker Windbg finnes over!

[Aak1]

ok. Takk, fin guide!

 

Jeg har nå kjørt en analyse av den, men dette er gresk for meg.

 

Kræsjdump 1:

 

 

 

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\WINDOWS\Minidump\Mini032308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Mar 23 02:26:33.968 2008 (GMT+1)
System Uptime: 0 days 3:50:42.572
Loading Kernel Symbols
..........................................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c0193650, 2, 0, 80510d72}



Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+2e )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c0193650, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80510d72, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS:  c0193650 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiDeleteValidAddress+2e
80510d72 8b0f			mov	 ecx,dword ptr [edi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  BF2.exe

LAST_CONTROL_TRANSFER:  from 805aee11 to 80510d72

STACK_TEXT:  
ad9e6c2c 805aee11 326ca201 89cd7cf8 007ffff8 nt!MiDeleteValidAddress+0x2e
ad9e6c4c 8051295d 89cd7cf8 89cd7e30 89cd7cf8 nt!MiDeleteAddressesInWorkingSet+0x65
ad9e6c80 805d114b 00cd7cf8 89b14020 89b14268 nt!MmCleanProcessAddressSpace+0x193
ad9e6d08 805d130e 0000002a 89b14020 00000000 nt!PspExitThread+0x621
ad9e6d28 805d14e9 89b14020 0000002a ad9e6d64 nt!PspTerminateThreadByPointer+0x52
ad9e6d54 805409ac 00000000 0000002a 0012f598 nt!NtTerminateProcess+0x105
ad9e6d54 7c90eb94 00000000 0000002a 0012f598 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f598 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteValidAddress+2e
80510d72 8b0f			mov	 ecx,dword ptr [edi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDeleteValidAddress+2e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  45e5484a

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiDeleteValidAddress+2e

BUCKET_ID:  0xA_nt!MiDeleteValidAddress+2e

Followup: MachineOwner
---------

 

 

 

 

Kræsjdump 2:

 

 

 

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\WINDOWS\Minidump\Mini032208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Mar 22 05:51:50.187 2008 (GMT+1)
System Uptime: 0 days 5:21:32.787
Loading Kernel Symbols
..........................................................................................
.........................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {8cb1b2fc, 2, 0, 80519d7b}



Probably caused by : memory_corruption ( nt!MiDecommitPages+2e1 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8cb1b2fc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80519d7b, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS:  8cb1b2fc 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiDecommitPages+2e1
80519d7b 8b500c		  mov	 edx,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  avgemc.exe

LAST_CONTROL_TRANSFER:  from 805b20c4 to 80519d7b

STACK_TEXT:  
b7415ca4 805b20c4 00b53000 c0005ae0 8a555020 nt!MiDecommitPages+0x2e1
b7415d4c 805409ac ffffffff 00b2fcf4 00b2fcf8 nt!NtFreeVirtualMemory+0x588
b7415d4c 7c90eb94 ffffffff 00b2fcf4 00b2fcf8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b2fca0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDecommitPages+2e1
80519d7b 8b500c		  mov	 edx,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiDecommitPages+2e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  45e5484a

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiDecommitPages+2e1

BUCKET_ID:  0xA_nt!MiDecommitPages+2e1

Followup: MachineOwner
---------

 

 

 

 

Hva får du ut av dette?

[fenderebest]

Dette er uten tvil problemer med det fysiske minnet.

Du kan sjekke innstillingene i BIOS at brikkene feks får den spenningen de skal ha.

Du kan prøve å kjøre med 2GB feks for å se om problemet gjentar seg.

Du kan prøve å oppdater BIOS.

[snippsat]

Har gitt noen råd om dette før.

Her en du kan se på.

https://www.diskusjon.no/index.php?showtopic=893096

[Aak1]

Skal jeg bruke de samme tallene? Altså, øke til 2,1 volt?

 

Jeg har 2x CORSAIR TWIN2X 6400 DDR2, 2048MB CL5 Kit w/two matched CM2X1024A-6400 Dimm's (TWIN2X2048-6400)

 

Altså, 4 brikker.

[snippsat]

Nei du bruker selvfølgelig spenning og timings til corsair.

Så setter du det inn som i posten.

[Aak1]

skal vi se...

 

Jeg fant ut følgende:

 

Latency Timings: CL5

Spenningsforsyning: 1.9 V

[snippsat]

MEM (DDR), Mhz: 800

Actual MEM (DDR), Mhz: 400(cpu-z)

 

Dram voltage:1.9v

 

tCL 5 (CAS Latency 5)

tRCD 5

tRP 5

tRAS 15

Command Per Clock (CMD): 2 clock (2T)

 

Advance Memory Settings

tRRD: AUTO

tRC: AUTO

tWR: AUTO

tWTR: AUTO

tREF: AUTO

Async Latency: AUTO

 

Når dette er satt bot memtest86+ 2.01

http://www.memtest.org/

Feil i test 5 øk spenning(2.0v)

Husk og øk NB spenning.

Masse feil test 1 og 1 brikke.

 

Husk at som oftes ligger det mye fix for 4gb i nyere bioser.

Endret 23. mars 2008 av SNIPPSAT

[Aak1]

Takk! Jeg fant også ut at jeg hadde en litt utdatert BIOS. Skal oppdatere den også.

[Aak1]

Jeg endret bare DRAM Voltage, fant ikke det andre.

 

Jeg oppdaterte også BIOS. Memtest fikk 1 pass og 0 feil

 

Takk for hjelpen!

Endret 24. mars 2008 av Aak1