XP laptop boots, logs in.. then nothing

[jayztek]

Really is no more to tell

It boots up, logs in, even can press ctrl+alt+dlt and choose options, if i pick task manager i get the hourglass, then nothing, caps lock works so no frozen keyboard

I have tried to boot to the os in

safe mode
safe mode + CMD PROMPT
last known good
whatever this is it is zapping the os after logon, but i dont think the drive is bad, the reason i have not tried the obvious cures is because the cd rom in this laptop is broken (actually it isnt even in there except for the ribbon cable)

Thinking of trying to boot with a usb, but everytime i try to make one of those they fail because someone forgot to include part of the files?

any ideas on what this is, how to get around it!

 

[jayztek]

how are you suggesting i use the bartpe disc

Only access is through the LAN i cannot see a desktop, i can get to the snapin for the computer (users and groups whatnot) however i cannot see the disk managment (perms denied)

I will try to set the whole drive as open, but remember i CANNOT see windows

I can only see files and folders through lan, no way to laod any external apps that i know of

Unless bartpe can scan the drive via the network, let me know

 

[jayztek]

Quick update

I have started DLEETING folders in the docs and settings area, erasing all trace of anything that may be hanging the system

Thinking about copying the SYSTEM32 from the windows disc to the laptop, who knows??

Also in the all users i found a drwatson log failry long (211mb) and it mentions some failing stacks and apps around the time this laptop went kablooey

one of them is below

Application exception occurred:
App: C:\WINDOWS\system32\dwwin.exe (pid=268)
When: 10/16/2009 @ 02:13:23.188
Exception number: c0000005 (access violation)


probably means nothing but then again everything probably means nothing at this point

 

[jayztek]

ok so here is where i am at

i have attached the event viewer MSC via the network

I cleared all the logs (saving them first) then i rebooted)

this was in the app log

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 10/16/2009
Time: 7:17:47 PM
User: N/A
Computer: TOSH
Description:
Faulting application USERINIT.EXE, version 5.1.2600.2180, faulting module USERINIT.EXE, version 5.1.2600.2180, fault address 0x0000c92a.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 55 53 45 ure USE
0018: 52 49 4e 49 54 2e 45 58 RINIT.EX
0020: 45 20 35 2e 31 2e 32 36 E 5.1.26
0028: 30 30 2e 32 31 38 30 20 00.2180
0030: 69 6e 20 55 53 45 52 49 in USERI
0038: 4e 49 54 2e 45 58 45 20 NIT.EXE
0040: 35 2e 31 2e 32 36 30 30 5.1.2600
0048: 2e 32 31 38 30 20 61 74 .2180 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 30 63 39 32 61 0000c92a



Also i did a boot logging, i am going to look and check that file now, my thought is a core windows file has been corrupted, and that's why windows is hanging, but i have full functionality via network

Any thoughts would once again be appreciated

 

[jayztek]

just an update

i have gotten the laptop so it will boot and after the logon it will fire off about 100 drwatson prompts makes tons of "ding" noises, once a exit out of all thsoe it jsut sits there, if i try o ctl alt dlt it fires off more of them

i am working with someone in IRc right now as to further ideas

 

[BadBigBen]

sounds more and more like a hardware issue, my thoughts are RAM maybe even the HDD...

ok, now to my earlier thoughts, I had believed that windows was switching off the external monitor after it loaded the Display driver, this usually happens after the black WinXP screen with the moving bar (cylon bar)...



Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[jayztek]

the end of this is as follows

after working considerably with someone via IRC we were able to put our brains together and discover many things, one was a virus ROOTKIT called NMP had ripped through the system, what it did not infect it trashed, with the help of a XP image on our RIS server and a night of work we were able to bring it back to life, it was not the hdd, ram, or any other HARDWAre ISSUE

IN THE END IT WAS A nasty VIRUS (PROBABLY ONE OF THE WORST I HAVE EVER ENCOUNTERED)

THANKS everyone for all the tips, see ya next time