PC Chips A11G (nForce 410) Motherboard BSOD @ Boot

[GnatGoSplat]

I replaced a Celeron 300A, Abit BH6 combo with an AMD Sempron 64 AM2 2800, PC Chips A11G (nForce 410 / GeForce 6100) mobo, 512MB DDR2. HD is a Seagate 120GB.

The old Windows XP SP2 install would BSOD on bootup. Nothing unusual, that's happened before on previous mobo swaps (especially switching to nVidia from Intel or Via). In an attempt to save the old install, I attempted a Repair. That did not take care of the BSOD problem. I did discover that it was able to boot in "Enable VGA Mode" and worked just fine. I figured a residual driver or registry setting caused the BSOD, so I completely wiped, repartitioned, reformatted, and performed a clean install of WinXP SP2.

No more BSOD. I installed all the nVidia drivers. WindowsUpdates. Perfect, all is good. I thought I took care of the problem, and give it back to my stepdad (the owner).

He installs SBC Yahoo DSL software to get his USB DSL modem connected. It installs the drivers and such. When it reboots, BSOD!!! It does it even with the modem unplugged. I try "Enable VGA Mode". It works. Ugh. So the original problem was probably the SBC Yahoo DSL software or drivers all along, BUT it worked fine on the old mobo!

No cards are installed in any slot.

Anyway, I have tried the following, each with no change:
- Installed the latest nVidia ForceWare drivers from nVidia.com (newer than the PC Chips CD-ROM).
- Installed the latest GeForce drivers.
- Tested memory using MEMT86 forl hours... no errors.
- "Enable boot logging" - no log is ever saved before the BSOD.
- Checked the event viewer - no errors are logged.
- Uninstalled Yahoo DSL software. No change.
- Disabled all onboard devices (sound, SATA, USB, parallel, etc) in BIOS except the IDE controller and video.
- Changed Auto config to manual.
- Changed Reset ESCD to Enabled.
- Updated to the latest BIOS release.

Details on the BSOD are as follows:
- Occurs immediately after "Windows XP" shows up. Usually BSOD's before anything even appears in the progress bar.
- No drivers are referenced, the BSOD apparently happens too early for logging.
- Technical information: *** STOP: 0x0000007E (0xC0000005,0x00000000,0xF79470C0,0xF7946DBC)

I'm having no luck and a Google search doesn't seem to reveal anyone with this problem. I'm about ready to RMA the motherboard as a last resort.

 

[elmer92413]

You don't need to install any software to use the DSL...
So fix it again and don't install the Yahoo stuff...
I have SBC DSL and don't need the software...
You just have to access the modem to login and put in the Access Code, found on a sticker on the modem...
...
..
.

 

[GnatGoSplat]

Thanks for the reply, but even after removing the Yahoo software, the computer still won't boot.
I just have to wonder if the Yahoo software does this (which works fine on any other machine), what other software will eventually cause the same problem? It makes me think the board could be defective.

 

[GnatGoSplat]

Problem solved! I finally plugged the right keywords into Google: "sbc yahoo" bsod. I don't know why I didn't think of those keywords before, duh! It seems this problem is very widespread with the Yahoo software. Several solutions said to delete IPVNMON.SYS. I did that, rebooted, no more BSOD!

So the problem is definitely the Yahoo software and NOT the motherboard. Whew! RMA'ing a motherboard is a huge hassle and I'm glad I didn't have to go to the trouble. Unfortunately, I also discovered PC Chips tech support is non-existent.

 

[dclive]

Originally posted by: GnatGoSplat
Problem solved! I finally plugged the right keywords into Google: "sbc yahoo" bsod. I don't know why I didn't think of those keywords before, duh! It seems this problem is very widespread with the Yahoo software. Several solutions said to delete IPVNMON.SYS. I did that, rebooted, no more BSOD!

So the problem is definitely the Yahoo software and NOT the motherboard. Whew! RMA'ing a motherboard is a huge hassle and I'm glad I didn't have to go to the trouble. Unfortunately, I also discovered PC Chips tech support is non-existent.

True, but in all honesty this isn't a PCChips problem - it's a MS/SBCY problem. MS/SBC have ways to help you with this - MS can step you through reading the dumpfile to get to the cause of the problem, no guessing required...

 

[GnatGoSplat]

Yeah, it was not a PCChips problem, for which I am very glad! It also turned out PCChips tech support did reply back, it just took nearly a week. He said he'd seen the problem before and to rebuild the machine without using SBC Yahoo software. Apparently, he wasn't aware of the exact cause on a file level. Anyway, it wasn't really an MS problem either, it was entirely the fault of the company that wrote IPVNMON.SYS (I forgot their name already, Virtual IP Networks or something like that).

 

[eplebnista]

Thanks for the update and solution! :thumbsup: