CPU/Mobo Need help with P5N32 E SLi

Status
Not open for further replies.

iml3g3nd

Explorer
i m havin frequent BSOD with this mobo !

some IRQ error !!!:(

does nyone know how to diagnose this????

is there a propability of faulty RAM??

i have also included a pic of the BSOD
 
yup from the screenshot it seems like the problem is becuz of your network card. are the drivers installed correctly? have you installed any network softwares on your pc? .. it may be causing the error.
 
so ll reinstalling the cable modem drivers help??????

but i have reinstalled Windows freshly twice before but still the problem persists!!!!!!!:(
 
if anyone needs more info on my system config to help me diagnose this error pleast let me know !!!i ll post it !!!!!!
 
Try the second network port and disable the one you're currently using.

Also set PnP OS in BIOS menu to 'No' if it's not already.
 
i m not usin ny network port !!!
no NIC

i m usin a usb cable modem !!

check the link above !!!

and i ll disable the PnP!!!
 
Doesnt matter if you are using network port or not. If you installed the network card drivers and said yes to installing NVIDIA Forceware Network manager, the firewall will be installed. Thats the root cause of all these bsods. I had the same damn issue for a week and couldn't figure out what it was until I disabled the firewall by accident :P.
 
turnin off the windows firewall ll rurn off nvidia firewall ryt ???????
if it does not then tell the procedure how to disable nidia firewall???
 
dude i dont have nvidia firewall drivers installed on my system !!!
just display drivers and nvidia ntune!:(

so ny other alternative???
 
1. Disable the network ports in BIOS. You can find them under 'Onboard device configuration' in the 'Advanced' menu in BIOS.

2. Uninstall all nVidia devices from Device Manager (right-click on my computer, properties, hardware, device manager). Don't let the system restart (say 'No' to any automatic restart requests).

3. Uninstall all nVidia software from the Control panel.

4. Restart the system in safe mode

5. Delete all files beginning with nv in the C:\windows\system32

6. Open this directory: c:\Windows\inf and start opening the files named oem0.inf, oem1.inf, etc. Delete the files which relate to the nVidia hardware. You can read which hardware device the file belongs to, in the first few lines of the file.

7. Reboot and see if you're still getting BSODs. If you are, the problem is a general hardware failure, either of the modem or the chipset southbridge. If the BSODs stop, it's time to install the drivers again.

In case the latest drivers don't work, try a few of the older ones. Sometimes new drivers (the latest is Nov 2006 for this board, btw) may break the system.
 
one last q!

is these BSODs harmful to system hardware in nyway?

i mean the cpu,motherboard,gpu etc...................
 
guys gettin to the root of the problem.....

@ sangram

dude i checked the inf file u said !!!

and on the inf file for the usb cable modem i found the .sys file which was makin the BSODs!!

check the pic i provided!!

now will reinstalling the cable modem driver help????
but as i said earlier i have already reinstalled the drivers for modem many times bfore!!!!

just a liitle bit more on diagnosing this error guys so help me out!!:hap2:
 
Try to use the network cable instead of the USB cable - the modem can connect to both. You need to enable one port on your PC, and don't install the firewall drivers when the system prompts you to.

Please read my post carefully and follow it to the letter. In case of more trouble take it to a technician. Remote troubleshooting is not going to be possible beyond a point if you're not comfortable hacking into system files.

For example, NDIS is a generic descriptor for network interfaces. It does not matter whether it is connected to a USB port or a network port. There is a massive difference between NDIS.sys and the file you have opened, oem3.inf

Would suggest you ask a service technician to come in and take a look, as I cannot guarantee the safety of your system from here.
 
Status
Not open for further replies.