Problemer med plutselig blåskjerm

Julepils · 21. juni 2008

Evenin

Jeg har nettopp satt isammen min nye maskin.

Speccs:

1 Asus Maximus Formula, X38, Socket-775, DDR2,ATX,2xGbLAN,Firew, 2xPCI-Ex(2.0)x16

1 Intel Core? 2 Duo E8500 3.16GHz, Socket LGA775, 6MB, 1333Mhz, BOXED w/fan

1 Zalman CNPS9700 NT Ultra Quiet CPU Kjøler, Socket 775/754/939/940/AM2

1 OCZ Freeze Extreme Thermal Kjølepasta, 3 gram

1 Corsair Powersupply 750W Black, ATX/EPS, 140mm Fan, 8xSATA, SLI

1 Corsair Dominator TWIN2X8500C5DF 4096MB, DDR2, 2x2GB(KIT), DHX, E.P.P, with FAN

1 Samsung SpinPoint F1 750GB SATA2 32MB 7200RPM

point of view nvidia gtx 280

Jeg installerte først Windows Vista Ultimate x64 versjonen på samsung spintpoint f1 sata harddisken, installerte driverene til hovedkortet og så skjermkortet. Når jeg prøver å installere Age of Conan eller prøver å spille noe så kommer blåskjermen. Eller helt tilfeldig ellers når jeg holder på med flere ting.

Etter mye stressing med å finne resten av alle harddiskene mine på Rocket IDE kontrolleren og etter et par blåskjermer til så leste jeg litt og forandret mhz til 1066mhz i bios på rammen og satt volten til 2.1v.

Etter litt så innstallerte jeg heller Windows XP SP2 x64 edition, samme rutine med install av hovedkort drivere og så skjermkort. Samme resultat med plutselig blåskjerm. Etterpå så fikk jeg tak i memtest og har hatt det på nå mens jeg skriver fra bærbaren og 0 errors/feil på det hvertfal.

Har også satt nb volt til 1.4v.

Any ideas?

Mvh, Julepilsen.

lommerusk · 21. juni 2008

Prøv det som blir anbefalt her og se om det hjelper: http://forumet.no/index.php?showtopic=63124

Julepils · 21. juni 2008

Har sett på den tråden der ja men som du ser i beskrivelsen min så er det vel egentlig mer eller mindre det som står der at jeg har gjort. Bortsett fra å ta ut 1x 2g rambrikke og teste 1 om gangen. Hvordan fungerer forresten det med 2gb ram med 64bit?

Julepils · 22. juni 2008

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?

Endret 14. juli 2008 av Julepils

Julepils · 22. juni 2008

Har nå også kjørt Hot CPU Tester Pro 4 Lite version:

Hot CPU Tester Pro(Lite Edition) 4.4.1

Sunday, June 22, 2008 - 18:13:16

Diagnostic Report

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

Test Started at: 17:52:12

Test Duration: 00:20:36

Physical Processors Available: 2

Logical Processors Available: 2

Multi-Processors System(SMP): Available

Hyper-Threading Technology: Not Available

CPU Name String: Intel® Core2 Duo CPU E8500 @ 3.16GHz

Speed: 3173MHz

Logical Processors Tested: CPU 0, CPU 1

Average CPU(s) Performance: 100.0%

Modules Results:

Complex Matrix: Finished without error

Calculating Pi: Finished without error

Sorting Algorithms: Finished without error

Prime Test: Finished without error

Fast Fourier Transforms:

Chipset:

L1 Cache:

L2 Cache:

Memory: Finished without error

HD: Finished without error

MMX: Finished without error

SSE:

SSE2/SSE3:

3DNow!:

og bench, ikke at det sikkert har noen betydning men, med samme program:

Hot CPU Tester Pro(Lite Edition) 4.4.1 - Benchmark Result

Sunday, June 22, 2008 - 18:28

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

Overall : 13972

MetaBench to MHz ratio : 4.40

Integer Instructions : 1,223 M Instructions/s

Floating-point Instructions : 1,046 M Instructions/s

MMX Instructions : 1,551 M Instructions/s

SSE Instructions : 480 M Instructions/s

SSE2 Instructions : 445 M Instructions/s

3DNow! Instructions : N/A M Instructions/s

Memory fillrate memcpy method : 3,764 MB/s

Memory fillrate C++ method : 3,678 MB/s

Memory rep movsd : 3,764 MB/s

Memory FPU 8 bytes blocks : 3,678 MB/s

Memory Assembly 4 bytes blocks : 3,678 MB/s

Memory Assembly 8 bytes blocks : 3,595 MB/s

Memory fillrate MMX 8 bytes blocks : 3,678 MB/s

Memory fillrate MMX 16 bytes blocks : 3,595 MB/s

Memory fillrate SSE 16 bytes blocks : 3,636 MB/s

Memory fillrate SSE movntq 8 bytes blocks : 6,274 MB/s

Memory fillrate SSE movntq 16 bytes blocks : 6,400 MB/s

Memory fillrate SSE prefetch movntq 16 bytes blocks : 6,274 MB/s

Memory fillrate SSE movntps 16 bytes blocks : 6,400 MB/s

Memory fillrate SSE prefetch movntps 32 bytes blocks : 6,274 MB/s

Memory fillrate SSE2 prefetch movntps 16 bytes blocks : 3,636 MB/s

Insertion Sort : 105 K Items/s

Shell Sort : 2,485 K Items/s

Merge Sort : 4,739 K Items/s

Heap Sort : 3,516 K Items/s

Quick Sort : 9,661 K Items/s

Large Objects Sort : 3,019 K Items/s

Fast Fourier Transformg (Standard) : 5,832 KB/s

Fast Fourier Transformg (Optimized) : 17,316 KB/s

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

Kan det hende at det er Hovedkortet som er problemet?

Er litt usikker på hvordan jeg kan finne utav akkurat det?

Endret 22. juni 2008 av Julepils

Julepils · 22. juni 2008

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.]

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

Endret 14. juli 2008 av Julepils

Julepils · 22. juni 2008

Enda ingen tilbakemelding på denne tråden og heller enda ikke funnet løsningen.

Jeg tok som sagt ut Highpoint rocket kontrolleren og alle 4x ide diskene. Tok også ut noe annet ekstra greier som USB porter osv.

Fungerte en god stund, fikk for første gang til å installere hele Age of Conan også. Men etter en god stund så plutselig poffet det fram en blåskjerm. Restartet. Poff enda en ny blåskjerm.

Har nå tatt ut 1x 2gb ram brikke for å se om det er noe mer stabilt.

Har også loadet default settings i bios men satt på rammen som DDR2-1066mhz da det står anbefalt i hovedkortets manual.

Noe merkelig var at når jeg startet den opp igjen nå så stod det at den hadde funnet noe ny hardware - en floppydisc. Hah, har da ingen floppy koblet til jeg.

Her er de 2 nye dumpene, paste fra windbg:

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

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062208-03.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 20:39:40.109 2008 (GMT+2)
System Uptime: 0 days 1:47:35.958
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
..........................................................................................
...........................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8002718200, 0, fffffadf8f349813, 0}

Unable to load image 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

Could not read faulting driver name
Probably caused by : nv4_mini.sys ( nv4_mini+92813 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8002718200, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffadf8f349813, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  fffffa8002718200 

FAULTING_IP: 
nv4_mini+92813
fffffadf`8f349813 8b0c88          mov     ecx,dword ptr [rax+rcx*4]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  nvcplui.exe

CURRENT_IRQL:  1

TRAP_FRAME:  fffffadf8c9044c0 -- (.trap 0xfffffadf8c9044c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8001f84200 rbx=0000000000100000 rcx=00000000001e5000
rdx=0000000000795000 rsi=fffffadf9bdf2660 rdi=0000000000000002
rip=fffffadf8f349813 rsp=fffffadf8c904650 rbp=0000000000100000
r8=00000000000ff86b  r9=0000000000000269 r10=0000000000000000
r11=00000000000007ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nv4_mini+0x92813:
fffffadf`8f349813 8b0c88          mov     ecx,dword ptr [rax+rcx*4] ds:fffffa80`02718200=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800010a6072 to fffff8000102e890

STACK_TEXT:  
fffffadf`8c9043e8 fffff800`010a6072 : 00000000`00000050 fffffa80`02718200 00000000`00000000 fffffadf`8c9044c0 : nt!KeBugCheckEx
fffffadf`8c9043f0 fffff800`0102d459 : 00000127`00000083 0000012b`00000083 000003b2`00000200 000003b6`00000083 : nt!MmAccessFault+0xa1f
fffffadf`8c9044c0 fffffadf`8f349813 : fffffadf`00000001 00000000`00000030 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
fffffadf`8c904650 fffffadf`00000001 : 00000000`00000030 00000000`00000000 00000000`00000000 00000028`00000000 : nv4_mini+0x92813
fffffadf`8c904658 00000000`00000030 : 00000000`00000000 00000000`00000000 00000028`00000000 00000000`00000000 : 0xfffffadf`00000001
fffffadf`8c904660 00000000`00000000 : 00000000`00000000 00000028`00000000 00000000`00000000 fffffadf`9c4e1450 : 0x30
fffffadf`8c904668 00000000`00000000 : 00000028`00000000 00000000`00000000 fffffadf`9c4e1450 fffffadf`9a5b7070 : 0x0
fffffadf`8c904670 00000028`00000000 : 00000000`00000000 fffffadf`9c4e1450 fffffadf`9a5b7070 fffffadf`9c4e1450 : 0x0
fffffadf`8c904678 00000000`00000000 : fffffadf`9c4e1450 fffffadf`9a5b7070 fffffadf`9c4e1450 fffffadf`8f373600 : 0x28`00000000
fffffadf`8c904680 fffffadf`9c4e1450 : fffffadf`9a5b7070 fffffadf`9c4e1450 fffffadf`8f373600 fffffadf`2020564e : 0x0
fffffadf`8c904688 fffffadf`9a5b7070 : fffffadf`9c4e1450 fffffadf`8f373600 fffffadf`2020564e fffffadf`9bbd4010 : 0xfffffadf`9c4e1450
fffffadf`8c904690 fffffadf`9c4e1450 : fffffadf`8f373600 fffffadf`2020564e fffffadf`9bbd4010 fffffadf`9bdf2660 : 0xfffffadf`9a5b7070
fffffadf`8c904698 fffffadf`8f373600 : fffffadf`2020564e fffffadf`9bbd4010 fffffadf`9bdf2660 fffffadf`9bdf6380 : 0xfffffadf`9c4e1450
fffffadf`8c9046a0 fffffadf`2020564e : fffffadf`9bbd4010 fffffadf`9bdf2660 fffffadf`9bdf6380 00000001`00000000 : nv4_mini+0xbc600
fffffadf`8c9046a8 fffffadf`9bbd4010 : fffffadf`9bdf2660 fffffadf`9bdf6380 00000001`00000000 fffffadf`9a5b7000 : 0xfffffadf`2020564e
fffffadf`8c9046b0 fffffadf`9bdf2660 : fffffadf`9bdf6380 00000001`00000000 fffffadf`9a5b7000 fffffadf`9bbd4010 : 0xfffffadf`9bbd4010
fffffadf`8c9046b8 fffffadf`9bdf6380 : 00000001`00000000 fffffadf`9a5b7000 fffffadf`9bbd4010 00000000`00001010 : 0xfffffadf`9bdf2660
fffffadf`8c9046c0 00000001`00000000 : fffffadf`9a5b7000 fffffadf`9bbd4010 00000000`00001010 00000000`00000000 : 0xfffffadf`9bdf6380
fffffadf`8c9046c8 fffffadf`9a5b7000 : fffffadf`9bbd4010 00000000`00001010 00000000`00000000 fffffadf`8f3553a0 : 0x1`00000000
fffffadf`8c9046d0 fffffadf`9bbd4010 : 00000000`00001010 00000000`00000000 fffffadf`8f3553a0 00000000`00100000 : 0xfffffadf`9a5b7000
fffffadf`8c9046d8 00000000`00001010 : 00000000`00000000 fffffadf`8f3553a0 00000000`00100000 00000000`00800078 : 0xfffffadf`9bbd4010
fffffadf`8c9046e0 00000000`00000000 : fffffadf`8f3553a0 00000000`00100000 00000000`00800078 00000000`00800078 : 0x1010
fffffadf`8c9046e8 fffffadf`8f3553a0 : 00000000`00100000 00000000`00800078 00000000`00800078 00000000`00000001 : 0x0
fffffadf`8c9046f0 00000000`00100000 : 00000000`00800078 00000000`00800078 00000000`00000001 fffffadf`9a5b7000 : nv4_mini+0x9e3a0
fffffadf`8c9046f8 00000000`00800078 : 00000000`00800078 00000000`00000001 fffffadf`9a5b7000 fffffadf`8f2ecf97 : 0x100000
fffffadf`8c904700 00000000`00800078 : 00000000`00000001 fffffadf`9a5b7000 fffffadf`8f2ecf97 00000000`00000010 : 0x800078
fffffadf`8c904708 00000000`00000001 : fffffadf`9a5b7000 fffffadf`8f2ecf97 00000000`00000010 00000000`00000286 : 0x800078
fffffadf`8c904710 fffffadf`9a5b7000 : fffffadf`8f2ecf97 00000000`00000010 00000000`00000286 fffffadf`8c904748 : 0x1
fffffadf`8c904718 fffffadf`8f2ecf97 : 00000000`00000010 00000000`00000286 fffffadf`8c904748 00000000`00000018 : 0xfffffadf`9a5b7000
fffffadf`8c904720 00000000`00000010 : 00000000`00000286 fffffadf`8c904748 00000000`00000018 fffffadf`8c904758 : nv4_mini+0x35f97
fffffadf`8c904728 00000000`00000286 : fffffadf`8c904748 00000000`00000018 fffffadf`8c904758 fffffadf`8f3461f4 : 0x10
fffffadf`8c904730 fffffadf`8c904748 : 00000000`00000018 fffffadf`8c904758 fffffadf`8f3461f4 fffffadf`8c9047a0 : 0x286
fffffadf`8c904738 00000000`00000018 : fffffadf`8c904758 fffffadf`8f3461f4 fffffadf`8c9047a0 00000000`00800078 : 0xfffffadf`8c904748
fffffadf`8c904740 fffffadf`8c904758 : fffffadf`8f3461f4 fffffadf`8c9047a0 00000000`00800078 00000000`00000000 : 0x18
fffffadf`8c904748 fffffadf`8f3461f4 : fffffadf`8c9047a0 00000000`00800078 00000000`00000000 00000000`00000040 : 0xfffffadf`8c904758
fffffadf`8c904750 fffffadf`8c9047a0 : 00000000`00800078 00000000`00000000 00000000`00000040 00000000`00000001 : nv4_mini+0x8f1f4
fffffadf`8c904758 00000000`00800078 : 00000000`00000000 00000000`00000040 00000000`00000001 fffffadf`8f3550d1 : 0xfffffadf`8c9047a0
fffffadf`8c904760 00000000`00000000 : 00000000`00000040 00000000`00000001 fffffadf`8f3550d1 fffffadf`8c9047a0 : 0x800078
fffffadf`8c904768 00000000`00000040 : 00000000`00000001 fffffadf`8f3550d1 fffffadf`8c9047a0 fffffadf`00800078 : 0x0
fffffadf`8c904770 00000000`00000001 : fffffadf`8f3550d1 fffffadf`8c9047a0 fffffadf`00800078 00000000`31415929 : 0x40
fffffadf`8c904778 fffffadf`8f3550d1 : fffffadf`8c9047a0 fffffadf`00800078 00000000`31415929 fffffadf`8f345cbc : 0x1
fffffadf`8c904780 fffffadf`8c9047a0 : fffffadf`00800078 00000000`31415929 fffffadf`8f345cbc fffffadf`9a5b7000 : nv4_mini+0x9e0d1
fffffadf`8c904788 fffffadf`00800078 : 00000000`31415929 fffffadf`8f345cbc fffffadf`9a5b7000 fffffadf`8c9047b0 : 0xfffffadf`8c9047a0
fffffadf`8c904790 00000000`31415929 : fffffadf`8f345cbc fffffadf`9a5b7000 fffffadf`8c9047b0 00000000`00000000 : 0xfffffadf`00800078
fffffadf`8c904798 fffffadf`8f345cbc : fffffadf`9a5b7000 fffffadf`8c9047b0 00000000`00000000 fffffadf`9bbd4010 : 0x31415929
fffffadf`8c9047a0 fffffadf`9a5b7000 : fffffadf`8c9047b0 00000000`00000000 fffffadf`9bbd4010 fffffadf`9bdf2660 : nv4_mini+0x8ecbc
fffffadf`8c9047a8 fffffadf`8c9047b0 : 00000000`00000000 fffffadf`9bbd4010 fffffadf`9bdf2660 fffffadf`9bdf6380 : 0xfffffadf`9a5b7000
fffffadf`8c9047b0 00000000`00000000 : fffffadf`9bbd4010 fffffadf`9bdf2660 fffffadf`9bdf6380 00000001`00000000 : 0xfffffadf`8c9047b0
fffffadf`8c9047b8 fffffadf`9bbd4010 : fffffadf`9bdf2660 fffffadf`9bdf6380 00000001`00000000 fffffadf`8c904910 : 0x0
fffffadf`8c9047c0 fffffadf`9bdf2660 : fffffadf`9bdf6380 00000001`00000000 fffffadf`8c904910 fffffadf`8c904910 : 0xfffffadf`9bbd4010
fffffadf`8c9047c8 fffffadf`9bdf6380 : 00000001`00000000 fffffadf`8c904910 fffffadf`8c904910 00000000`00000000 : 0xfffffadf`9bdf2660
fffffadf`8c9047d0 00000001`00000000 : fffffadf`8c904910 fffffadf`8c904910 00000000`00000000 00000000`00000000 : 0xfffffadf`9bdf6380
fffffadf`8c9047d8 fffffadf`8c904910 : fffffadf`8c904910 00000000`00000000 00000000`00000000 fffffadf`8f2fe516 : 0x1`00000000
fffffadf`8c9047e0 fffffadf`8c904910 : 00000000`00000000 00000000`00000000 fffffadf`8f2fe516 fffffadf`8c904910 : 0xfffffadf`8c904910
fffffadf`8c9047e8 00000000`00000000 : 00000000`00000000 fffffadf`8f2fe516 fffffadf`8c904910 fffffadf`8f374594 : 0xfffffadf`8c904910
fffffadf`8c9047f0 00000000`00000000 : fffffadf`8f2fe516 fffffadf`8c904910 fffffadf`8f374594 fffffadf`9c74cac0 : 0x0
fffffadf`8c9047f8 fffffadf`8f2fe516 : fffffadf`8c904910 fffffadf`8f374594 fffffadf`9c74cac0 fffffadf`9c773610 : 0x0
fffffadf`8c904800 fffffadf`8c904910 : fffffadf`8f374594 fffffadf`9c74cac0 fffffadf`9c773610 00000000`00000001 : nv4_mini+0x47516
fffffadf`8c904808 fffffadf`8f374594 : fffffadf`9c74cac0 fffffadf`9c773610 00000000`00000001 fffffadf`00000000 : 0xfffffadf`8c904910
fffffadf`8c904810 fffffadf`9c74cac0 : fffffadf`9c773610 00000000`00000001 fffffadf`00000000 00000000`00000000 : nv4_mini+0xbd594
fffffadf`8c904818 fffffadf`9c773610 : 00000000`00000001 fffffadf`00000000 00000000`00000000 00000000`31415929 : 0xfffffadf`9c74cac0
fffffadf`8c904820 00000000`00000001 : fffffadf`00000000 00000000`00000000 00000000`31415929 00000000`00000000 : 0xfffffadf`9c773610
fffffadf`8c904828 fffffadf`00000000 : 00000000`00000000 00000000`31415929 00000000`00000000 fffffadf`8f5bbc42 : 0x1
fffffadf`8c904830 00000000`00000000 : 00000000`31415929 00000000`00000000 fffffadf`8f5bbc42 fffffadf`8c9048d8 : 0xfffffadf`00000000
fffffadf`8c904838 00000000`31415929 : 00000000`00000000 fffffadf`8f5bbc42 fffffadf`8c9048d8 00000000`dada970d : 0x0
fffffadf`8c904840 00000000`00000000 : fffffadf`8f5bbc42 fffffadf`8c9048d8 00000000`dada970d fffffadf`9c74cac0 : 0x31415929
fffffadf`8c904848 fffffadf`8f5bbc42 : fffffadf`8c9048d8 00000000`dada970d fffffadf`9c74cac0 fffffadf`8c9049f0 : 0x0
fffffadf`8c904850 fffffadf`8c9048d8 : 00000000`dada970d fffffadf`9c74cac0 fffffadf`8c9049f0 00000000`0000003e : nv4_mini+0x304c42
fffffadf`8c904858 00000000`dada970d : fffffadf`9c74cac0 fffffadf`8c9049f0 00000000`0000003e 00000000`00000010 : 0xfffffadf`8c9048d8
fffffadf`8c904860 fffffadf`9c74cac0 : fffffadf`8c9049f0 00000000`0000003e 00000000`00000010 00000000`c1d0000c : 0xdada970d
fffffadf`8c904868 fffffadf`8c9049f0 : 00000000`0000003e 00000000`00000010 00000000`c1d0000c 00000000`31415929 : 0xfffffadf`9c74cac0
fffffadf`8c904870 00000000`0000003e : 00000000`00000010 00000000`c1d0000c 00000000`31415929 00000000`00001010 : 0xfffffadf`8c9049f0
fffffadf`8c904878 00000000`00000010 : 00000000`c1d0000c 00000000`31415929 00000000`00001010 fffffadf`8f2fe98c : 0x3e
fffffadf`8c904880 00000000`c1d0000c : 00000000`31415929 00000000`00001010 fffffadf`8f2fe98c fffffa80`00001f80 : 0x10
fffffadf`8c904888 00000000`31415929 : 00000000`00001010 fffffadf`8f2fe98c fffffa80`00001f80 fffffadf`900a54ec : 0xc1d0000c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_mini+92813
fffffadf`8f349813 8b0c88          mov     ecx,dword ptr [rax+rcx*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nv4_mini+92813

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME:  nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4835ec7d

FAILURE_BUCKET_ID:  X64_0x50_nv4_mini+92813

BUCKET_ID:  X64_0x50_nv4_mini+92813

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

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062208-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: 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 20:41:47.125 2008 (GMT+2)
System Uptime: 0 days 0:00:58.970
*** 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 : 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: fffffadf90881240
Arg3: 00000000b6200016
Arg4: 0000000000080a01

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

PROCESS_NAME:  svchost.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`000e4880 fffffadf`90881570 : hal!HalHandleMcheck+0x12c
fffffadf`90881370 fffff800`0102d975 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
fffffadf`908814f0 000007ff`7fd4d4af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
00000000`07e3e098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7fd4d4af


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

---------

Det jeg la merke til var at det står noe om nv4_mini.sys og det trodde jeg var noe med skjermkortet? Eller? Bilde fra GPU-Z: http://img516.imageshack.us/my.php?image=gpuzsz2.jpg

Endret 14. juli 2008 av Julepils

lommerusk · 22. juni 2008

Prøv å sett NB volt til 1.5

Julepils · 23. juni 2008

Det jeg gjorde var å ta ut alle harddiskene (kontrolleren) og 1x 2gb ram brikke i tillegg til å sette default i bios (bortsett fra mhzen osv). Den er stabil som bare det nå sånn sett, fikk Age of Conan opp på 180 fps så jeg har kost meg litt i kveld.

Men jeg får vel finne utav om det var ram'en eller highpoint kontrolleren. Ugh. Får vel enten sette i ram'en igjen å se om det holder.

snippsat · 23. juni 2008

Den slo på win sin filer også en gang på skjermkortet sine filer.

Der tyder på at hardware er ustabil.

Bios bør du oppgaradere til nyeste.

Alltid viktig for 4gb minne.

Du siere du har kjørt mestest ikke hvilken.

Har tatt dette en del ganger før,tar bare og kopiere en jeg har skrevet før.

Vi får starte med med det som alltid skal gjøres først.

Bios bør være ny når det gjelder 4gb.

P.g.a at det kommer fix for minne 4gb i nyere bioser.

I bios skal minne settes manuelt og teste med memtest86+ 2.01

Alltid finne korrekt info om minnet.

http://www.corsair.com/_datasheets/TW3X4G1600C9DHXNV.pdf

DDR mzh 1600(er 800mzh cpu-z)

Dram voltage:1.9v-->her setter vi en litt over det den skal kjøre på som er 1.8v(ikke feil kan du prøve på 1.8v)

NB Core Voltage: 1.4v-->viktig og øke denne litt for 4gb.

tCL 9 (CAS Latency 9)-->timings for ditt minne.

tRCD 9

tRP 9

tRAS 24

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 boote memtest86+ fra diskett-cd-usb det link til alle typer boot muligheter.

http://www.memtest.org/

Når det gjelder testing med memtest86+ la den kjøre alle 9 tester et par ganger.

Får du feil stopp teste 1 og 1 brikke.

Får du noen feil i test 5 øk spennin minnet litt.

Ja litt basic,dette må være iorden.

Ikke feil her feilsøker man videre.

Når det gjelder bluescreen må du skrive ned stopcoden.

Dette kan gi en indikasjon fra hvor feilen kommer fra.

Kan ta mere om feilsøking av bluescreen senere,med bruk av windbg og analysere minidump kan man finne eksakt fra hvor feilen kommer fra.

Når det gjelder hardisk så kan du teste den før win booter bruk utimatbootcd.

Velg test ut ifra produsent av hdd.

Det er viktig og få testet så mye så mulig før man begynner og innstalere win

Endret 23. juni 2008 av SNIPPSAT

Julepils · 23. juni 2008

Jeg har kjørt memtest: ** Memtest86+ V2.01 (21/02/2008) **

Og BIOS'en er faktisk siste versjon fra orginalt av, faktisk. : p

Btw jeg har nå satt tilbake den ene ram brikken som jeg tok ut, oppdaterer conan nå og skal kjøre igang litt så får jeg se om den holder seg stabilt eller ikke. Og om den skulle holde seg stabilt og vise seg at ram'en er grei så må det da egentlig være HighPoint Rocket 133 IDE kontrolleren som var feilen.

Endret 23. juni 2008 av Julepils

Julepils · 23. juni 2008

PCen kræsjet etter en stund da jeg hadde plassert tilbake minnebrikken som jeg tok ut. Så da tyder det på at det er noe med ram'en, om det er BIOS instillinger eller bare ram'en som er "defekt" på et vis har jeg ingen anelse om.

Håper det er noen her som har idèer?

Har det noe å si om hvor ram'en er plassert i hovedkortet?

Forstod ikke helt det som stod i manualen sånn sett om plassering.

Endret 23. juni 2008 av Julepils

Sertito · 23. juni 2008

Blå skjerm skjer oftest fordi dataen overopphetes. Prøv å plassere så evt. vifter ikke går inn i veggen og at pc'en står et "fritt" sted. enkel løsning som langt ifra trenger så mange avanserte svar.

Julepils · 23. juni 2008

Nei men så tviler jeg sterkt på at du har lest noe av det som står ovenfor..

lommerusk · 23. juni 2008

Prøvde du å sette NB volt til 1.5

Julepils · 23. juni 2008

http://img292.imageshack.us/my.php?image=rammhkbd3.jpg ugh? populated er der den burde sitte?

NB volt lå på ca 1.44v

lommerusk · 23. juni 2008

Brikkene skal stå i de blå slotene

snippsat · 23. juni 2008

Du har 2 brikker da skal du bruke dimm_a1 + dimm_b1

Dette er for at dualchannel skal virke.

Ja eller lik farge som poster over

Endret 23. juni 2008 av SNIPPSAT

lucky666 · 23. juni 2008

Sett Transaction Booster til "disable 0 eller 1.Husk også at hovedkortet overvolter på ram,og 2.1v som du har satt,nok er nærmere 2.2v.Sett 2.02v-2.04v.

Overklokker du ikke,sett NB til auto.Blir veldig fort ustabilt på dette kortet med for høy NB spenning.

Julepils · 24. juni 2008

Hehe, synd at jeg ikke får rammen presset i A1 slotten... cpuvifta sin klemme er iveien. : P

Men kan det forårsake blåskjermen ved at rammen stod i dimmB1 og dimmB2?

Problemer med plutselig blåskjerm

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

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