🔒 Locked
Strange behaviour
Advertisement
Original Post
OK, here's a short story: I was visiting a friend and brought my PC (only the tower) along. He already prepared a display and keyboard for my computer. When I plugged all in, I started my computer, and Win2000s login-dialog appeared, so I took the keyboard which I thought would be the right one and entered my admin-pw.... ...guess what happened now!! The other machine did a nice & smooth blue-screen-reboot, because I typed on the wrong keyboard... everytime I type may pw on this WinXP-PC it reboots! Funny he?
Yes it's ok.
The point is:
His machine was running normal applications and so on, he is already logged in.
The point is:
His machine was running normal applications and so on, he is already logged in.
Quote:
Original post by boolean
So technically you got his keyboard and just started mashing keys, thinking you were typing a password in on your computer? lol, I wonder what you did to it!
There's a registry key you can add that forces the PC to BSOD after you press a key combination [grin]
Correct, no edit-control or something, just typed my password in -> reboot.
I also checked for sys-keys (Alt,Ctrl etc.) - nothing...just 7 letters!.
I won't post my password here, although it may be worth trying on other machines.
I also checked for sys-keys (Alt,Ctrl etc.) - nothing...just 7 letters!.
I won't post my password here, although it may be worth trying on other machines.
Quote:
Original post by Martin Foerster
Correct, no edit-control or something, just typed my password in -> reboot.
I also checked for sys-keys (Alt,Ctrl etc.) - nothing...just 7 letters!.
I won't post my password here, although it may be worth trying on other machines.
You sure it's not a problem with the keyboard?
My old password ended in SSS - and for some reason if you type SSS really quickly on this keyboard I'm using (as I type my password very quickly anyway) it'll only send a single s. Maybe your keyboard sends a weird scancode in a certain sequence which causes the machine to reboot? Improbable, I know...
There were no problems with the keyboard as far as I know.
What about that shady reg-key?
What about that shady reg-key?
Quote:
Original post by Martin Foerster
There were no problems with the keyboard as far as I know.
What about that shady reg-key?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
Add a new DWORD value and name it CrashOnCtrlScroll, value 1.
Hold down the right Ctrl key and press Scroll Lock twice. Unless that's in your password, I doubt that's it!
Start->Run type eventvwr press enter
Explore the system events
Explore the system events
That's a good idea...I will try that when I visit him again...
and post my observations here
and post my observations here
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement