Hiya everyone, I was hoping someone might be able to help me with my little problem. I have recently formatted my western digital 200gb hard drive and reinstalled windows xp, sp1 and sp2 patch for 48LBA support.

Everything was fine until I started installing a few programs, now when I shut down the computer I get a really annoying "ending program debuglog.log", I can't seem to find where this is coming from and wondered if anyone out there can help me get rid of it!

Any advice/help would be gratefully appreciated!

:gabby:

winXP is just shutting it down before it exits.
Why dont you do a search in XP for debuglog, im sure you'll find it ;)

Good Luck

Hiya,
thanx for that, can't acually find any file with this name! The only place it seems to be mentioned is in the setup.log is it okay to delete the following line from that file?
"07/31/2003 19:30:22,d:\xpclient\base\ntsetup\syssetup\oobe.c, 1127,,SetupOobeInitDebugLog"

thanxs

I'm also having a similar problem, and can't find debuglog.log

The two things I'm aware of are M$ Active X debugger in C:\WINDOWS called SETDEBUG.EXE and DEBUG.EXE in C:\WINDOWS\COMMAND (WIN98).

The only other thing but this is far fetched is if you have S.M.A.R.T enabled for your hard drive in the bios.

Originally posted by Yoda300
Hiya everyone, I was hoping someone might be able to help me with my little problem. I have recently formatted my western digital 200gb hard drive and reinstalled windows xp, sp1 and sp2 patch for 48LBA support.

Everything was fine until I started installing a few programs, now when I shut down the computer I get a really annoying "ending program debuglog.log", I can't seem to find where this is coming from and wondered if anyone out there can help me get rid of it!

Any advice/help would be gratefully appreciated!

:gabby:


It's usually a failing startup program that causes that error.

Click Start --> Run... --> Enter "MSCONFIG" to run the System Configuration Utility

In the System Configuration Utility, click on the startup tab then click on the DISABLE ALL button. Now reboot and after the system restarts, restart again to see if the error continues to happen.

Assuming that the error no longer happens re-run MSCONFIG, go to the Startup tab and enable some of your startup items a handful at a time. Then restart and repeat the test until you can narrow down which application is failing.

If it turns out that non of your startup applications are causing the failure then the problem is with one of the Services. Click on the Services tab in MSCONFIG and test by disabling all non-Microsoft services.

Insomniac:

Can you be more specific about the SMART in the BOIS? Thanks

Got the following feedback from the Microsoft Support group

See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;294876 "'Stop 0x00000044
Multiple_IRP_Complete_Requests' Error Message During a Shutdown or Standby
Operation"
http://support.microsoft.com/default.aspx?scid=kb;en-us;296734 "STOP 0x00000044
Error Message Appears While You Are Using MSMQ"


I hope it helps anyone else. As for my problem, well it has gone from bad to worse. Tonight I plan to reformat C:\ and start again with a fresh slate!!!

--
I'm suffering from the same problem, but under Windows 2000 Professional (SP4).
I upgraded my motherboard/processor/graphics card, and this DebugLog.Log error keeps comming everytime that I try to shutdown/restart. If I "End Task" on the DebugLog.Log, then I get the Blue Screen.
I've sutdown/disabled every service; removed everything from StrartUp, but I still can't find the problem.
I couldn't find the MSCONFIG opperation in Win 2K.
The Event Logs show nothing.
I've re-installed Windows, too.
I've switched off the SMART in the BIOS. Still no help.
I've installed DirectX 9.0b. Still no help.
I've got all the latest Drivers for all my hardware.
The only time I don't get the error, is if I start up in "Safe Mode".

Any idea of what service could be causing this error?
Would upgrading to XP solve the problem?
How about if I boot from a different Disk? (I only want to do this if it will definitely solve the problem).

Thanx,
D