How to make it work without BSODs?

hi, I recently bought a new computer, but couldn't manage to make it work properly.

Intel Pentium D930
Gigabyte 8N-SLI Pro mobo
2x512 Corsair Value DDR II modules
WD2000JS SATAII HD 160 GB
Pioneer DVR 111D
Sapphire ATI x1600XT
Pinnacle 310i hybrid tv card

I'm using nforce4 drivers except from EIDE ones, which are from windows (I had cdrom errors in the app. log with bluescreens that disappeared with this treatment)
I run memtest86 from dos and had 5 passes ok.
I did that because I had a MEMORY_MANAGEMENT bsod
When I use or close some software that uses the pinnacle I sometime get bsods.
This sometimes happens also when I shutdown Windows.
I also had blue screen complaing about sr.sys and a PNF_LIST_CORRUPT while I was working with Windows' control panel.
Other bsods include IRQ_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA.
I also tried only with one RAM module (single channel, obviously). No
results, still bsods
What are the steps I must follow to troubleshot it?
Thanks in advance

 

All those errors can be caused by faulty hardware or bad drivers. Take it back and tell them to fix it, much easier. Don't try fixing it yourself as you can possibly void your warranty!!

 

(firts is most recent)

0x1000000a (0x8284db44, 0x00000002, 0x00000000, 0x805057fe)
0x10000050 (0x86e9ec90, 0x00000000, 0x8055259a, 0x00000000)
0x0000004e (0x0000008f, 0x00018597, 0x00018557, 0x00000000)
0x10000050 (0xa1af2048, 0x00000000, 0xf76f7a70, 0x00000000)
0x0000001a (0x00003451, 0xc029fa34, 0x85364790, 0x00000000)
0x1000000a (0x00000004, 0x00000002, 0x00000000, 0x804e85f5)
0x1000000a (0x00000028, 0x00000002, 0x00000001, 0x804ecb94)
0x000000c2 (0x00000007, 0x00000cd4, 0x00130046, 0x8508b238)
0x00000035 (0x85450c00, 0x00000000, 0x00000000, 0x00000000)

The fact is that the event viewer doesn't display any error, just the

SaveDump.
Is there a way to infer which driver failed to operate which hardware?

Some of those Bsods appeared during shutdown, e.g. the first

(0x1000000a): seems like a driver that failed to close a peripheral.
I already tried a clean reinstall, but it didn't help.
When I took it back they told me to try with single channel ram, and

that improved stability (so maybe were due to ram), so maybe the two

modules were not so alike as they should to work in dual channel, but I

still got the last bsod (0x1000000a - which is IRQL_NOT_LESS_OR_EQUAL -

when shutting down).
thanks for attention
Paolo

 

There is . Analyzing the minidumps can provide info on the failing driver. You can do this yourself, or post the minidumps here (zipped). Minidumps can be found at c:\windows\minidump. The most recent ones will hold the best info.

 

Well, maybe you should have said "You can do this yourself... If you have an ADSL"... Symbol library for xp sp2 are some 190 Megs and I only have a 56k

I'm sending dumps: know that the last, Mini091406-01.dmp is probably the last problem I have -IF- the rest were due to Dual Channel RAM, so that's the one I'm most interested in.
I really apreciated all the help this forum is giving to me, if I knew it was so good I would have spared me some 3 months of pain... but at least I can say that I tried all by myself first.
Thanks again,
Paolo

 

Which version of zonealarm do you have installed?

Included is the debug result of mini091406-01.dmp
The error IRQL_NOT_LESS_OR_EQUAL usually points towards a failing driver. Since the cause is set to "memory_corruption", it is caused by corrupted kernel memory. This is always caused by a faulty kernel driver.
The first driver to suspect would be vsdatant.sys, the TrueVector driver installed by ZoneAlarm. I think this because one of the dumps points to it and because it has been known to cause problems. Which version do you have?

(You can determine which driver is failing using the Driver Verifier, although it is not very easy to use)

 

ZoneAlarm version:6.0.631.003
TrueVector version:6.0.631.003
Driver version:6.0.631.003

I know it's quite old. I will download an update immediately. The other bsods disappeared after using single channel ram, so the modules or, at worse, the mobo were to blame.
Thanks a lot, that solved my problem.
Paolo