Blue Screen Stop Error 0x0000005

I suspect this is some type of malware file, because I cannot find this file anywhere on Google.

Does it boot into safe mode?

yes it seems I can boot into safe mode without receiving the stop message

I was able to boot up regularly and log on but like I said as all the start up featuers were loading I would get the stop message

But in safe mode it seems ok so far

Alright, let's run "Safe Mode with Networking" and then go to http://www.eset.com/onlinescan/ to run an online scan.  I would be interesting to know where this gulfd.sys file is...can you locate it?  If you find it, please post the time and date of the file into this thread.

Running the scan now

This is where the file is

c:\windows\system32\drivers
its a system file
size 174kb
created March 15, 2006  3:50:40 PM
modified March 15, 2006 3:50:40 PM
Accessed Today December 12, 2007 9:22:54 AM

Some other things to look at:  Take a look at the following web page,

http://aumha.org/win5/kbestop.htm

which is presented using frames.  Click on the error code (50) in the left pane of the page, which is a link to the following quotation:

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1548.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During setup {KB 171003} Win NT, Win 2000, Win XP
Partial List of Driver Error Codes That the Driver Verifier Tool Uses to Report Problems {KB 315252} Win XP
Easy CD Creator 5.0 Does Not Function In Windows XP {KB 310628} Win XP
STOP Error When You Start Windows After You Connect a Scanner {KB 310869} Win XP
Stop 0x1E in PROTCLS.SYS When You Undock a Toshiba Tecra 8100 {KB 284154} Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
STOP 0x00000050 Error Message in Stac97.sys After You Upgrade Your Panasonic Toughbook to Win XP Service Pack 1 {KB 329832} Win XP SP1

You should go to the actual page in order to read the links given in the quotation above.

No error were reported using that tool

I moved that file gulfd.sys to root c:

rebooted and it started up without the error..This poped up

The system has recovered from a serious Error
BCCode: 10000050
BCP1: E62EA000
BCP2: 00000000
BCP3: F8F6C9E2
BCP4: 00000001
OSVER: 5_1_2600
SP: 2_0
Product 256_1

Should I leave that file in the root?  Should I delete that file?  Should I place it back in windows/system32/drivers and see if it causes the problem again?

Thanks

Also-  everything is running in slow motion.

It takes forever to open things....longer than normal...So I was able to log on but it still seems like something is wrong

I would leave it out for a while and see if the computer behaves.  If the computer continues to operate without error, I would just leave the file there.  Shouldn't hurt anything.

return the file to its previous position, write msconfig in the run command of the startup menu and choose startup tab then uncheck the mark beside every file that you do not know its function...eg. you know that msn messenger is a program that you selected to run with windows startup so leave the mark beside it but a file called for eg. asdft.exe is a file you do not know its function so just uncheck the mark beside it and do this with all unknown or strange files. Try starting your computer normally therafter and see what happens

Should have refreshed before posting :)  If you go into the event log (Right-click my computer, manage, system tools, event log), do you see any errors in there and if so, what are they?

That is, I should have refreshed...perhaps EE can fix it so a page is refreshed when a comment is posted.  Hmmm...

Rename Gulfd.sys to something like Gulfd.sy_ and then reboot your machine. That should take care of the blue screen.

I placed the gulfd.sys file back into windows/system32/drivers

rebooted and it booted fine now with the file in that folder.

I made no other changes  so not sure why its working now

That's weird. I'm still skeptical whether the issue has been completely resolved. I'd suggest you monitor the machine for a couple of days. If the issue does resurface then rename gulfd.sys to gulfd.sy_ and then reboot the machine to see if that fixes it.

Good luck!

Not sure if this is the fix all solution but its what got me up and running again.  Moving the file to the root allowed me to get back in...however, moving it back to its original location didn't recreate the problem so perhaps this file wasn't the real reason I was receiving the error.  Either way it fixed me for now.  Thanks for the help much appreciated