Restarts

[Smooth*{MEOW}*]

I ran memtest, no problems there.  Haven't swapped sticks yet.  Idle voltages are at:

vcore = 1.47
+3.3 = 3.33
+5 = 5.13
+12 = 12.22-12.35

Also looking into doing a BIOS update.  Mine is at 0903, there are 2 newer versions, 1009 and 1103.

[Smooth*{MEOW}*]

I noticed this also.  The little red light next to "surge" is on.  Think I could be running too much juice through this thing?  Everything for my computer goes through there, nothing else.

[Raidien{MEOW}]

definitely possible... however, i don't have any problems with mine and my surge protector (which is full) is daisy-chained into my UPS (which is also full) and then that plugs into just 1 outlet :P but it's possibly that maybe there is an electrical leak somewhere if the outlet isn't getting enough power or such...

[THE PEARL]

ROFL!!! A ELECTRICAL LEAK??? THATS JUST TOO FREAKIN FUNNY. HEY SMOOTH, SURGE PROTECTOR OVER A BUCKET. THAT WAY YOU WONT LOSE ANY OF THE ELECTRICITY THAT MAY "LEAK" OUT.

  THE PEARL-MEOW-

[Raidien{MEOW}]

of course... then you can re-use the electricity  <smiletongue>

[Smooth*{MEOW}*]

What leak?  I'm just wondering if that thing is doing it's job, I've had it for over 5 years now.

[THEKATZ*{MEOW}*]

Well,  I am thinking that surge has been expired.  Not all surge protectors last for ever.  As a matter of fact, usually when the strip has a fault, it is no longer able to protect you against another surge.  That red light may be telling you that a fault has occurred and you need to reset or replace the SP.

[Smooth*{MEOW}*]

That's what I'm thinking too TK, it's been through quite a few outages.

[Jugulator*{MEOW}*]

some surge protectors have lights to indicate that the thing has self destructed in the course of protection.
in this event the thing cannot protect against a similar surge again.
if the light was off when it was new then that is what its telling you.
if it was on when it was new then its telling you that its still working.
the big one we have at work that protects our whole system, has two red light that mean its working.

[Smooth*{MEOW}*]

I'm trying to get a look at these minidump files.  Installed the support tools from the Windows cd.  Tried to open one of the files with dumpchk.exe and it won't open.  I see a DOS window for a fraction of a second then it closes.  Also, I've disabled the auto-restart on error feature.  Now I get a BSOD with IRQ NOT LESS THAN OR EQUAL.

[Smooth*{MEOW}*]

I changed the sticks around, put stick 1 into slot 2 and vice versa.  I'll run it like that for a while and see what I get.  I'm thinking this is more of a driver issue.

[Smooth*{MEOW}*]

Got dumpcheck working, here's the analysis from the latest one:

C:\Program Files\Support Tools>dumpchk y c:\windows\minidump\mini032406-03.dmp
Loading dump file c:\windows\minidump\mini032406-03.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  17f60160
PfnDataBase         81800000
PsLoadedModuleList  805531a0
PsActiveProcessHead 80559258
MachineImageType    0000014c
NumberProcessors    00000001
BugCheckCode        1000000a
BugCheckParameter1  8058a000
BugCheckParameter2  000000ff
BugCheckParameter3  00000000
BugCheckParameter4  805315ce
PaeEnabled          00000001
KdDebuggerDataBlock 80544ce0
MiniDumpFields      00000dff

TRIAGE_DUMP32:
ServicePackBuild      00000200
SizeOfDump            00010000
ValidOffset           0000fffc
ContextOffset         00000320
ExceptionOffset       000007d0
MmOffset              00001068
UnloadedDriversOffset 000010a0
PrcbOffset            00001878
ProcessOffset         000024c8
ThreadOffset          00002728
CallStackOffset       00002980
SizeOfCallStack       0000094c
DriverListOffset      00003560
DriverCount           000000a0
StringPoolOffset      000064e0
StringPoolSize        00001648
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            baaa76b4
DebuggerDataOffset    000032d0
DebuggerDataSize      00000290
DataBlocksOffset      00007b28
DataBlocksCount       00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Mar 24 22:46:58 2006
System Uptime: 0 days 0:03:44
start    end        module name
804d7000 806cd280   nt             Checksum: 001F632B  Timestamp: Tue Mar 01 19:
34:37 2005 (42250A1D)

Unloaded modules:
ad8f2000 ad8fd000   imapi.sys    Timestamp: unavailable (00000000)
ad902000 ad90b000   processr.sys    Timestamp: unavailable (00000000)
add59000 add5e000   Cdaudio.SYS    Timestamp: unavailable (00000000)
adffb000 adffe000   Sfloppy.SYS    Timestamp: unavailable (00000000)

Finished dump check

[THEKATZ*{MEOW}*]

Smooth, is it possible that you have the wrong setting in BIOS for the memory you have installed?  Time stamps not found would be the reason I am asking.  Are you overclocked?

[Smooth*{MEOW}*]

No overclocking, I haven't changed any memory settings since I built it.  The ram is specified to run at 2-3-2-5 timings, my systems detects and runs it at 2.5-3-2-5.  Getting some help here as well:

http://www.gamerstech.org/forum/index.php?topic=524.new;boardseen#new