btkrnl.sys and a stalled XP load

[Nelson D]

My desktop system seems to have taken a dump on me. All
attempts to reboot, normal, safe mode, etc.... result int
he load sequence stalling upon loading btkrnl.sys. I have
had some bluetooth issues in the past but at least 9-10
months of trouble frre use since those times. I cannot
even repair this XP installation as the installation stalls
upon scanning the hardware configuration. I suspect some
sort of hardware failure and have already eliminated the
memory and hard drive as the source of the problem. Before
I continue to disassemble the computer.........

Has anybody experienced this before or might anybody have a
recommendation for a solution?

Thanks.

 

[Guest]

i am currently experiencing this same problem on my desk top and have found
another reference to it on the internet an it appears to be a result of
adding a windows xp critical update. followed by not shutting down corectly
nedding a couple of programmes to be forced shut down. then on every
subsequent boot normal hangs at windows logo and safemode hangs on
btkrnl.sys. if you use recovery console to rename the btkrnl file in the
hope widows ignores it safe mode hangs at mup.sys (the file before
btkrnl.sys). and after ripping out all bluetooth hardware system still won't
boot.

currnt conclusion is the new "critical security updates" have blocked a port
used by this software during boot up stopping it from functioning and causing
the system to hang.

if anyone has any ideas or solutions please let me know asap.

 

[antjw50]

THANK YOU HP TECH SUPPORT

follow these simple steps and cheer for HP

1 turn it on
2 enter the BIOS (one of the function keys, usually F10, it looks like
a blue screen and lists your proccesor etc.)
3 look carefully for something that sounds like resetconfigurtion or go
to original configuration. This should solve the problem as it did for
me.
4 exit and save
total time = 5 min
time I spent banging my head against the wall trying to figure this out
myself=4 1/2 days


TELL ME HOW THIS WORKS OUT

 

[nikkm1]

I had this EXACT problem, and tried all that you tried, so I was fully resigned to having to do a complete re-install of XP, But against the odds this is what worked for me - I put in the XP cdrom disk and as it booted it offered me the repair option (whereby once selected you are at the command prompt with a blank black screen and none of the data on your hard drives are easily accessible) Remembering bygone days and my previous tangles with DOS, I thought “ Just for the hell of it, I will try running DOS’s chkdsk command, using the parameter Chkdsk /F and it reported that there were errors , So I thought “Okay I might as well fix them and ran the command with the find errors and repair option - Chkdsk /R It took about 10 minutes and then reported that the errors had been corrected. Now anybody that remembers DOS will know that all Chkdsk seemed to do did back then was recover lost clusters, put them into useless files with which the only sensible thing to do with them was to delete them. At this point I exited the session, restarted and instructed XP to try to reboot normally, - all the while I am speaking to my buddy (who formerly was an IT professional) and I said to him quite confidently “there is no way that using Chkdsk will work”, he agreed saying “there’s more chance of him getting action from his wife tonight” [ I doubt if he’s had any lovin’ from that department for three years…brrrrrrr] Anyway to my incredulity instead of stopping mid-boot and then going into that non-stop repetitive booting cycle… the screen did a strange twitch and then Microsoft’s Windows XP Started ..frankly, I was shocked and so was my buddy, the system has been fine ever since.

 

[shaiss]

Confirmed, CHKDSK /r fixed this error on my xp pro machine!!!