random restarts

I have been reading about this problem all over the net and the answer still seems elusive.  My compuer randomly shuts down.  Sometimes a blue screen sometimes just a restart.  i havent been able to copy down the error code(i just turned off auto restart).    but it did mention sysdata.xml and mini2300-02.dmp.

Heres the thing.  I thought it was memory because i tested earlier today and i got thousands of errors on it.  then later i removed one module and tested with the other.  then replaced the first and tested again.  so i could get an idea of which one was bad.  when tested alone one of them had 2 errors.  later i did this again but there were no errors on either.  Also the computer didnt seem to randomly restart when there was only one stick in.  I tried both sticks one at a time.  Would this be a memory problem or maybe a bad socket on the mobo?

by the was my specs are:

Opteron 165
eVGA 7800 GT
DFI Lanparty Ultra-D
OCZ Enhanced Latency 1GB (2 x 512MB)
Antec TP-II (550w)
Scythe Ninja
abmacomberAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

robertthecatCommented:
Could be either or but typically it's memory. The only way to truly test the memory is to get a new stick and attempet to run windows normally.

The problem you describe sounds like inconsistant memory. you get the blue screen at different times and different errors since the memory never fails in the same place. If it were a software error you would usally get a more consistant reaction. So either bad memory or bad hard drive. I would say memory since you have already gotten errors on it.

What are you using to test the RAM?

Try at least one new NON-GENERIC sitck of RAM and post your results here. If it's the RAM gone bad then when you put the new stick in it should run striaght and normal right off after installation.
nobusCommented:
first, check if your memory is compatible with your mobo.
check it at www.kingston.com or    www.crucial.com
Then , run memtest86+ from   http://www.memtest.org/      and let it run a couple of passes.
and testing with 1 stick is a good start; but i've seen errors when both sticks were ok separately, and not when used together.
cpc2004Commented:
Maybe it is bad contact between the memory module with the memory slot. Reseat the memory at the same memort slot or different memory. If your memory module does not have same speed, you have to change them to lower speed.

For example : DIMM1 and DIMM2 do not have the same timing.
   DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
   DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
   DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
Build an E-Commerce Site with Angular 5

Learn how to build an E-Commerce site with Angular 5, a JavaScript framework used by developers to build web, desktop, and mobile applications.

MereteCommented:
could be your psu is not pulling the correct power too if you have added a few extra bits and pieces.
I read somewhere here today too about the memtest may not always give an accurate reading first time and running it again could solve it.
abmacomberAuthor Commented:
i use memtest 86.   and my mem is compatible with my mobo

the thing is that when i run a single stick at a time then nothing bad happens.
robertthecatCommented:
Ar they the same exact RAM or different brands or types?
MereteCommented:
could be something simple too check the ide socket the plug where the ram sits  a small bit of dust thats all it takes, if you have some small compressure that can blow air into them to clean them. Is the arms that hold the ram in tight both click when you insert the ram sticks, did you lay the tower on its side?
If a stick is not seated correctly this can cause problems too, or it could be extremely bad luck and you got a bad stick. It is recomended not to touch the sticks surface when installing them as this can cause serious damage.



cpc2004Commented:
Try downclock the ram.
cpc2004Commented:
I mean pull back all the ram stick and downclock the ram.
nobusCommented:
>>   but i've seen errors when both sticks were ok separately, and not when used together  << this points to a Ram problem, but it can be the memory controller on the board too. you could test it with another brand of ram, or a slower setting as said by cpc2004
MereteCommented:
have you checked your event viewer it will list all the errors your machine is having. in control panel administrative tools event viewer applications.
you could also test your directx display from run type in dxdiag press enter.

MereteCommented:
Possible causes:

-Everything not completely seated on the motherboard.

-Overheating
If the system temp gets over 45 deg. C, then make sure the computer's fans are running, the vents are open, the computer is not located in an enclosed space or near a heat source, and there is no internal dust build up.
If those are ok, then remove the computer's cover, and run an external fan. If this fixes things, then install additional case fans. Recommended locations are lower front and upper rear of the case.
If the CPU gets over 60 deg. C, then make sure the thermal compound has not oozed out from between the CPU die and the heat sink. If that's ok, then replace the compound with Arctic Silver.
If no luck, then install a higher capacity heat sink fan.
If still no luck, then replace the heatsink with a more efficient unit.

-Overtaxed or bad power supply
Either test it, or swap it out with a different(preferably higher wattage) unit.
Also, always use a reliable brand, like Antec or Enermax. Off name cheap brands(even high powered units) can have one voltage leg that's insufficient to handle the load.

-Bad memory
Run Memtest86 and if problems are reported then -> remove and reinsert the memory a few times, if using multiple modules then install just one module at a time and try it in different slots, do not use any optimal settings for the memory in BIOS, and swap it out with known good memory.
Also, do not mix parity and non-parity memory.

-Bad video card.
Make sure it's fully seated, it's fan is running, its heatsink is securely mounted, and there's no dust built up on the fan and the heatsink.
If those are ok, then swap it out with a known good card.

-Bad MB.
Check for bulging, leaking, or ruptured capacitors.
If they look ok, then swap it out with a known good MB.

-IRQ conflict with a network card.
If no problems show up for the NIC in Device Manager, then remove it from DM, shut down, remove the card from the MB, and restart.

-Viruses and spyware.
Run Ad-aware, Spybot, and Hijack This for removing spyware.
abmacomberAuthor Commented:
Ok.  I placed my new memory in my dell.  After i started up it crashed after about 5 minutes.  I left it on for a day and there were no more crashes.  Also I put the dell memory in my computer and it worked fine.  seems like a memory problem to me!
MereteCommented:
good to hear you have progress abmacomber  yeah memory has its days I know :)
abmacomberAuthor Commented:
ok this problem is coming back.  I got my new ram today and im getting the exact same problem...blue screen.   i dont understand because this thing didnt crash at all when i was usint 256mb of the cheapest most generic ram ever made.

im not 100% sure but i think it might have something to do with the dual channel ram.  the 2 128mb sticks of cheapo stuff arent dual channel and they didnt crash it.  ive tried 2 different sets of the stuff in my sig and it made this computer go to crap.  It also seems to run better with only one stick of the OCZ at a time.

Does this dual channel theory make any sense?  im desperate.
nobusCommented:
could be, but as i said before, memory errors can point to the memory controller, which means a bad mobo
nobusCommented:
if you still got warranty on it, call for a replacement
abmacomberAuthor Commented:
is there a way to test this before changing out the whole mobo?
nobusCommented:
you can run some tests, but the outcome is not guaranteed  here some links :

Microscope :  www.micro2000.com/microscope_suite/index.php

tufftest :  www.tufftest.com/

Burnintest :   http://www.passmark.com/download/index.htm      
abmacomberAuthor Commented:
Another prob is that battlefield 2 will quit before i can even load a game.  no error message or anyhtihing...just straight to the desktop.  does this sound memory controller related??
cpc2004Commented:
You have to provide the system event log and minidump for further analysis. The crash may be caused by faulty ram or device driver error. The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump.
Check system event 1001 and 1003 and it has the content of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here
Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram.

MereteCommented:
abmacomber try this. from run type in dxdiag. run all the tests audio and display. check what version of directx you have, this test hopefully will shed some light if there is nay problems with your display card.

Go to control panel administrative tools event viewer applications and have a look at any errors here see if they point to one particular area.
When you put the ram in, do you A: unpower the machine actually unplug the power plug out? and B: lay the tower on its side ensuring that the ram click into place, how many ram/slots sockets are there on your mobo, some are sdram some are ddr ram, usually two different colours,
 C: are you putting the two sticks into the same colours even though they are apart ( ie the slots) make sure the ram is matching the colours. 2 for eg red sdr ram sockets, or the 2 blue/black for ddr sockets.
If you put one stick in the red and one in blue it will cause blue bsod.

Regards M
abmacomberAuthor Commented:
here is a file with maybe 20% of the 1001/1003 errors ---------http://home.comcast.net/~xomac/Document.rtf


here is the minidump zip file------------------http://home.comcast.net/~xomac/Minidump.zip


thanks for the help
cpc2004Commented:
From your minidumps, windows is crashed randonly with different bugcheck code. It is hardware error and most  probably the culprit is faulty ram.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
   Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
   For example : DIMM1 and DIMM2 do not have the same timing.
   DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
   DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
   DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitor

If it still crashes, diagnostic which memory stick is faulty
Take out one memory stick. If windows does not crash, the removed memory stick is faulty.


Mini010106-01.dmp BugCheck 1000000A, {88216478, 1, 0, 8051a375}
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+c9 ) <- faulty ram

Mini010106-02.dmp BugCheck 1000008E, {c000001d, f72b23cc, f7a3bbb8, 0} <-- hardware error
Probably caused by : yk51x86.sys ( yk51x86+193cc )

Mini010106-03.dmp BugCheck 1000000A, {0, 2, 0, 8050ced6}
Probably caused by : memory_corruption ( nt!MiGatherMappedPages+1a ) <-- faulty ram

Mini010206-02.dmp BugCheck 1000008E, {c0000005, 804ecfe3, f594ab94, 0}
Probably caused by : sr.sys ( sr!SrGetContext+58 )

Mini010606-01.dmp BugCheck 4E, {99, 43b40d, 0, 0}
Probably caused by : memory_corruption ( nt!MiDecrementShareCount+3a ) <-- faulty ram or CPU

Mini122905-01.dmp BugCheck C2, {7, cd4, 4c0, e1db00d0}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+2a3 )

Mini123005-01.dmp BugCheck 10000050, {d8f73114, 8, d8f73114, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttributeInExistingFile+3f3 )

Mini123005-02.dmp BugCheck DE, {2, e2e75660, e2e75664, 2bcb68c0} <- Faulty ram
Probably caused by : Cdfs.SYS ( Cdfs!CdPurgeVolume+c7 )

Mini123005-03.dmp BugCheck 1000000A, {88133e8c, 2, 0, 80510a8d}
Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+51 )  <- Faulty ram

Mini123005-04.dmp BugCheck 1000007F, {d, 0, 0, 0}  <-- hardware error probably faulty ram
Mini123005-04.dmp Probably caused by : ntkrpamp.exe ( nt!SwapContext+be )

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MereteCommented:
also check these
 by turning off all the applications that load automatically when Windows boots: Press Windows-Run >> at start, type in  msconfig, and press Enter. Click the Startup tab, uncheck everything, click OK, and reboot your system. If that solves the problem, try rechecking programs on the Startup tab one at a time (reboot between each) until the problem recurs. When it does, you've found the source.

Scan your PC for viruses (which you should be doing regularly anyway), and update your hardware drivers as well.

If these actions don't remedy your PC's involuntary reboots, the cause is most likely an overheated system. Open your PC's case and clean the dust out with a can of compressed air (you can buy this at any computer store for about $10).

The problem could also be related to the computer's electrical system. Try a different power cord (hey, it's cheap and easy), or replace your surge protector (not as cheap but still easy). And make sure your PC doesn't share an electrical circuit with a washing machine or other large appliance that uses a lot of power at irregular intervals.



cpc2004Commented:
Do you have any update?
abmacomberAuthor Commented:
well nothing so far has worked so i RMA'ed the mobo and the GPU and I got new RAM.  it should all be coming today.  i will let you know if there is a prob
cpc2004Commented:
Do you have any update?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.