Windows XP Reboot

I have the following system:

Albatron 865PE Pro II motherboard
Intel 3.00 GHZ cpu w/high speed variable fan
4 sticks of Geil DDR 512 mb memory
1 Maxtor 120 gb harddrive
1 Maxtor 160 gb harddrive
Windows XP w/SP2 and all subsequent updates
Windows 2003 Office Suite W/all updates
various other software

Problem:
I can be using any of the software or an the internet, or looking at pictures - in others words, there is not set pattern and you never know when it happens - but my system will display a black screen and then reboot.

Then I can work for 1 hour or half a day or 1 week or 2 weeks before it does it again. I have tried writing down what I do and what I use inbetween the auto-reboots, but cannot find a pattern as to what would be causing it.

I can reboot my system 2 or 3 times a day, myself, but then 10 minutes later or 1 hour later, etc.. my system will display the black screen and then reboot and then it stats all over again.

Any help or suggestions would be appreciated.


6 months of fustration,
RwsRichard

 

Hmmmm could be a driver problem, could be a problem with ram, could be a problem with just the cables inside your case, you tried these 3?

Giving Memtest a try wouldn't hurt, can download from MG in memory apps.

 

Go to system properties.

Right click my computer >properties. Click on the advanced tab and then settings under Startup and Recovery.

Under system failure, uncheck, automatically restart.

Click OK all the way out. Next time you have a problem, a blue screen will come up. Take note of the error message, verbatim!

Then manually reboot your computer and post here what it said.

 

Downloaded Memtest86, but when I unzipped it, a file was created for Easy CD Creator Classic. When I click on this up pops Easy Cd Creator Classic, wanting to know what files need to be backed up. Can't figure out to work with the .ISO file..


RwsRichard

 

I did all this and will repost when it happens again.

Thanks,
RwsRichard

 

Ok here is what the blue screen said:

A problem has been detected and windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue (I omitted the rest of this, because it is about 3 paragraphs long telling how to boot in SAFE MODE to disable new hardware and software and how to shut off CACHING and SHADOWING in the BIOS)

Technical Information:

*** STOP: 0x00000050 (0xFFFDE086, 0x00000001, 0XBF8E16D2, 0x00000000)

*** win32k.sys - address BFBE16D2 base at BF800000, DATESTAMP 41107F7A

There was also a dump created. Do not know how to edit it. It's size is 88k.


RwsRichard

 

What were you doing at the time this happened?

 

Running McAfee Virusscan on my whole system.




RwsRichard

 

Figured out how to get output from dump. It requires running two programs to figure out the which program caused the problem: Dumpchk.exe and Pstat.exe.

Dumpchk displays the dump in a readable format. These following fields are required to figure out which program is causing the problem:
BugCheckCode
BugCheckParameter1
BugCheckParameter2
BugCheckParameter3
BugCheckParameter4

ExceptionCode
ExceptionFlags
ExceptionAddress

But when I run dumpchk, I do not get the ExceptionCode, ExceptionFlags and the ExeceptionAddress. Without these, I cannot figure out which program is causing the problem.

According to Microsoft, the ExceptionAddress is "within" the program that caused the problem.

When you run pstat it displays the programs with their StartingAddress. You compare the ExeceptionAddress with the StartingAddress and you can figure out which program is the culprit, supposedly

Any suggestions?

 

Post the memory dumps from your C:\windows\minidump directory.

I don't understand what you are saying. I really, really doubt that dumpchk.exe is responsible for this.

 

could this be a simple heat issue? -ie: could the pcu fan be messed up/not working?
Yours,
522.

 

Here is the dump using dumpchk.exe.

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 2e957000
PfnDataBase 81a03000
PsLoadedModuleList 805644a0
PsActiveProcessHead 8056a558
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 10000050
BugCheckParameter1 fffde086
BugCheckParameter2 00000001
BugCheckParameter3 bf8e16d2
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805542e0
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 00000a30
DriverListOffset 00003640
DriverCount 00000085
StringPoolOffset 00005dc0
StringPoolSize 00001268
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack a926f5d0
DebuggerDataOffset 000033b0
DebuggerDataSize 00000290
DataBlocksOffset 00007028
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Sun Mar 13 10:30:47 2005
System Uptime: 0 days 23:16:09
start end module name
804d7000 80701000 nt Checksum: 0021C534 Timestamp: Wed Aug 04 01:18:18 2004 (41107FAA)

Unloaded modules:
a8eb9000 a8ee3000 kmixer.sys Timestamp: unavailable (00000000)
a8eb9000 a8ee3000 kmixer.sys Timestamp: unavailable (00000000)
a8eb9000 a8ee3000 kmixer.sys Timestamp: unavailable (00000000)
ba2f2000 ba2f7000 ATWPKT2.SYS Timestamp: unavailable (00000000)
ba312000 ba317000 ATWPKT2.SYS Timestamp: unavailable (00000000)
a9e23000 a9e28000 ATWPKT2.SYS Timestamp: unavailable (00000000)
a8eb9000 a8ee3000 kmixer.sys Timestamp: unavailable (00000000)
a8eb9000 a8ee3000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8f83000 a8fad000 kmixer.sys Timestamp: unavailable (00000000)
a8fd0000 a8ffa000 kmixer.sys Timestamp: unavailable (00000000)
a8fd0000 a8ffa000 kmixer.sys Timestamp: unavailable (00000000)
a8fd0000 a8ffa000 kmixer.sys Timestamp: unavailable (00000000)
a8fd0000 a8ffa000 kmixer.sys Timestamp: unavailable (00000000)
a909a000 a90c4000 kmixer.sys Timestamp: unavailable (00000000)
a9999000 a99c3000 kmixer.sys Timestamp: unavailable (00000000)
f7a8c000 f7a8d000 drmkaud.sys Timestamp: unavailable (00000000)
a99c3000 a99e6000 aec.sys Timestamp: unavailable (00000000)
ba918000 ba925000 DMusic.sys Timestamp: unavailable (00000000)
aa194000 aa1a2000 swmidi.sys Timestamp: unavailable (00000000)
f79fb000 f79fd000 splitter.sys Timestamp: unavailable (00000000)
f7567000 f7570000 processr.sys Timestamp: unavailable (00000000)
f778f000 f7794000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7917000 f791a000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check


RwsRichard

 

Thats not what I asked for.

 

Sorry, how do I post the minidump?

 

inside of the directory, you will find several files that have a .dmp extension.

Zip them up and attach them to a post.

Default size is 64kb, and max post attachment is 100kb. Keep that in mind. I just need the last 2 or so.

Thanks!

 

attached is the last 3 dumps.

 

I'll look at it today after class.

 

Ok...

A lot of information to follow.

First, the debug logs, then, the possible diagnosis.

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


Crash from 3/13
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\memdump\Mini031305-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:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Sun Mar 13 09:30:47.812 2005 (GMT-7)
System Uptime: 0 days 23:16:09.673
Loading Kernel Symbols
....................................................................................................................................
Loading unloaded module list
...................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {fffde086, 1, bf8e16d2, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: 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: fffde086, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf8e16d2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: fffde086

FAULTING_IP:
win32k!GrePolyPolygonInternal+5e
bf8e16d2 f2ff8b85e0fdff repne dec dword ptr [ebx-0x21f7b]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf84e8d3 to bf8e16d2

STACK_TEXT:
a926f870 bf84e8d3 74010e6d a926f898 a926f8ec win32k!GrePolyPolygonInternal+0x5e
a926f918 804ddf0f 74010e6d 0012bc28 0012bbcc win32k!NtGdiPolyPolyDraw+0x1cc
a926f918 7c90eb94 74010e6d 0012bc28 0012bbcc nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012bb90 00000000 00000000 00000000 00000000 0x7c90eb94
a926fbec 80570593 a926fca8 a926fcac a926fc7c nt!KiCallUserMode+0x4
a926fc48 bf813d09 00000002 a926fc8c 00000018 nt!KeUserModeCallback+0x87
a926fccc bf803522 bc68c888 0000000f 00000000 win32k!SfnDWORD+0xa8
a926fd0c bf80f40a 7d5084d5 a926fd64 0012fe7c win32k!xxxDispatchMessage+0x1dc
a926fd58 804ddf0f 0012fed0 0012feb4 7c90eb94 win32k!NtUserDispatchMessage+0x39
a926fd58 7c90eb94 0012fed0 0012feb4 7c90eb94 nt!KiFastCallEntry+0xfc
0012fe44 00000000 00000000 00000000 00000000 0x7c90eb94


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
bf8e16cb - win32k!GrePolyPolygonInternal+57
[ ff:bf ]
1 error : !win32k (bf8e16cb)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------



crash from 3/09

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


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\memdump\Mini030905-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:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Wed Mar 9 20:53:40.562 2005 (GMT-7)
System Uptime: 0 days 6:40:56.413
Loading Kernel Symbols
.....................................................................................................................................
Loading unloaded module list
..................
Loading User Symbols
Unable to load image ati2dvag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {979fad80, 0, 979fad80, 0}


Could not read faulting driver name
Probably caused by : ati2dvag.dll ( ati2dvag+122ec )

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: 979fad80, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 979fad80, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: 979fad80

FAULTING_IP:
+ffffffff979fad80
979fad80 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf9e52ec to 979fad80

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a9a7f4ec bf9e52ec e216bad0 e13cf400 00000010 0x979fad80
a9a7f5ec 00000000 00000050 00000201 00000058 ati2dvag+0x122ec
a9a7fb58 80570593 a9a7fc14 a9a7fc18 a9a7fbe8 nt!KiCallUserMode+0x4
a9a7fbb4 bf813d09 00000002 a9a7fbf8 00000018 nt!KeUserModeCallback+0x87
a9a7fc38 bf83c81d bc6d34e8 0000007f 001593a8 win32k!SfnDWORD+0xa8
a9a7fcac bf801e58 e1fc4638 a9a7fd64 00000000 win32k!xxxReceiveMessage+0xb7
a9a7fce8 bf80365e a9a7fd14 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x1d7
a9a7fd48 804ddf0f 00c2ff28 00000000 00000000 win32k!NtUserPeekMessage+0x40
a9a7fd48 7c90eb94 00c2ff28 00000000 00000000 nt!KiFastCallEntry+0xfc
00c2fe80 00000000 00000000 00000000 00000000 0x7c90eb94


FAILED_INSTRUCTION_ADDRESS:
+ffffffff979fad80
979fad80 ?? ???

FOLLOWUP_IP:
ati2dvag+122ec
bf9e52ec ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ati2dvag+122ec

MODULE_NAME: ati2dvag

IMAGE_NAME: ati2dvag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 412ccc5d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_CODE_AV_BAD_IP_ati2dvag+122ec

BUCKET_ID: 0x50_CODE_AV_BAD_IP_ati2dvag+122ec

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


crash from 3/07

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


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\memdump\Mini030705-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:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Mon Mar 7 09:05:17.125 2005 (GMT-7)
System Uptime: 0 days 20:21:36.829
Loading Kernel Symbols
.....................................................................................................................................
Loading unloaded module list
..............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, a9e76fca, a8f01ad4, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: a9e76fca, The address that the exception occurred at
Arg3: a8f01ad4, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
afd!AfdBReceive+5f
a9e76fca 8dcf lea ecx,edi

TRAP_FRAME: a8f01ad4 -- (.trap ffffffffa8f01ad4)
ErrCode = 00000000
eax=00000000 ebx=a8f01b94 ecx=89587008 edx=00000000 esi=8963fef0 edi=8963fef0
eip=a9e76fca esp=a8f01b48 ebp=a8f01b88 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
afd!AfdBReceive+0x5f:
a9e76fca 8dcf lea ecx,edi
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from a9e77233 to a9e76fca

STACK_TEXT:
a8f01b94 a9e77233 89587008 895870e4 000000a0 afd!AfdBReceive+0x5f
a8f01c30 a9e752c7 89576230 8a1696b8 a8f01c64 afd!AfdReceive+0x599
a8f01c40 804e19ee 8a0d1d80 89587008 80703410 afd!AfdDispatchDeviceControl+0x53
a8f01c50 8057184c 895870e4 89592338 89587008 nt!IopfCallDriver+0x31
a8f01c64 80582cef 8a0d1d80 89587008 89592338 nt!IopSynchronousServiceTail+0x60
a8f01d00 8058ecc3 0000065c 00000764 00000000 nt!IopXxxControlFile+0x5ef
a8f01d34 804ddf0f 0000065c 00000764 00000000 nt!NtDeviceIoControlFile+0x2a
a8f01d34 7c90eb94 0000065c 00000764 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0578fd1c 00000000 00000000 00000000 00000000 0x7c90eb94


FAILED_INSTRUCTION_ADDRESS:
afd!AfdBReceive+5f
a9e76fca 8dcf lea ecx,edi

CHKIMG_EXTENSION: !chkimg -lo 50 -db !afd
2 errors : !afd (a9e76fcb-a9e76fdb)
a9e76fc0 f6 47 0d 01 0f 85 b7 6b 00 00 8d *cf 1c 8d 55 cc .G.....k......U.
a9e76fd0 89 45 e0 ff 15 ac b5 e6 a9 f6 47 *0f 10 0f 85 a7 .E........G.....

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .trap ffffffffa8f01ad4 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

Well, 2/3, the errors likely point to corruption in the ram. Another to the video driver.

So...my thoughts on it?

Upgrade your videoa nd motherboard chipset drivers, and get your ram checked.

http://www.majorgeeks.com/download4226.html

 

HMMMM...I'm no expert (by any means!!), and I am new here, but since I had a scary similarity to your problem...figured I would atleast tell you what happened to me.

Had it overclocked to much!!! Don't know if you are even oc'd at all, but my system was doing alot of the same things as yours and more. What had me thrown, was that I wasn't having any of the typical symptom of an unstable oc'd system. Instead it was more along your line. Including...Diagnostic utilities trying to blame it on other stuff...ie...bad memory, or video, etc.

Anyway...what was happening....the cpu was slowly reaching maximum temp and then ofcourse when it did...it rebooted. No ryme or reason was apparent up front, but when I really started thinking about it, I came to the conclusion that it was when I was running really intense graphics, or if I had alot of stuff going on in the background (which ofcourse uses alot of RAM, which inturn is going to put more of a workload on the mobo, and on down the line etc.) So then I clocked it back to default and....VIOLA, My problem was now understood.

Well...I hope this gives you a little more insight, but if not...sorry to interrupt!!

Roger

 

I will check on the drivers for the motherboard chipsets. And run the test for the ram using the Memtest86+.

Thanks,
RwsRichard

 

Appreciate the input. I do not overclock my system.

The system should be running cool. I have one of those cases that shows the temp on the cpu, do not know how accurate it is , but it connects on the motherboard next to the cpu. This gauge always reads between 25c and 35c.

There are 4 fans blowing into the case and two fans blowing out the rear of the case and there is one fan setting on top of the cpu.

I also keep the room temperature between 70-76 degrees during the day, especially during the summer, and it gets cooler at night. The AC vents are pointed right at the PC, so I know it is getting a good cool draft.


Thanks,
RwsRichard

 

After letting Memtest86+ run for over 6 hours, I did not know how long to let it run, could not find instructions, I got 1500+ errors thru Pass 7, on tests 5 & 8.

Since I have 4 sticks of memory, it would have been nice to know which sticks are the problem.

Now, which brand of memory is best? I spent almost $600.00 for 4 sticks of Geil DDR memory. According to Memtest86+, I have just wasted $600.00.


RwsRichard

 

Well, the easiest thing to do is to take out all sticks but one and test each one.

If you get errors on the first pass, just stop it right there.

its likely only one stick is bad, and regardless of brand, you will end up with lemmons.

 

I will test each stick and see what I come up with.

Thanks for all your help, it was greatly appreciated.


RwsRichard

 

After testing each stick, I found 1 of the 4 sticks to be bad. I took the bad-paired sticks back where I bought them and they said that that particular brand of memory had a 5 year-in-store warranty and a lifetime warranty from the manufacture.

They were REALLY nice about it - surprise, surprise. They actually gave me the next grade up by the same manufacture and then tested the memory using MemTest86+.

I lucked out on that one!!


Thanks again for the assist.
RwsRichard