Chainer

Quick thought. Perhaps something went wrong in the CMOS?

I've seen quite a few threads where that was the ultimate fixer for the computer... hmmm...

Any thoughts on that?

jcgriff2

Hi -

I was wondering why still so few files in your reply zip. So I got on XP Pro system finally and found the reason.

This batch script written for Vista. I did make some changes, but forgot the most important -- XP is "My Documents"; Vista = "Documents".

Please download the zip attached to this post. Make sure SysInternals AutoRuns in your "My Documents" folder. Then run batch script file. Then look for TSF_Vista_Support folder in My Documents - you will see exactly what I mean.

Live SysInternals AutoRuns - SAVE as exe file in 'My Documents' folder:
http://live.sysinternals.com/autoruns.exe

Still a problem w/ 'where' command - don't worry about that. Same issue w/ dump of app & sys logs - command not in XP - so I am having batch script copy the entire log files out. Also issue w/ dxdiag command - don't know yet what that problem is in XP.

I need you to run another exe file - can't do so here. See PM and send those results to me via email.

Thanks. . .

JC

.

Attached Files

BSOD_XP_v1.1_jcgriff2_.zip (3.9 KB, 10 views)

Chainer

Hey JC,

Sorry if I missed files. If you can, just make a list. This is all very much over my head personally, and keeping up with someone of your caliber is very tough but interesting none-the-less.

Anywho, give me a bit to run this stuff and get the results out. I have a few appointments to tend too today.

Again, thanks as always -
Chain

Chainer

wevtutil was not a recognized command in this version of the file. it's currently sitting on the msinfo32. will load it up as soon as it finishes.

ok, past the msinfo32, it's onto other things. autoruns.exe opened up, and it's still going. will you need an export of the autoruns.exe? nevermind, it closed on its own, haha

here's the TSF folder now :) got it done! Woot!

Attached Files

TSF_Vista_Support.rar (346.9 KB, 2 views)

Chainer

Ok - So I can try and provide as much info as possible, here are pictures of the freeze with processor information.

It seems with my X2 dual core - only one side is ever really in use? Could this be a problem?

Anyway...

I'll be posting pics and linking to youtube videos so you can see the freeze process.

And, to top it off, I'm not always getting the blue screen. as you can see in these pics - It hard freezes. (DON'T STEAL MY MXO SKILL TREE LOADOUTS! XD lol)

Anywho, expect a video to come next...

Attached Images

	FREEZE.jpg (259.8 KB, 3 views)
	FREEZE2.jpg (507.7 KB, 3 views)

Chainer

http://www.youtube.com/watch?v=x6f8hhFPrH0

There is video of my actual freeze - So... Take from it what you will.

Chainer

http://www.youtube.com/watch?v=CGf0DJBA_I4

Another Freeze video - Weird Keyboard response. Check the video details for a longer description.

Thanks as always to may favorite forum people :)

jcgriff2

Hi -

Very nice flick you made - but i didn't get to see a live BSOD! I think that would have been more desirable actually given the situation. The system completely freezing during boot obviously is not good nor does it give me hope that your system problem is software related.

I must ask about the YouTube site - I noticed all of the other clips - all seemed to be related to BSOD "How to BSoD your Windows NT based computer", "The 'Virus' Prank with BSOD" and one that not too many need instructions for - "Pointless ICT - How To Make Windows Vista BSOD".

Thanks for running the file - and for the film. I knew that several of the commands in the batch scrip would probably be INOP under most XP systems. Some XP systems can run those commands - like one XP Pro system here. I may have copied the utility... don't recall.

I will continue to look through the ~20 files (5+ MB) that you generously sent. But what I am finding so far looks very much like my Vista event logs did a few months ago. 4 new systems froze w/in 24 hours after 1st boot. I have been listening to those here in this Forum finally - a major cause was heat.

Unfortunately, I will not be much help to you as this turns to hardware. I sit - am actually over the fence and squarely on the software side of this business. I have never had a reason nor the opportunity to handle hardware. I am the type that can take anything apart - but end up w/ many "spare parts" after it is reassembled. Then it doesn't work.

I have found much more out about Dr. Watson, but right now I think you should get some hardware specs posted. D/L, install and run PC Wizard and save all. You can paste some into post, but the report in its entirety will need to be attached.

http://www.cpuid.com/pcwizard.php

Please keep me posted on BSODs or additional freezes.

Try to have a good weekend.

JC

.

Chainer

Alright, I'll get right on getting that done. Also, I have the camera next too me in case of a freeze where it blue screens -_-

If I can catch it, great. If not, Eh.

I am wondering if the mother board may be bad, or the processor bad, something along the lines of creating the occurrence of the power still going through the system to the keyboard? To me it sounds like some (for lack of a better term) "switch" isn't operating as it should.

Ok, here is the Hardware support. If I did it wrong, lemme know and I'll try again :)

As always - Thanks! :D

Attached Files

Hardware summary.rar (14.9 KB, 2 views)