Soyo SY-7VBA133U

[ChaosBlizzard]

I just bought a new soyo SY-7VBA133u motherboard. I have noticed the system had 3 critical errors and win2k forced a shutdown, It has also freezed on me once. The board is now 1 month old. Are these boards still shipped with those crap caps? If so what brands do they go by on soyo boards? The board cost me $73.00, so I feel its worth fixing if it is something as simple as the caps.


Thanks,
CP

[willawake]

You should post the manufacturer of your caps here so ppl can advise further.

Please also past those errors from your eventlog here and give more information about the "Windows forced a shutdown" do you mean that the computer just went off or did it advise something like "Windows must now restart because Remote Procedure Call (RPC) Service terminated"

could be a virus. Update your virus definitions and do a full scan of your system. If you dont have a firewall you really need one these days.

[kc8adu]

look out for system authority service or somesuch error with lsass?
sasser worm does that.

[ChaosBlizzard]

Im aware of sassar and its abilities. I have dealt with it on a clients system. Also I mean the system had some kind of critical error that forced the system to just go off in an instant, with no error or blue screen. Its only done it twice so far. But still a windows 2000 machine doing that? If it was windows xp I wouldnt have double checked this..

Well I have three of these in my system log:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 5/7/2004
Time: 7:24:46 AM
User: N/A
Computer: NONE-K9GUMZOWEK
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000009, 0x00000002, 0x00000000, 0x00000009). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini050704-01.dmp.

[willawake]

Yes the problems with win2k are less but some of them can be a pain, mostly driver issues causing win98 style crashes, capacitors, memory or hdd failing and corrupting the os and also virii causing crashes. Otherwise I love it and it has made my worklife much better, especially event viewer.

Win2k is set by default to automatically reboot on system failure
(control panel/system/startup and recovery - system failure - automatically reboot)
so the fact that your comp does not blue screen is because of this setting being on. win2k can blue screen at boot though and also totally stick when in windows. If you disable the automatic reboot then you will get a nice Driver IRQL Less Than or Equal BSOD for your 0x000000d1.

You can decode the dump to find the offensive driver or check what you are doing when it happens again.

Gathering Blue Screen Information After Memory Dump in Windows 2000 or Windows NT
http://support.microsoft.com/?kbid=192463

You can also search the microsoft knowledgebase for 0x000000d1 which brings up quite a few specific driver related issues.

0x000000d1 (0x00000009, 0x00000002, 0x00000000, 0x00000009)

0x000000d1 - STOP Code - Driver IRQL Less Than or Equal
0x00000009 - Parameter 1 - Memory Referenced
0x00000002 - Parameter 2 - IRQL at time of reference
0x00000000 - Parameter 3 - Type of Access (0x00000000 = read, 0x00000001 = write)
0x00000009 - Parameter 4 - Address that referenced memory

Interesting but not enough information at all for a solution until you decode the dump.

[willawake]

Some more links

How do I gather information after a Windows 2000 memory dump (BSOD)?
http://www.jsiinc.com/SUBK/tip5000/rh5007.htm

Pstat.exe: Process and Thread Status + Download pstat.exe
http://www.microsoft.com/windows2000...ng/pstat-o.asp

How to Use Dumpchk.exe to Check a Memory Dump File
http://support.microsoft.com/default...b;EN-US;156280

[ChaosBlizzard]

Yeah windows 2000 is my favorite operating system too. I already knew about the default settings. As well as where the mini dumps are stored. I just dont have anything to decode them with.... I think it may be an irq issue anyway. I have about 6 devices using irq 11 when I have pleny avalable for use... Just have to figure out how to enable manual selection. I remember seeing something in the bios.

[ChaosBlizzard]

Ok I "decoded" my minidumps..

Mini #1:
----------
Filename . . . . . . .C:\winnt\minidump\Mini050304-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x81863000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x00000009
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000009

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3

Mini #2
----------
Filename . . . . . . .C:\winnt\minidump\Mini050604-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x81863000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x00000008
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000008

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3

Mini #3:
-----------
Filename . . . . . . .C:\winnt\minidump\Mini050604-02.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x81863000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x0000000c
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x0000000c

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3

Mini #4
----------
Filename . . . . . . .C:\winnt\minidump\Mini050704-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x81863000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x00000009
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000009

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3


Which codes should I cross reference with the microsoft database?


Thanks,
CP

[ChaosBlizzard]

Sorry I am posting so much and that this is off topic. I just wanted to include my irq list. It might help.

System Information report written at: 05/11/2004 11:00:06 PM
[IRQs]

IRQ Number Device
5 Microsoft ACPI-Compliant System
11 Amigamerlin 3.0 for voodoo5 5500 AGP
11 VIA USB Universal Host Controller
11 VIA USB Universal Host Controller
11 VIA AC'97 Audio Controller (WDM)
11 Standard OpenHCD USB Host Controller
11 Linksys LNE100TX(v5) Fast Ethernet Adapter
14 Primary IDE Channel
15 Secondary IDE Channel
8 System CMOS/real time clock
13 Numeric data processor
6 Standard floppy disk controller
4 Communications Port (COM1)
3 Communications Port (COM2)


As you can see I have plenty of room for many of those devices using irq 11, they shouldnt be jamed together like that.

[willawake]

XP and 2000 use virtual IRQs so that many devices can be on IRQ 9,10 or 11. Some devices can be totally happy, others devices with specific hardware or badly written drivers do not like this. I still have not made up my mind whether it is better to let windows or the mobo handle the assignments. I usually set PNP os to not installed in the bios when i install windows but sometimes forget. Some mobos can also make messy assignments anyway and you have to check the manual to see which pci slots are sharing IRQs. If i have a major problem device i would reserve an IRQ in the bios for that PCI slot.

The problem devices in your system could be either the via audio or the Linksys nic. i have seen threads on both. Particularly the linksys if you check this thread :

http://www.tek-tips.com/gviewthread..../750/qid/75282

which suggests similar reboots with certain versions of the driver. Those minidumps are quite similar indeed, nothing like the wierdness of ram or capacitor failure. What you need to do is get pstat and run it.

http://www.microsoft.com/windows2000...ng/pstat-o.asp

In the last section you will see the modules loaded and their Load Addr.

For instance

ModuleName Load Addr Code Data Paged LinkDate
----------------------------------------------------------------------
ntoskrnl.exe 804D4000 449216 99264 735168 Thu Jul 18 05:39:51 2002
hal.dll 80670000 31808 8128 22048 Wed Mar 20 16:35:10 2002

You find the load address which is just lower or equal to your ExceptionAddress . . .0x804690f3
and that will be the offending module. But i am thinking that 0x804690f3 will be close to ntoskrnl.exe which will not be helpful. It is a pity but it is worth to go down this route we are going, cos sometimes you get lucky.
(sometimes you get close to a driver file or a file related to a common driver issue and that is very useful then because you know the problem device exactly)

Can you pinpoint when the problem occurs. Is it when you are on the net via your linksys? To keep this thread relevant you could post the brand of the caps on your board and ppl here can tell you if you will have problems with them in the future. tell us if you have better success with other linksys drivers.

[ChaosBlizzard]

Well I replaced my linksys NIC with a NetGear NIC, I still get problems when going over 60 network connections. I think microsoft needs to fix these issues in the next service pack.

For example I now get this (Looks like its still the NIC, seeming how the message is pretty much the same):
****************************************************************
**
** Windows 2000 Crash Dump Analysis
**
****************************************************************
*
Filename . . . . . . .C:\WINNT\Minidump\Mini052404-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x81863000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x014f1114
BugCheckParameter2 . .0x00000002
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0xf9c88c5c

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3

[willawake]

That dump looks the same thing - ntoskrnl.exe not happy with something, great that tells us nothing. You have determined that the error is when you have 60 network connections. That is good, now you have to find the source. You could specify to have a more detailed dump in the control panel/system/startup and recovery but again it may say nothing.

I am not aware of the chipsets of the netgear and the linksys. I hope they are not the same. The problem is that when you are troubleshooting like this you really need to get a card like an intel or 3com nic that has excellent drivers and knowledgebase to eliminate the problem and therefore confirm that it is indeed the nic that is the problem.

(I do not intend to netgear bash, i do not have experience with them but i have been impressed with their offerings. I will buy a netgear 24 port switch as a backup for a cisco soon.) it is just that i have been totally satisfied with 3com and intel nics.

the thing is that with your changing the nic and the problem persists. then i am tending towards a mobo chipset issue or software issue as you said. Can you please expand on the 60 network connections issue as i am not grasping it. I assume you are on SP4.