Error 0x0000007f

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Just in case anybody is getting a similar error:

I was getting a stop code of 0x0000007f every 20 minutes after switching on
my machine. I narrowed this down to when the scan routine was running in
Windows Defender, the error also occurred on a manual scan. I found out that
a file on my machine called BOCOLEF.DLL is causing this issue. Even if I
select the file to look at its properties it still crashes the machine.
Therefore although I only got this issue when running Windows Defender, it
looks as if the cause lies elsewhere.
 
I'd strongly recommend a chkdsk /f (you'll probably need to restart and
allow the chkdsk to proceed on boot)
 
Thanks for the reply, I did try a chkdsk and got some minor inconsistencies.
The file however still caused issues when you clicked or attempted to copy
it, even within the command prompt. I have now deleted the file as it
resides from a very old version of Borland C++ that was installed over a year
ago. I did previously run several scans using other software and never
encountered this error, but I also received the same error using the Mcafee
online virus scan.
 
This is interesting. I think if I'd been more awake I would have requested
a copy of the file--but probably generating that would cause the crash?

Do you have either event log entries, or, better yet, memory dumps related
to these crashes? I don't think dumps get generated for application
crashes?

I'm concerned--because if there really was no filesystem problem
involved--if the only issue was data content--this surely is a bug that
needs addressing.

I'd love to see pastes of the details of system event log entries related to
these crashes, and if you have memory dumps, I think I could find folks
interested in seeing them, even though this doesn't appear to be a Windows
Defender problem, per se.

--
 
Hello Andy,

Have a look at this article. It may be relevant to your prºblem.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

http://wiki.djlizard.net/STOP_errors

I suggest you D/L Ccleaner and Dial a fix.

In safe mode ran CCleaner

After CCleaner use Dial a Fix Do a scan with all the check marks on.

Run again Ccleaner

Reboot

Go to http://safety.live.com/site/en-US/default.htm
Look for the broom Clean up, also Tune Up..

Reboot


http://www.ccleaner.com/downloadbuilds.asp
Ccleaner - http://www.ccleaner.com
Note, When you install Ccleaner, uncheck the Yahoo toolbar option.
Note, in Options, Advanced, uncheck - Only delete files in Windows folders
older than 48 hours.
Note: uncheck Windows Defender in the applications.
Do scan with all the check marks on.
Open Ccleaner and press "Windows" "Aplications" and Run Cleaner from the
menu choose 'Issues' and then press scan for issues, Repair any fºund.
Run twice Ccleaner, the same as above,until you get “0 bytes to be removedâ€.


Dial-a-Fix
downloaded it here:
http://fileforum.betanews.com/detail/Dialafix_Full/1131569373/2
The EXE file from here
http://djlizard.net/Dial-a-fix-2006-09-19.exe
Please take some trime and read Windows Internals, Troubleshooting, and this
page http://wiki.djlizard.net/Special:Allpages

I hope this post is helpful.

Let us know how it works ºut.

Еиçеl
 
Some further information..

The file is extremely old i.e. dated 1994 and was released prior to the
official release of Win32. I again received the stop code after doing a full
scan, but this was due to the file now residing in the restore point
directory. I have managed to rename the file and removed the .dll extension,
and Windows and Defender do not have any issues with the file now. It seemed
as though Defender only started to issue the stop code after an update from
1.14.1704.2 to 1.14.1706.7. I can provide a copy of the file if required.
 
I'd love to have a copy of it, if you will: I'd recommend zipping it up and
password protecting it with the password "infected"

I realize this is not the case, but zipping and password protecting help in
moving such files intact between various systems, and we might as well use a
standard password.

I will make sure that it gets to the Windows Defender team with some
background information--you've given lots of useful details. I'm not sure
what to call this--it isn't exactly a false positive, but file data
shouldn't crash the app--and I'm sure the developers would be interested.

--
 
Whoops:

bill_sanderson @ msn.com

(remove the spaces.)

If, for whatever reason, you'd prefer to submit directly to a Microsoft
address, I suggest one.

--
 
Andy said:
Just in case anybody is getting a similar error:

I was getting a stop code of 0x0000007f every 20 minutes after switching on
my machine. I narrowed this down to when the scan routine was running in
Windows Defender, the error also occurred on a manual scan. I found out that
a file on my machine called BOCOLEF.DLL is causing this issue. Even if I
select the file to look at its properties it still crashes the machine.
Therefore although I only got this issue when running Windows Defender, it
looks as if the cause lies elsewhere.
Click to expand...

Could this be related to the "CPU usage at 100%" bug mentioned in
another thread
(news://privatenews.microsoft.com:119/[email protected])?

Theoretically, if your hardware is unstable, and your CPU overheats, it
will crash windows.
 
That's never been specific to a given file. This is pretty strange--I
really expected to see a filesystem problem--or disk error of some sort,
since the crash happens with different apps, just the same data.

I've tested the file in question on my own system with Windows Defender with
current definitions, and nothing blinks.

--
 
Back
Top