Printable View
@david02
I ran the test under blend and it went into the Blue screen of death so I guess it might be ram no doubt.
I also ran it under "small FFT" and it crashed but it did not give me a blue screen of death
[Tue Sep 19 05:20:55 2006]
FATAL ERROR: Final result was 0CFF84E4, expected: F6BD0728.
Hardware failure detected, consult stress.txt file.
[Tue Sep 19 05:26:53 2006]
FATAL ERROR: Final result was 9EB6A06B, expected: F6BD0728.
Hardware failure detected, consult stress.txt file.
If you have 2 sticks of ram then test one at a time.
Check your temps with Everest, http://www.majorgeeks.com/download4181.html
Could Virtual Memory be causing this?
http://img83.imageshack.us/img83/156/vmri1.jpg
I have 512MB but it says I got 503MB and only using 283MB??
I heard that virtual memory can cause BSOD. Could this be a problem because I ran a memory tool from dos and it found no errors at all. The memory is 6 months old so I am sure it can't be it.
Age has nothing to do with it. Things go wrong and they can do so at any time. It's not uncommon for a product to be faulty when purchased.Quote:
Originally Posted by KazaaBoy
What does it say in the stress.txt file?Quote:
Originally Posted by KazaaBoy
Check your temperatures under full load. Post the results.
If even under format the problem persists, the Ram or high temps could be the problem.
However, just a thought, could one of your HDD be faulty and as a result cousing this?
Hi Peat Moss,
You can find it here
http://www.mersenne.org/freesoft.htm
greetings
503 MB of RAM?
I find that a real strange number :)
shouldn't Everest say it is 512 or am I missing something?
most likely it is a RAM problem :(
as said by dodgy367 and in the instructions below try one module at a time if you have 2x 256 MB modules and try it in in different slots. that sure will isolate the faulty module (no BSoD = memory OK) If you have one 512 MB module also try it in a different slot.
doublecheck it with memtest which can be found here
http://www.memtest.org/#downiso
quote
Instructions - Download the "Pre-Compiled package for Floppy (DOS - Win)" to "c:\memtest", insert a blank formatted 1.44MB Floppy Disk into the Floppy Drive. Unzip the file to the same folder, run "install.bat". At the prompt type "a" and press enter, if the disk is in the drive press enter again. Then wait for it to complete. When it is finished, reboot your PC leaving the disk in the drive, your computer should boot to the disk automatically. If it does not consult your PC manufacturer for further instructions. Once it boots it will run the test automatically, let it run for 3 passes. Intermittent memory errors require a more thorough test of running the diagnostic overnight. If you get any errors (designated in red) then you most likely have a defective memory module and it will need to be replaced. To be sure try reseating the module and testing it in another slot. If you have more then one memory module in your system you will need to test one at a time to isolate the defective module.
Notes - You will not be able to read the Floppy Disk in Windows when it is finished being made, this is due to the file system used by Memtest98+ not being supported in Windows. This is normal.
end quote
Quote:
Originally Posted by david02
Ah thank you . :)
Ya 503 mb is weird as the used and free = 502 . He has shared video I take it ? Mabye wrong chip set drivers ?
hmmm I thought everest would display (in the memory section) the real amount of ram (in your case 512) but it looks this is not the case (I wonder why) . Everest told me I have 511 MB Ram, not 512. Although it says 512 MB on section computer/summary I still find this strange .
Do other people have this too?
and yeah Peat Moss, It looks like Everest cannot calculate that well
Used ram + free ram = total ram -1(!)
strangly it calculates the same way on my configuration
Can someone explain this ?
I'll try to find an explanation but I do not have that much time now.