ShadePopping
New Member
actually, i took it apart, and i dont think anything is out of place o_O... want me to take a picture?
Neo_0069.sys belongs to the Neo_VPN Client Device Driver
aebcl6mz.SYS gets not results - that's suspicious.
Please do this: Please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
How to locate names of drivers:
- HKLM\SYSTEM\CurrentControlSet\Services contains things like DisplayName and Description keys
- MSINFO32.exe...Software Environment...System Drivers
- Process Explorer...DLL View of the System Process
- Properties dialog box for the driver file...Details
MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
the device that uses neo_0069.sys is disabled....Go to C:\Windows\System32\drivers and locate the aebcl6mz.SYS file. Right click on it and select Properties, then select the Details tab. Does it give any information about the file?
Try this other stuff to find more info on the driver:
There's a list of the error files at my website here: BSOD IndexHow to locate names of drivers:
- HKLM\SYSTEM\CurrentControlSet\Services contains things like DisplayName and Description keys
- MSINFO32.exe...Software Environment...System Drivers
- Process Explorer...DLL View of the System Process
- Properties dialog box for the driver file...Details
STOP 0xC4 is here: BSOD Index
The dump file for that error said that NEO_0069.sys was at fault - hence my request to update the drivers (or disable it).
********************************************
Yep, it blames EagleNT.sys
That's maybe an older firewall, or an older Symantec product - or maybe this product: eaglent.sys - At your option
If you don't know what it is, please upload this for us to have a look-see:
MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
Thanks for the info on AhnLab - I've run into this before and haven't been able to get a firm answer.
Try the C:\Windows folder, then search the entire computer for them.