Problemer med plutselig blåskjerm

Julepils · 11. juli 2008

Innstallerte Windows Vista Ultimate 32bit versjonen i dag. Innstallerte driverene til highpointen og daemon tools og så kom blåskjermen igjen gitt.

Tok ut highpointen fra hovedkortet helt og innstallerte age of conan i håp om å "provoke" en blåskjerm, yepp der kom den alikevel.

Så jeg satt tilbake highpoint kontrolleren og tok ut lydkortet, har ingen anelse om lydkortet (supreme fx greiene som følger med hovedkortet) kan forårsake en blåskjerm av denne sort men shit på, prøver det ut nå så får se hvordan det går. Må bare prøve mest mulig å provoke en blåskjerm, så langt har installasjonen av ageofconan fungert fint hvertfal men får holde på å spille litt, skru av og på spillet og maskinen og prøve å se om jeg klarer å tease, må gi det en dag minst før jeg kan si meg selv sikker, disse her blåskjermene har vært så tilfeldige at det er vanskelig å se hva som forårsaker det.

Er det noen som har anelse om hvor lang tid komplett bruker på å feilsøke en maskin? Fra erfaring, CA? Er en mann av dårlig tolmodighet så tenkte jeg skulle bare kjøre nedover til sandefjord (hvis jeg forstod det rett så var det i sandefjord) med pcen selv. : P

*Update*

PCen fikk blåskjerm igjen så det er ikke lydkortet heller.

Gir snart opp. Eneste som er igjen er vel egentlig noe på hovedkortet eller noe med rammen som ikke kommer opp på testene eller eventuellt skjermkortet selv om det skulle vel egentlig være i sjønneste orden. Trodde ikke heller det skulle være noe galt med strømforsyningen.

Endret 11. juli 2008 av Julepils

Mr_Tiger · 11. juli 2008

:nei:

Har gjort det der WinDbg greiene, og her er teksten:

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini062208-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

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_gdr.070321-2337

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140

Debug session time: Sun Jun 22 14:26:42.609 2008 (GMT+2)

System Uptime: 0 days 8:04:44.471

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

...........

*** WARNING: Unable to verify checksum for hal.dll

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {3, fffffadf90881240, b6200016, 80a01}

Probably caused by : win32k.sys ( win32k!RawInputThread+736 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available (For example Intel

Pentium), the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel

Pentium Pro), the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

Arguments:

Arg1: 0000000000000003

Arg2: fffffadf90881240

Arg3: 00000000b6200016

Arg4: 0000000000080a01

Debugging Details:

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

BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff8000102e890

STACK_TEXT:

fffffadf`90881208 fffff800`0080ef4c : 00000000`0000009c 00000000`00000003 fffffadf`90881240 00000000`b6200016 : nt!KeBugCheckEx

fffffadf`90881210 fffff800`0102db37 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffadf`90881570 : hal!HalHandleMcheck+0x12c

fffffadf`90881370 fffff800`0102d975 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77

fffffadf`908814f0 fffff800`01029bd0 : 00000000`00000000 fffff800`01037c79 00000000`00000000 00000000`00000003 : nt!KiMcheckAbort+0xf5

fffffadf`905b0880 fffff97f`ff0d0b36 : 00000000`00000007 fffff97f`ff3b85b4 fffff97f`00000001 00000000`0000000d : nt!KeWaitForMultipleObjects+0x2d7

fffffadf`905b0910 fffff97f`ff0117ee : 00000000`00000000 00000000`00000000 fffffadf`905b0cf0 00000000`00000004 : win32k!RawInputThread+0x736

fffffadf`905b0c10 fffff97f`ff0a3680 : 00000000`0000000c fffffadf`9bcc0bb0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xb0

fffffadf`905b0c40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9bcc0bb0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c

fffffadf`905b0c70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3

00000000`0099ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a

STACK_COMMAND: kb

FOLLOWUP_IP:

win32k!RawInputThread+736

fffff97f`ff0d0b36 44392583792e00 cmp dword ptr [win32k!gdwUpdateKeyboard (fffff97f`ff3b84c0)],r12d

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!RawInputThread+736

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47e0f866

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_win32k!RawInputThread+736

BUCKET_ID: X64_0x9C_GenuineIntel_win32k!RawInputThread+736

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available (For example Intel

Pentium), the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel

Pentium Pro), the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

Arguments:

Arg1: 0000000000000003

Arg2: fffffadf90881240

Arg3: 00000000b6200016

Arg4: 0000000000080a01

Debugging Details:

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

BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff8000102e890

STACK_TEXT:

fffffadf`90881208 fffff800`0080ef4c : 00000000`0000009c 00000000`00000003 fffffadf`90881240 00000000`b6200016 : nt!KeBugCheckEx

fffffadf`90881210 fffff800`0102db37 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffadf`90881570 : hal!HalHandleMcheck+0x12c

fffffadf`90881370 fffff800`0102d975 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77

fffffadf`908814f0 fffff800`01029bd0 : 00000000`00000000 fffff800`01037c79 00000000`00000000 00000000`00000003 : nt!KiMcheckAbort+0xf5

fffffadf`905b0880 fffff97f`ff0d0b36 : 00000000`00000007 fffff97f`ff3b85b4 fffff97f`00000001 00000000`0000000d : nt!KeWaitForMultipleObjects+0x2d7

fffffadf`905b0910 fffff97f`ff0117ee : 00000000`00000000 00000000`00000000 fffffadf`905b0cf0 00000000`00000004 : win32k!RawInputThread+0x736

fffffadf`905b0c10 fffff97f`ff0a3680 : 00000000`0000000c fffffadf`9bcc0bb0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xb0

fffffadf`905b0c40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9bcc0bb0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c

fffffadf`905b0c70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3

00000000`0099ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a

STACK_COMMAND: kb

FOLLOWUP_IP:

win32k!RawInputThread+736

fffff97f`ff0d0b36 44392583792e00 cmp dword ptr [win32k!gdwUpdateKeyboard (fffff97f`ff3b84c0)],r12d

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!RawInputThread+736

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47e0f866

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_win32k!RawInputThread+736

BUCKET_ID: X64_0x9C_GenuineIntel_win32k!RawInputThread+736

Followup: MachineOwner

---------

Any ideas?

Zzzz :dontgetit:

Jeg kjørte igang en Prime test og så kom blåskjerm. Copypaste fra minidump:
----------------------------------------------------------------

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini062208-02.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

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_gdr.070321-2337

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140

Debug session time: Sun Jun 22 18:39:21.656 2008 (GMT+2)

System Uptime: 0 days 1:21:47.500

*** WARNING: Unable to verify checksum for ntkrnlmp.exe

Loading Kernel Symbols

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

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

Loading User Symbols

Loading unloaded module list

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

*** WARNING: Unable to verify checksum for hal.dll

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {3, fffff80000113bc0, b2200016, 80a01}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+77 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

MACHINE_CHECK_EXCEPTION (9c)

A fatal Machine Check Exception has occurred.

KeBugCheckEx parameters;

x86 Processors

If the processor has ONLY MCE feature available (For example Intel

Pentium), the parameters are:

1 - Low 32 bits of P5_MC_TYPE MSR

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of P5_MC_ADDR MSR

4 - Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA feature available (For example Intel

Pentium Pro), the parameters are:

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

IA64 Processors

1 - Bugcheck Type

1 - MCA_ASSERT

2 - MCA_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing MCA.

3 - MCA_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.

4 - MCA_FATAL

FW reported a fatal MCA.

5 - MCA_NONFATAL

SAL reported a recoverable MCA and we don't support currently

support recovery or SAL generated an MCA and then couldn't

produce an error record.

0xB - INIT_ASSERT

0xC - INIT_GET_STATEINFO

SAL returned an error for SAL_GET_STATEINFO while processing INIT event.

0xD - INIT_CLEAR_STATEINFO

SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.

0xE - INIT_FATAL

Not used.

2 - Address of log

3 - Size of log

4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO

AMD64 Processors

1 - Bank number

2 - Address of MCA_EXCEPTION structure

3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error

4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error

Arguments:

Arg1: 0000000000000003

Arg2: fffff80000113bc0

Arg3: 00000000b2200016

Arg4: 0000000000080a01

Debugging Details:

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

BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff8000102e890

STACK_TEXT:

fffffadf`90881208 fffff800`0080ef4c : 00000000`0000009c 00000000`00000003 fffffadf`90881240 00000000`b2200016 : nt!KeBugCheckEx

fffffadf`90881210 fffff800`0102db37 : 00000000`00000000 00000000`00000000 00000000`c0000034 fffffadf`90881570 : hal!HalHandleMcheck+0x12c

fffffadf`90881370 fffff800`0102d975 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77

fffffadf`908814f0 00000000`6b0068c3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5

00000000`0386e830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b0068c3

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!KxMcheckAbort+77

fffff800`0102db37 488d8c2400010000 lea rcx,[rsp+100h]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KxMcheckAbort+77

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 460280f7

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+77

BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+77

Followup: MachineOwner

---------

Jeg skrudde av psuen og tok ut kabelen og drog ut rocket ide kontrolleren og et par andre ting som ikke er nødvendige for at systemet skal fungere. Så nå er det kun sata (boot) disken som står i. Kjører igang en ny test og om blåskjermen skulle gå på igjen så tar jeg ut lydkortet og prøver etterpå å ta ut 1x 2gb rambrikke.

Noen som finner/ser noe tydelig fra minidumpen?

-------

Update:

Nå har jeg latt SP2004 stå på 40min og så langt:

More than one CPU detected.

You should run two copies of SP2004 simultaneously.

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 3838 Time: 15

CPU: 3173MHz FSB: 333MHz [334MHz x 9.5 est.]

CPU: 3173MHz FSB: 333MHz [334MHz x 9.5 est.]

22.06.2008 18:58 Beginning a continuous self-test to check your computer.

Press Stop to end this test.

Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.

Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.

Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.

Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.

Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.

Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.

Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.

Test 8, 4000 Lucas-Lehmer iterations of M18274367 using 1024K FFT length.

Test 9, 4000 Lucas-Lehmer iterations of M18274369 using 1024K FFT length.

Test 10, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.

Test 11, 4500 Lucas-Lehmer iterations of M17432577 using 1024K FFT length.

Self-test 1024K passed!

Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.

Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.

Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.

Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.

Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.

Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.

Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.

Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.

Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.

Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.

Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.

Self-test 8K passed!

Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.

Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.

Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.

Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.

Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.

Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.

Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.

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

Volt og temp fra bios:

Vcore volt: 1.1-1.2v

CPU PLL volt: 1.6v

NB volt: 1.4v

DRAM volt: 2.19-2.2v

FSB termination volt: 1.18v

South bridge volt: 1.07v

DDR2 controller ref volt: 1.1v

SB 1.5v volt: 1.536v

3.3v volt: 3.248v

5v volt: 5.064v

12v volt: 12.040v

CPU temp: 30c

MB temp: 36c

NB temp: 44c

SB temp: 45c

Julepils · 11. juli 2008

Hva skulle den replyen der forestille?

Julepils · 14. juli 2008

Nå har det ikke vært blåskjerm på dag nummer 2 men hardware problemer som dette har hatt antydning til kan vel ikke bare forsvinne? Prøver å stresse den ut litt for å forårsake nytt kræsj.

Har snakket med komplett også men de tar jo nesten 600kr i timen for reperasjon og behandlingstid på 3 uker. Svarer seg mer for meg å bare kjøpe nye deler enn det der. : P

Poster oppsummering på alt her, begynner å bli tom for idèer:

PCen består av,

Kabinett: ZALMAN Z-MACHINE GT1000 Gaming, Alu, black, ATX, 3xfans (without PSU) (GT1000-BK) (fra multicom.no)

Hovedkort: Asus Maximus Formula, X38, Socket-775, DDR2,ATX,2xGbLAN,Firew, 2xPCI-Ex(2.0)x16 (fra komplett.no)

CPU: Intel Core™ 2 Duo E8500 3.16GHz, Socket LGA775, 6MB, 1333Mhz, BOXED w/fan (fra komplett.no)

Strømforsyning: Corsair Powersupply 750W Black, ATX/EPS, 140mm Fan, 8xSATA, SLI (fra komplett.no)

Skjermkort: PointOfView GeForce GTX 280 PCI-E 1024MB GDDR3 (R-VGA150910F) (fra multicom.no)

RAM: Corsair Dominator TWIN2X8500C5DF 4096MB, DDR2, 2x2GB(KIT), DHX, E.P.P, with FAN (fra komplett.no)

IDE-kontroller: Highpoint Rocket HPT302 UDMA/ATA133 Controller (fra komplett.no en gang i tiden)

Boot HDD: Samsung SpinPoint F1 750GB SATA2 32MB 7200RPM (fra komplett.no)

Jeg har prøvt følgende:

- Har prøvt forskjellige operativsystem (Windows XP SP2 x84, x64 og Windows Vista Ultimate SP1 x64 og x86 versjon).

- Har prøvt default bios instillinger og manual tweak instillinger med riktige volt/ram-instillinger.

- Har kjørt Hot CPU Tester Pro 4 Lite version, Primetest, Seatools og Memtest86+ uten feil (i flere timer på alle program).

- Har prøvt uten alle ekstratingene i maskinen som ikke trengs for å drive/boote.

- Har prøvt uten IDE kontrolleren.

- Har prøvt uten lydkortet som følgte med hovedkortet.

- Har prøvt 1 og 1 ram om gangen.

- Har sjekket og brukt siste utgitte drivere.

- Temperaturene skal også være ganske aktuelle.

- Bios er også flashet til 1201.

Dumper:

http://www.julepils.com/minidump.zip

http://www.julepils.com/minidump2.zip

Litt mer info om HK osv:

[b]Motherboard [/b]

Manufacturer ASUSTeK Computer INC. 
Product Name Maximus Formula 
Version Rev 1.xx 

[b]BIOS [/b]

Vendor American Megatrends Inc. 
BIOS Version 1201 
BIOS Release Date 04/23/2008 
BIOS ROM Size 2048 KBytes 



[b]CPU [/b]

Socket Designation LGA775 
Manufacturer Intel 
Version Intel® Core(tm)2 Duo CPU E8500 @ 3.16GHz 
Supported Voltage 1.2 v 
External Clock 333 MHz 
Max Speed 3800 MHz 
Current Speed 3166 MHz 


[b]Memory [/b]

Socket Designation DIMM0 
Current Speed Unknown 
Memory Type Unknown
Installed Size No Memory Installed 

Socket Designation DIMM1 
Current Speed 1872 MHz 
Memory Type DDR2 
Installed Size 2048 MBytes 

Socket Designation DIMM2 
Current Speed Unknown 
Memory Type Unknown 
Installed Size No Memory Installed 

Socket Designation DIMM3 
Current Speed 1872 MHz 
Memory Type DDR2 
Installed Size 2048 MBytes

Link til bilde av kræsj-info osv:

http://www.julepils.com/report.jpg

Endret 14. juli 2008 av Julepils

lucky666 · 14. juli 2008

Har du sjekket spacerne bak hovedkortet, slik at det ikke er satt en spacer feil og jorder på kortet? Eller at det ligger en skrue el. bak kortet og jorder?

Julepils · 14. juli 2008

Ugh ukjent begrep for meg, Spacer - hvordan sjekke/se/ser ut?

Er det den der dibbedutten som står fast i kabinettet og er mellom det og hovedkortet hvor skruen går i?

lucky666 · 15. juli 2008

Spacer er "avstandshylsene" mellom hovedkortet og kabinettet.

Julepils · 15. juli 2008

http://www.julepils.com/2008-07-15.zip

Alt virker så stabilt ut ifra tester også at dette her opplegget bare skjærer hjertet. : P

Blir det å bestille hovedkort eller ny ram for drastisk?

Tror isåfall det blir MSI Mainboard S-775 P45 ATX 2xPCI-E Audio GbLAN 2x1394 SATA-II Raid DDR2 Retail (P45 PLATINUM) og eller evt. G.SKILL 4GB DDR2 Kit (2x2GB) PC2-8500 Non-ECC CL5 (F2-8500CL5D-4GBPI)

Endret 15. juli 2008 av Julepils

Logg inn

Problemer med plutselig blåskjerm

Anbefalte innlegg

Julepils

Lenke til kommentar

Videoannonse

Mr_Tiger

Lenke til kommentar

Julepils

Lenke til kommentar

Julepils

Lenke til kommentar

lucky666

Lenke til kommentar

Julepils

Lenke til kommentar

lucky666

Lenke til kommentar

Julepils

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Hvem er aktive 0 medlemmer