Solved Windows XP Professional Bsod please help!!!

[mikiboy]

My OS is Windows XP Professional 32bit updated to SP3
- the original installed OS on the system? Windows XP Professional SP2
- What is the age of system (hardware)? my Hard disk is a little bit old, about 3years old
- What is the age of OS installation (have you re-installed the OS?) I re-installed the OS because I bought new processor (AMD Athlon x3 435)

More Info.. I hope this will also help..
Bug Check String: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code: 0x000000fc
Parameter 1: 0xb64a3d1c
Parameter 2: 0x1927b963
Parameter 3: 0xb64a3c8c
Parameter 4: 0x00000001
Caused by Driver: hal.dll
Caused by Address: hal.dll+2d43
File Description: Hardware Abstraction Layer DLL

P.S
Sorry for N.F.I. just newb in this forum.. BTW I'm using Windows XP, I hope you'll still help with this kind of OS..

 

[yowanvista]

Follow these instructions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[usasma]

Please provide us with a copy of the MSINFO32 report:

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.

The dump file cites a problem with a Windows file. I'd suggest that you run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

These older drivers may be having problems. You can look some of them up here: Driver Reference
If they're not there, then you'll have to Google them (that's why this isn't an XP forum)

[font=lucida console]
BIOS.sys     Wed Mar 16 02:23:52 2005 (4237D0F8)
ftdisk.sys   Fri Aug 17 16:52:41 2001 (3B7D8419)
AFS2K.SYS    Thu Oct 07 21:16:03 2004 (4165EA53)
ptilink.sys  Fri Aug 17 16:49:53 2001 (3B7D8371)
raspti.sys   Fri Aug 17 16:55:32 2001 (3B7D84C4)
AegisP.sys   Fri Jun 10 10:29:52 2005 (42A9A3E0)
lirsgt.sys   Sun Jan 29 06:06:18 2006 (43DCA1AA)
BS_I2cIo.sys Mon Dec 11 08:02:22 2006 (457D56DE)
mnmdd.SYS    Fri Aug 17 16:57:28 2001 (3B7D8538)
dxgthk.sys   Fri Aug 17 16:53:12 2001 (3B7D8438)
audstub.sys  Fri Aug 17 16:59:40 2001 (3B7D85BC)
[/font]

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 2600.xpsp_sp3_gdr.100427-1636
Debug session time: Sun Oct 24 11:13:31.140 2010 (UTC - 4:00)
System Uptime: 0 days 9:01:41.984
BugCheck FC, {b64a3d1c, 1927b963, b64a3c8c, 1}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+d0 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  war3.exe
Bugcheck code 000000FC
Arguments b64a3d1c 1927b963 b64a3c8c 00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[mikiboy]

I attached my MSINFO32 file and Driver Verifier. I read those driver references and searched some of those. And I also check the BUG CHECK SUMMARY that you provided, it seems war3.exe (warcraft 3) may also be cause of this error. I'm planning to re-install my OS if it can solve this errors.

 

[usasma]

Late for work, gotta run...
Dump blames AegisP.sys (AEGISP.SYS is related to AEGIS Client 3.4.0.1. Meetinghouse Data Comm or Cisco)
BUT it's not a Driver Verifier enabled memory dump
Please continue running Driver Verifier

 

[mikiboy]

Thank you for the immediate response. I ran Driver Verifier once more and I experienced 17X BSOD consistently during start up, until it recovers automatically. And I think the errors are still the same, please check the zip file I attached. BTW my cable modem is cisco 2100 cable modem.

In addition... I'll try to run Driver Verifier w/o selecting AegisP.sys, to see if there are other causes of this error.

 

[usasma]

Interestingly, the errors remain the same, but none of them are Driver Verifier enabled memory dumps.
Regardless, the procedure is the same:
- delete the Driver Verifier settings.
- download a fresh copy of the Cisco 2100 Cable Modem drivers
- uninstall the current software/drivers from your system
- install the freshly downloaded drivers and test for further BSOD's.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:16:11.171 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.765
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 891e8a48 00000002 00000001 f77c00f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:14:57.750 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.609
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88830a48 00000002 00000001 f77e80f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:13:45.750 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.593
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 889c8a48 00000002 00000001 f77e80f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:12:34.453 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.312
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 8898ea48 00000002 00000001 f77b00f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:11:22.718 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.578
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 889f0a48 00000002 00000001 f77f00f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:10:09.859 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.718
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 8917aa48 00000002 00000001 f77f80f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:08:57.281 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.140
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88970a48 00000002 00000001 f78200f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:07:44.265 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.125
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88a14a48 00000002 00000001 b83b30f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:06:31.828 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.687
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 889f0a48 00000002 00000001 a1c130f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:05:19.515 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.375
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 8920aa48 00000002 00000001 b83d30f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:04:06.000 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.859
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88a1aa48 00000002 00000001 f77a00f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:02:53.734 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:42.593
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 889a8a48 00000002 00000001 f78600f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:01:41.421 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:43.265
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88aa2a48 00000002 00000001 f77a00f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 07:00:30.218 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:41.078
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88c7ea48 00000002 00000001 f77f80f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 06:51:22.484 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:30.328
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 89444a48 00000002 00000001 f78200f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp3_gdr.100216-1514
Debug session time: Mon Oct 25 06:50:28.484 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:26.328
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 88428a48 00000002 00000001 ec4c90f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 2600.xpsp_sp2_gdr.100216-1441
Debug session time: Sun Oct 24 23:47:07.515 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:28.109
*** WARNING: Unable to verify timestamp for AegisP.sys
*** ERROR: Module load completed but symbols could not be loaded for AegisP.sys
Probably caused by : AegisP.sys ( AegisP+10f3 )
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 100000D1
Arguments 87cc4a48 00000002 00000001 ef3990f3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[mikiboy]

Thanks again for the response, I'll do the procedure that you gave.. I'm searching a new drivers right now it seems not easy to find that one though. I'll post back after I finish the procedure you've given.

BTW, I tried to use Driver Verifier w/o selecting AegisP.sys, my system ran normally. I'll try to use my pc for longer hours let see if BSOD will occur.

 

[mikiboy]

I can't found any cisco 2100 cable modem driver. I also can't found any driver update. I only found 2000 series USB driver from cisco, which is I think not compatible with my modem, because my modem is not a USB.

 

[mikiboy]

I still running my PC in Driver Verifier w/o selecting AegisP.sys, and I didn't experience any BSOD errors for 2days until now. I did re-install Service Pack 3 and updated the drivers of my MoBo.. I hope that BSOD will not occur.

 

[mikiboy]

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.

 

[usasma]

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.

 

[usasma]

nvnrm.sys - NVIDIA Network Resource Manager
a driver of the NVIDIA Network Bus Enumerator

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)
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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[mikiboy]

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?

 

[usasma]

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

 

[mikiboy]

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.

 

[mikiboy]

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.

 

[usasma]

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.

 

[mikiboy]

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.

 

[mikiboy]

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!