Printable View
sorry for this long delay from me, but I have just tested my memory with memtest86 and I found no errors, so It isnt the memory in my pc. :\
I'm wondering if it is possible that a hdd can be the cause of the error.
It makes this odd, sort of hacking sound (not much tho, its only about 2-3 of this anomalitis in the sound, and I'm not sure if it is the hdd or another device) when it is almost done booting up.
I will see if I'm able to install windows on a nother hdd and see of it goes.
If you are hearing sounds from the hdd then almost "anything" is possible. Download the hard drive diag from your hard disk manufacturer and run the test before continuing problem solving. Listen: if the hard drive is going bad, you will lose everything if you continue unless you back up NOW!!!Quote:
Originally Posted by Qerr
So, try this first:
http://support.wdc.com/download/index.asp#dlgtools
Here what to try is to remove all cards disconnect all drive except your floppy, hard drive and your video card and start your computer and see what and what code you received by Windows XP.
Also see this links on Windows XP Knowledge Base Articles on stop Error Messages Checklist at http://dynamicmember.us/wmtbb/index.php?showforum=23
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details. at
http://www.msicomputer.com/product/d...l=K7N2_Delta-L
SLOTS
One AGP (Accelerated Graphics Port) 1.5V 4x/8x slot
Five 32-bit PCI bus slots (support 3.3v/5v PCI bus interface)
One ACR (Advanced Communication Riser) slot
What will happen if I have two xp installed simutanuasly on two different hdds
(both are in the same pc tho)
Can I choose from which to boot from?
Need to make sure that it isnt the hdd that is bad and to see if it is possible to solve the problem by just formating the whole hdd.
To wmicro: where in bios can I change voltage etc to the memory? Can check it out aswell, but I'm pretty sure it isnt the memory.
Re memory timings - experience tells me if they are 'bad' then setup spits the dummy & won't complete, I'd be off running some disk diagnostics like RRR mentions ..
& that seems much better & less bother than doing a tandem install (btw if you do another then 'pre-windows' it should give you a choice of which to run)
Geesh this thread is getting confus-ed https://forums.windrivers.com/images.../2005/03/1.gif. I had to look back to see who started it and what the original problem was. https://forums.windrivers.com/images.../2005/03/1.gif
Qerr, go back to the WD link for the diag. You seem to want to do this the hard way. The download will fit on one floppy and take 90 seconds to test the drive. Remember, if you're drive is going bad, the more you play with it, the less chance you get at recovering data. So, let's be sure about the hdd first.https://forums.windrivers.com/images.../2006/04/1.gif
To start the ball rolling we must conclude on diagnosing the machine.
Windows NT, 2000, XP, XP professional and Windows 2003 and one of the secrets of the software is the reason behind the delay on starts up these Windows versions have a built in diagnostic sequence which every time window starts up going through the diagnostic sequence which you can’t see this is the reason of the long start up time. In the Linux OS version when you install the Linux you will see the diagnostic sequence live which you see everything testes accept for Windows in something fails in the diagnostic sequence you will get the error codes like these.
User confus-ed is on the right track “Re memory timings - experience tells me if they are 'bad' then setup spits the dummy & won't complete, I'd be off running some disk diagnostics like RRR mentions ..” and also so user TripleRLtd is on the right track also “go back to the WD link for the diag. You seem to want to do this the hard way. The download will fit on one floppy and take 90 seconds to test the drive. Remember, if you're drive is going bad, the more you play with it, the less chance you get at recovering data. So, let's be sure about the hdd first”.
These error codes, this sounds like more of a hardware problem then software and you tested the hard drive and test OK! I would disconnect that hard drive and install your Windows XP on another drive and see if this cure the problem if not I would incline it would be the motherboard and the reason behind this I have seen this, 4 times in my experience dealing with Windows 2000 and XP as confus-ed states it is timing’s problem.
The rule of thumb any type diagnosing from TVs to automobile computers you must diagnose using knowing good parts.
Also your Bios should be set to auto unless you changed it.
You can see better explanation in your user manual on voltage setup.
Just a note for both RRR & wmicro - folks here always want to do things the hardway ! :D - strangely even when several folks say the same thing many times the poster will 'have their own agenda' & want to do things their own way regardless, of whats already been said to them .. you'll have to grin & bear it ;), they don't know who knows what they are talking about, if they did they probably wouldn't be asking !
The PC Boot Process - Windows XP.
http://dotnetjunkies.com/WebLog/unkn...les/12284.aspx
OK, I ran the diagnostics utility, both quick and extended testing and it found no errors.
How can I find out if the motherboard is the cause for the "random" reboot?
Qerr is your machine set to automatically restart on error? If so, please uncheck it. (Right click my computer, properties, advanced, startup and recovery button).
Then you can get the full bsod in all its glory and you can post exactly what these errors are.
What does event viewer have to say just after one of these reboots?
What will happen if I delete the memory.dmp file? Will windows make a new one because atm it is 767mb in size and I'm unable to open it.
Wow! Nothing, delete away, it will recreate...
To Qerr
The key is win32k.sys this is the root of the problem like I stated it is a timing problem, see more on the PC Boot Process - Windows XP. At http://dotnetjunkies.com/WebLog/unkn...les/12284.aspx
On the file or driver call win32k.sys so to make it quite sample it sounds like a graphic card is your problem. See these links for better understanding.
See this one for understanding Windows program cannot predict that this will happen because there is no standard location for storing the GINA DLL chain at
http://www.anixis.com/products/ppe/techdoc/td00026.htm
http://www.i.u-tokyo.ac.jp/ss/lectur...32K/Win32K.pdf
http://support.microsoft.com/default...&Product=WinXP
You need to enable 'small memory dump' .. goes searching on how .. Overview of memory dump file options for Windows 2000, for Windows XP, and for Windows Server 2003 - 'ed's summary -Quote:
Originally Posted by Qerr
I'm coming to the conclusion that this is all just IRQ & resource issues for sure, as I said about two pages ago (less 'certainly' ;)).. this thread now is sooooooo complicated, due to having answered about three other peoples problems on the way .. that's its pretty difficult to find out just what is happening - if Qerr can manage a summary at this point of just where he might be 'at' :) - I think it'll certainly help (if it just helps me !)..Quote:
Click Start, point to Settings, and then click Control Panel.
Double-click System.
On the Advanced tab, click Startup and Recovery