New
#11
I experienced another BSOD. Please check the file I attached, it seems like it something to do with kernel. I encounter this error while using driver verifier, I already used my PC in longer hours.
I experienced another BSOD. Please check the file I attached, it seems like it something to do with kernel. I encounter this error while using driver verifier, I already used my PC in longer hours.
Go to C:\Windows\System32\drivers and find AegisP.sys
Rename it to AegisP.BAK
Then use the free program Autoruns (available here: Autoruns for Windows ) to stop the driver from attempting to load.
Download the Chipset-Ethernet driver on this page: BIOSTAR :: MCP6PB M2+ :: Driver (the nvnrm.sys driver is dated 10/28/2009 - the same date as the one currently installed on your system)nvnrm.sys - NVIDIA Network Resource Manager
a driver of the NVIDIA Network Bus Enumerator
Then uninstall the current ethernet drivers/program
Then install the freshly downloaded drivers
Monitor for further BSOD's - if they continue, then you'll have to consider that there may be a hardware problem with the network card.
BSOD BUGCHECK SUMMARY
Code:Built by: 2600.xpsp_sp3_gdr.100427-1636 Debug session time: Tue Oct 26 13:56:54.734 2010 (UTC - 4:00) System Uptime: 0 days 0:52:04.581 *** WARNING: Unable to verify timestamp for NVNRM.SYS *** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS Probably caused by : NVNRM.SYS ( NVNRM+91d0 ) DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: Idle Bugcheck code 1000000A Arguments 00000016 00000002 00000001 8065f94d ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
I already did what you've ask. For now I'm trying to see further error, by the way what is the cause of my errors? Is it by the AegisP.sys or something to do with kernel?
You have an issue with the AegisP.sys driver.
You must rename it if you can't replace it.
Until then the dump files aren't going to be very useful.
We need to test the new state of the system without the AegisP.sys driver.
In the latest dump file the AegisP.sys file is still loading, indicating that it hadn't been removed/renamed as of Tue Oct 26 13:56:54.734 2010
If the errors keep coming in NVNRM.SYS after AegisP.sys has been removed/renamed - then we have to wonder about other elements in the networking subsystem. But that won't be an issue until AegisP.sys is renamed AND you have further BSOD's
Hello again, I already renamed the AegisP.sys to AegisP.BAK as you've said. I think its almost 2days since I renamed the AegisP.sys and I didn't experience an error since then. I also downloaded and installed the driver that you've said. I hope the error is really fixed.
Last edited by mikiboy; 28 Oct 2010 at 11:59.
Another BSOD just encountered, I already renamed the AegisP.sys as I've said earlier. But then I experienced another error and I think it also something to do with NVNRM.SYS. Please take a look to the file I attached.
This one points to nvenetfd.sys - another component of your nVidia networking controller.
As such this is the 3rd error and each blames a different driver. In most cases this is a symptom of a hardware problem.
Normally I'd run Driver Verifier at this point, but as we had no luck with it previously I don't think that it's going to help.
So, I'd suggest the following:
- update your nVidia driver from this page: BIOSTAR :: MCP6PB M2+ :: Driver
Select the Chipset-Ethernet driver.
If that doesn't stop the problems, then try another Ethernet card. Be sure to disable the onboard one in the BIOS while testing the new card.
Thank you for the response. I already updated my nvidia driver when I encountered the latest error. It seems I'll give it a try to use another Ethernet card. I'll post later when I already installed my new Ethernet card. Thanks again.
Hello, I already installed my new Ethernet card and I'm running Driver Verifier, my PC runs without problem. I'll use my PC for longer hours to see if error/s still occur. I'll post back for further updates. Thank you!
Last edited by mikiboy; 29 Oct 2010 at 00:56. Reason: Correction