Computer Restart

[nightscar]

Hello everyone,
It has been a rough 2 days for me, to make a very long story short, Thinking XP's SP2 was having an effect on the installation of a game I have. I reinstalled xp, and came into all sorts of blue screen "Memory Managment" errors, disk errors, ect.

Untill finally the 5th time installing xp everything went ok, with some few bumps.

But the main problem I have been having and have always have ever since I upgraded and rebuilt my pc was constint computer restarts.

I will be in a game, commin out of a game, installing a game ect... and the computer will just up and reboot on me.

I used Microsoft's debugging tool with the mini dmp file and have come up with this:

************************************************************


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


Loading Dump File [C:\WINDOWS\Minidump\Mini051505-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun May 15 04:50:02.140 2005 (GMT-4)
System Uptime: 0 days 3:57:29.712
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DE, {2, e2df5820, e2dfd820, 1ccdd8c0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to load image Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

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

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

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 00000002
Arg2: e2df5820
Arg3: e2dfd820
Arg4: 1ccdd8c0

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xDE

LAST_CONTROL_TRANSFER: from 80524f98 to 805371aa

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a9d058 80524f98 000000de 00000002 e2df5820 nt+0x601aa
f7a9d09c 804f7da5 86069300 01000000 8643a3b0 nt+0x4df98
f7a9d0c8 804f9491 860693cc f7a9d15c 00000000 nt+0x20da5
f7a9d128 804f93a6 85cca650 f7a9d15c ffffffff nt+0x22491
f7a9d168 f766dc0c 00000000 00139a98 f7681f60 nt+0x223a6
f7a9d190 f769b76e 85fd7850 e2139a98 e2139a88 Ntfs+0x3c0c
f7a9d1f4 f76a20e1 f7a9d5c8 85fd7850 00000001 Ntfs+0x3176e
f7a9d264 f76a2189 f7a9d5c8 e21399c0 f7a9d30c Ntfs+0x380e1
f7a9d390 f76a1373 f7a9d5c8 e21399c0 e17de918 Ntfs+0x38189
f7a9d5ac f768fd83 f7a9d5c8 85f892b0 85d056c8 Ntfs+0x37373
f7a9d724 804e13d9 86708020 85f892b0 85f892b0 Ntfs+0x25d83
f7a9d764 8056e943 860861d8 86708020 00010080 nt+0xa3d9
f7a9d794 8056ea96 860861d8 01d056b0 867e7e70 nt+0x97943
f7a9d7bc 8056e9bc e1ab9c48 85d056c8 000005d0 nt+0x97a96
f7a9d804 8056ea06 000005d0 00000001 00000000 nt+0x979bc
f7a9d818 804dd99f 000005d0 0007d878 7c90eb94 nt+0x97a06
f7a9d824 7c90eb94 badb0d00 0007d81c bf8142ad nt+0x699f
0007d878 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

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

************************************************************

It looks like a driver problem to me, but to go from hear is beyond me?

If anyone has any instructions or ideas. I would greatly appreciate it.

Thanks

 

[Guest]

WOW! That all looks like a bunch of gibberish to me. What type of errors are you getting in the event viewer? Since I don't know anything about your system specs, I'm just going to throw some things at you.
Go to your MoBo manufactures web site and download the latest chipset driver for your board. Do the same thing for your video card and other components.
If that doesn't help, download <A HREF="http://www.memtest86.com/#download0" target="_new">Memtest86</A> and run it from floppy for at least a couple of hours. Overnight or something is better, the longer the better. Zero errors is the only acceptable result. If you get any errors, and are useing more than one stick of RAM, run Memtest again on each stick individually.
Next, go to your hard drive manufacturers web site and download their diagnostic utility, and check your hard drive out. For example, the one for Maxtor drives is called PowMax, I think.
Now, if you feel comfortable doing so, flash the BIOS to the latest version, if you don't already have it. There is nothing complicated about it, and there is nothing to be scared of, but some people FUBAR their system trying to do this. So be careful and follow the instructions.
If you still have problems after all this, your power supply is probably go out. Swap it out with one that you know it works.
Good Luck.

_________________________
Your arrogance is boring!

 

[nightscar]

I do appologize about not includin my system specs was late and I was tired



My Box:
Windows XP W/ SP2
P4 3.4GHz
1 GiG HyperX Duel channel DDR 400
2 60 GiG HDD's Runnin Raid 0
Lite-On DvD RW CD-Rom RW all in one drive
Abit Ai7 MohtherBoard
550W PSU


As far as your ideas, most of them I have already done, I have flashed the bios, have downloaded every update to every hardware componint in my case that I could find.

I ran that MeM test from microsoft, and before I had a 400W PSU and got over 200 errors.

I recently picked up a 550W PSU and I ran the test again for the same amount of time and out of 117 passes I got 1 error on the 64th pass.

I wrote Kingston about this and they suggested upping the voltage to my RAM and run the test again. Is this wise?

So I have yet to do that, and see what I get for results. The error I think that came up during the MeM test was a WINVC error.

Like I stated in my 1st post ever since I upgraded the CPU, RAM, and HDD's with Raid 0. MY system has been acting funny. As in getting errors in games that I never got before, or my whole computer restarting on me.

Thanks for the help guys/gals<P ID="edit"><FONT SIZE=-1><EM>Edited by Nightscar on 05/15/05 03:27 PM.</EM></FONT></P>

 

[riser]

Reset BIOS to fail-safe if that is an option.

Is your CPU over heating? That causes frequent and random reboots. Double check to make sure you have a good heat sink on there.. or take the side off your case, have a small fan blow in there.. check the temps in BIOS or download a program that shows the temps on your desktop.

Video card.. wasn't listed on your specs..

Make sure you have adequate air flow...

Reseat your heat sink on your CPU. Those p4 things work good at times.

You might even want to disable HT in bios JUST to see if that might be causing your a problem.

As far as your memory.. do you have 1 chip or 2 for the 1GB?

If you have 2, remove one, test it out, switch that config around to test both out.

If you have 1, try putting it in slot 2 if your mobo will let you. Check to see if that's a problem.

Is the RAM hot to touch? Could be over heating or faulty.
I buy all my RAM from Crucial.com because of their lifetime warranty. Hope HyperX offers that kind of warranty..

 

[nightscar]

Sorry could of sworn I had my vid in there.

It's a Radeon 9700 pro.

As far as temps I have abit motherboard with guru on it so my temps are:

at high load CPU: 130F
at idle load CPU: 110F

Now the big boy is my PWM

At high load PWM: 180F
At idle load PWM: 120F

Try not to flip out after reading that temp for the PWM I looked at the abit site and they say this is normal for a P4 presscott and that the PWM is quoted for over 200F

As far as my RAM yes the hyperX goes though kingston which has lifetime warrenty on there RAM.

I have 2 sticks each one is 512MB
thats one of the things I still have to test is each RAM individually, I will do that after my diag test run on my Seagate HDD's

I looked more into the issue from my 1st post and suposivly the stop error I am receiving that is rebootin my computer is from a driver?!

Well there are only 4 new items that I have upgraded in my PC that after I did this whole problem started.

Those are RAM, CPU, HDD's, CD-DVD R/RW drive.

So by deductive logic which one of those have drivers?

My Box:
Windows XP W/ SP2
P4 3.4GHz
1 GiG HyperX Duel channel DDR 400
2 60 GiG HDD's Runnin Raid 0
Lite-On DvD RW CD-Rom RW all in one drive
Abit Ai7 MohtherBoard
550W PSU

 

[riser]

What is the exact error you get when you boot your computer?

 

[nightscar]

Ok, hear is the situation thus far.

I have run diag test on both HDD's no errors
I ran the windows MeM diag test for over 12 hrs on 1 stick of RAM no errors

I am now as I write this running the MeM test on the other stick of RAM, so far over 4 errors
*light bulb goes off above head*

I play the massive multiplayer game Worlds of Warcraft which is very heavely into RAM usage and CPU usage. What I plan on doing tomarrow since everytime I try and install this game (with both sticks of RAM in mind you) I usually get errors or computer restarts, i'm going to stick in just the good stick of RAM and try to install this game if I get no errors or restarts and everything goes smooth. Then Raid 0 will go back onto my pc along with a frash install of winxp with sp2.

I know it's kinda a weird way to test the system but hey if it works right.

I have a feeling that all this time and all this trouble I was having was from a bad stick of RAM.

I will let everyone know (for those who care ) how everything turns out. And I thank everyone who has lent me there tips.

Tis truly amazing how errors in a single stick of RAM out of all other normal working hardware in your computer can cause such havok to a system.


My Box:
Windows XP W/ SP2
P4 3.4GHz
1 GiG HyperX Duel channel DDR 400
2 60 GiG HDD's Runnin Raid 0
Lite-On DvD RW CD-Rom RW all in one drive
Abit Ai7 MohtherBoard
550W PSU

 

[riser]

RAM can cause some crazy problems.. new systems share memory. older motherboards would work off one stick of memory and move to the other as needed.. this was done because it didn't bog the system down running a small amount of memory on two sticks.. today's new computers do the dual/double data stuff which can keep up..

remove that bad stick and you probably won't have a problem at all...

and keep in mind, memory normally comes with a lifetime warranty.. so that means just return it and get a new stick.. if you have to ship it somewhere, ask for a "cross shipment" so they'll ship the stick to you that day and you return yours.. unless they want you to return it in their box..

 

[jmwpom3]

I've had more problems over the years with RAM than any other. Sometimes even certain brands work better with certain MB's, etc. I've found that usually those strange problems trace back to the mem. Buy same manufacturer for all sticks in the system, use the better companies, that kind of thing seems to minimize this stuff, IMHO.
One of the first thing's I'll do with these prob's is either remove the RAM and try a diff. one and/or change/check the slots where available. I know you already found the prob, just my comments.

<font color=green> AMD- Intel's choice for Best CPU manufacturer </font color=green>

 

[nightscar]

Well today I would have to say was a very good day for me

After running those diag test on the stick I found that the RAM had over 80 errors on it after 500+ passes.

So I went with the one stick I knew was good and put Raid 0 back on my pc with a fresh install of xp, along with WoW and HL2 and everything went on without one single problem.

I will be contacting Kingston for an RMA number and getting that little trouble making stick-o-RAM out of my hair.

To be exstra safe when the new RAM comes first thing i'm doing is running the MeM test on it.

All in all I think this was a good learning exspireance for me, I now know that in the future if something is acting funny and I start to get errors the 1st place i'm lookin is the RAM

I would like to thank everyone again for giving there tips out and helping me the best they could.

My Box:
Windows XP W/ SP2
P4 3.4GHz
1 GiG HyperX Duel channel DDR 400
2 80 GiG HDD's Runnin Raid 0
ATI 9700 Pro
Lite-On CD-ROM/DVD R/RW
Abit Ai7 MohtherBoard
550W PSU