Printable View
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
Why, wmicro, are you apologizing for anything? For what -ed said? Well, you shouldn't, alright? Geesh that was nothing!! We are ALL about diagnosing pc's. Some of us just need to editorialize: me, others, and especially confus-ed. He is THE Geezer, and has been around longer than most, after all. So, let him go off on his occasional techno rants. After all, it is often the ones who have been here the longest who do just that And. there really is a reason for it. (well, most of the time...you see sometimes, we just 'play' with each other) and quite often we ALL can learn something from it. So, being you are here to help, take it from someone who hasn't always gotten "along" with the old timers: be patient and don't fight back: but DO contribute...because we can always use expertise. Alright?Quote:
Originally Posted by wmicro
Anywho, yeah, now that we know the hdd is alright we can pursue other possibilities. And, yeah, the video card is a possiblility. So: step by step we will help! Trust me: don 't fight, just get along. Your knowledge and expertise will become obvioius: to some sooner, to others later.https://forums.windrivers.com/images.../2006/04/1.gif
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
I have now enabled small dumps.
Well atm it looks like it is either some thing wrong with the motherboard, gfx card or IRQ and resourse problem as you think it is.
How can I got about checking thise 3 things?
Ok, just had a couple of BSoDs, and I need to know which program to use to open them
If you unchecked the 'restart automatically' bit as Noo says above, when you get a 'fatal' one it should get 'stuck' & the only way out is reset or on/off (you can get 'BSODs' that aren't fatal), the simplest answer is to write it all down !Quote:
Originally Posted by Qerr
& I'll answer your earlier questions while I'm at it as well ..
The only practical way (without specialist equipment), to check any PC part is to try it in conjunction with known working good ones (I think someone says earlier?) - not much help if you just have one pc !
As for IRQ conflicts the best way with that is to start with absolutely the minimum kit installed you can, get it working like that & then add back any additional cards that might be responsible for all this 'madness' .. (so just memory vga & hd, any 'onboard whatever' wants disabling in bios if you can work it out - this is also the time to try ACPI on or off, if you still can't get it going)
Its over a month since I made it so that the pc becomes a blue screen with the serius errors instead of just rebooting, but isnt there a way to read the logs?( I'm some what lazy when it comes to writing down all the stuff it sais. :)
As for the resolving if it as an IRQ problem, isnt there an easier way? :)
Because if I Have to install every thing again then I would have to wait intill this weekend :\
Qerr, the bsod information is vital. Please write it down.
No (well if there is, somebody please tell me ! then maybe I won't think the pay for this is so 'mean' ..) - this is one of the many things I do for a living - testing various pc part combos for 'assembly' manufacturers (folks who put a motherboard made by 'someone' with a video card by 'somebody else' with a NIC by 'yet another guy' etc) - they send me a big pile of parts & I test all the combos & drivers they come with & then they decide what they might want to ship (not always taking notice of what they paid me to do I might add, grrr.. - pressumably another tester somewhere can get it to work, maybe with other drivers ? or maybe I'm more picky or just thick ..) - if you can get hold of all the correct documentation it gets easier (aforementioned available resources by slot), but nobody seems to do that any more !Quote:
Originally Posted by Qerr
Often any BSOD gives pointers after a bit of googling ;)