First, a little background on this problem:

This all started after I installed Norton Internet Security 2008. It seemed to install ok, but then after I ran liveupdate to update all the components, it said I needed to restart my computer, so I did so. After it booted up again, I decided to run a system scan. It got about 15 minutes into the scan, then I got a BSOD, with the message "STOP 0xF4", which is a thread execution error. It said "Please restart the computer and if the error persists, try uninstalling the hardware or software most recently installed, or check that memory shadowing is not enabled in the BIOS settings." I had to hard boot the computer, and when it tried to go into Normal Mode, it got the STOP 0xF4 error again, so I tried going into Safe mode, and it booted to the desktop, and I went to add/remove programs to remove Norton Internet Security, and it got maybe 10 seconds into the uninstall process and then got the STOP 0xF4 error again. I then contacted Symantec technical support, but their agents weren't very helpful - one of them finally had me go in in safe mode and delete the Symantec registry keys and delete the Symantec directory, but when I tried to restart the computer, it froze, so I was unable to save the registry changes as I guess it was set to a hive structure rather than to a file structure. The Symantec support agent then referred me to my computer manufacturer, even though this problem started when I bought and installed Norton Internet Security. I then ran memchk86, as I had done some searching on the STOP 0xF4 error and found sometimes it was due to bad memory, but memcheck did 5 passes and found no errors in the memory. I then found an article that said the problem could be with my hard disk connection, so I disconnected all the cables, opened up the case, and tried changing the hard drive connector from the middle connector to the end connector in case that made a difference. I then tried going into normal mode, and got the same STOP 0xF4 error. I then tried to get into safe mode, and when I hit the F8 key at bootup, that worked, as did the arrow key and enter key to select Safe mode, but when I got to the Login screen neither the keyboard nor the mouse responded. I then tried turning off the computer and changing the USB ports that the mouse and keyboard were on, but that did not help. My computer does not have PS2 ports, so that is not an option. Please help.

Hi there and welcome to PCHF, go here: http://www.pchelpforum.com/windows-x...bsod-here.html and follow the instructions to post the logs, and post them as attachments in your next reply. A tech will be along shortly to assist you.

Please excuse the tone of the next sentence. Regarding your advice about posting the logs, this would be something that I would gladly do, if I could, but if you had read to the end of my request, you would have seen that my more immediate problem is that neither of my input devices respond enough for me to even log into Windows, either the keyboard or the mouse. Another behavior that I thought was odd, was that my mouse, which is an optical mouse, when I first power on the computer, has the LED lit up, but when I get to the login screen, it has gone out. Also, when I am at the boot options menu, I am able to turn off caps lock and num lock, but when I get to the login screen it does not respond.

Hi Zig.

Assuming it's a software issue, you PC could be crashing at the point where you would normally log onto Windows. If this is the case, then you'll still be able to use your keyboard before Windows starts.

When you switch your PC on, just past the initial post screen, keep pressing F8 on your keyboard until you reach the startup screen. At the startup screen, scroll down to "Safe Mode with Networking". You should then be able to access Windows from here, and then follow the instructions of posting a dump/log from there?

Thank you for your reply, madmonkey. I was actually trying to get into safe mode, but even in safe mode the mouse and keyboard are not responding.

Zig

Hi,

Just chipping in...could be that, as this is effective before Windows drivers kick in, we're possibly looking at bios, motherboard ports (unlikely) or the mouse and the keyboard both being faulty at the same time (even more unlikely).

Let's go with the bios for now. Can you get into the bios? If you can, please reset it to default or faile-safe mode. Reboot and test.