I did manage to talk to the guy, Wil that finally got this computer running correctly and wanted to give you some input on it. He had done the boot from disk thing and went thru the repair windows function a few times to no avail. What he learned was that when you are going thru the instal screens there is one that asked you to hit F6 to select drivers or something like that. Well you can also hit F5, especially with a laptop and select a power scheme. That is what he did and then ran the repair Windows funtion again and all worked as the BSOD was gone. He mentioned something like power supply with HCFS and I probably have that wrong but you guys probably know. LarryB K & L Electronics South Carolina LarryB wrote: Well, I met my match for sure. I was unable to fix this problem so I took it to someone that is professionally in the business. (by the way our last communique, he has less hair.)I'll let you know when it is fixed if ever. I have checked many resources to no avail. Most say good luck finding the cause. LarryB K & L Electronics South Carolina Clint Hamilton-PCWorks Admin-OrpheusComputing. com & ComputersCustomBuilt. com wrote: Many people do, (I always do), and there's no easy solution to it. It can be software, or it can be hardware causing it. The only thing I can suggest is to install that Debugger from M$ and see what it says. Go to the area like you're going to the Device Manager, but instead click the "Advanced" tab, then under "Startup and Recovery" click "Advanced Settings". Then under "System Failure" check the first box, then in the drop-down I'd suggest trying the Kernel dump first. If that takes too long or locks up the PC, then select the "Small memory dump". This will write the info into a file in that Minidump folder, hopefully. Then you can open that Debugger and load the .dmp file and see if it will tell you anything. Usually you can just drag the dmp file to the program after you open it. http://www.microsoft.com/whdc/devtools/debugging/default.mspx http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx The dmp files are not always created on BSOD's while starting or shutting down, so it may or may not create one. In my case, I'm pretty sure my BSOD's are caused by a bad motherboard. -Clint God Bless Clint Hamilton, Owner http://www.OrpheusComputing.com http://www.ComputersCustomBuilt.com http://Computer-Hardware-Sales-Consumer-Electronics-Sales.com ----- Original Message ----- From: "LarryB" I get the blue screen on shut down with the following info. IRQL_not_less_or_equal. 0x0000000A (0x000000B0,0x00000002,0x00000000,0x804EA44F) I have visited M$ and didn't learn much that was useful to me. I have installed a Kodak printer but removing it does not solve the problem. It is a all in one type printer. This is my home computer using XP Home and it is a Dell laptop. When this happens I have to hit the power button and hold it to turn it off. I can then turn it back on with no problem and nothing seems to be wrong otherwise. I have checked for malware with spybot, AVG, and Spysweeper. Nothing unusual. M$ says it could be a driver! Good how do you find the one that is the culprit? ========================= The list's FAQ's can be seen by sending an email to PCWorks-request@xxxxxxxxxxxxx with FAQ in the subject line. To unsubscribe, subscribe, set Digest or Vacation to on or off, go to //www.freelists.org/list/pcworks . You can also send an email to PCWorks-request@xxxxxxxxxxxxx with Unsubscribe in the subject line. Your member list settings can be found at //www.freelists.org/cgi-bin/lsg2.cgi/l=pcworks . Once logged in, you have access to numerous other email options. The list archives are located at //www.freelists.org/archives/pcworks/ . All email posted to the list will be placed there in the event anyone needs to look for previous posts.