Best Answer: i also have the 9800GX2 i love it to death,
most likely you up-ed the clock speed to high and that causes it to crash, boot safe mode with networking and download nTune if you dont already have it. its a program from nVidia that helps with well… tuning. download it open it and go to performance. first go to adjust GPU setting, in that windows make sure the GPU clock settings are set to "factory shipped clock frequencies" then go to tune system and run a 20 min "coarse tuning" this should help
make sure core bus is set no higher than 600Mhz and the memory bus no higher than 1000Mhz
good luck and try not to mess up any more $500 video cards =P
let me know if you need any more help. its always nice to help out another nvidia user.
Satellite Channels
Re:A sincere thank you to all that helped me figure this BSOD out, especially guy. I pulled ZoneAlarm from the affected system and waited roughly one month, which was beyond the upper limit of the bluse screen frequency, and the problem has yet to reappear. To be scientific, I could have put ZA back on, but I would most certainly use the latest version which may have corrected the issue, thus negating the accuracy of the test.
Change Your Mind, Change Your Life
Re:I've actually seen a lot of Dells (Desktops, notebooks, and even some of their lower-end servers) end up with these inevitable un-curable BSOD's, and recently, one of my colleagues discovered that Dell actually has a great tool for analyzing the drivers on any Dell machine, though ATM, I can't remember what it's called…
Anyways, have your associate enter the service tag of the machine on the Dell website, and then manually search for a 'driver analysis tool' or something like that; it's not listed in their normal tools for the individual machines. I wish I could say for certain that it'll help you come upon the fix for your BSOD's, though on four different Dells, i've seen it work to solve these wonderful little M$ quirks 
Good luck.
30 Days to Change Your Life
Re:Originally posted by: guy
What tools do you use to analyze the minidumps? I opened this one up in notepad and could not find the string "ZONE" nore "Z O N E". Is there special software that can make this soemwhat more readable?
On Microsoft's site, you can download the "Debugging tools for Windows" packages.
However, unless you're a device driver author, and/or are VERY familiar with assembly language AND the internal workings of Windows, you're not likely to have much success in looking at dump files.
Kernel mode debugging is what sets the ubergeeks apart from the merely freakish geeks. It's part science, part art, but mostly black voodoo magic.
Life-Changing Weight Loss
Re:Originally posted by: guy
In my experience, PAGE_FAULT_IN_NONPAGED_AREA is almost always bad memory or a flaky motherboard/memory controller.
Your experience and mine are different. My experience is that a STOP 0×50 is almost always a poorly written driver.
My experience includes working technical support for a large software company troubleshotting blue screens and reading dump files. 
Dump Mini121405-01.dmp was caused by a system worker thread. It's impossible to tell from the dump what thread submitted the task for the worker thread to do; we'll never really know the cause of this crash.
Dump Mini100605-01.dmp was the same thing.
Dump Mini010506-01.dmp was a STOP 0xC2 and was caused by vsdatant.sys, which I believe guy correctly identified as a Zone Alarm driver.
The best start to fixing this is to ensure that you're running the latest version of Zone Lab's drivers.
If problems persist, configure your machine to write a Kernel dump instead of a mini dump. (System control panel, advanced, startup and recovery.) A kernel dump has a lot more information in it.
OmniPCTV – Unlimited Access to Over 3,500 Hd Channels
Re:There's conflicting errors. Probably memory gone bad.
Probably caused by : vsdatant.sys ( vsdatant+3e6e1 )
Probably caused by : ntoskrnl.exe ( nt+9577b )
Probably caused by : ntoskrnl.exe ( nt+9577b )
Run memtest86 first.
Successful Life Strategies to Capitalize on Change
Re:Originally posted by: guy
What tools do you use to analyze the minidumps? I opened this one up in notepad and could not find the string "ZONE" nore "Z O N E". Is there special software that can make this soemwhat more readable?
WinDbg tools with kd!analyze command.
Info for modules in D8F0RR61_MPSReports.CAB\D8F0RR61_SYSTEM32_SYS.TXT
Start Your Own Real Sky Tv Channel
Re:Don't guess. C'mon guys! Dumps are available…. with those, we don't need to guess – we can know what's going on (with a pretty good amount of certainty.)
If it is indeed a hardware problem you can't trust the minidumps. Bad memory, dying PSU, too much dust on some contacts, etc could all cause random BSODs that point to different drivers each time or just by dumb luck point to the same driver each time.
Dare to Change Your Job and Your Life — Acclaimed Book
Re:Originally posted by: guy
Don't guess. C'mon guys! Dumps are available…. with those, we don't need to guess – we can know what's going on (with a pretty good amount of certainty.)
You've posted the minidumps, so let's look at those. I looked at the most recent dump from 1-5-06, and that said your problem is Zone Lab's software:
Module[ 19] [C:\WINDOWS\SYSTEM32\VSDATANT.SYS]
Company Name: Zone Labs, LLC
File Description: TrueVector Device Driver
Product Version: (6.1:737.0)
File Version: (6.1:737.0)
File Size (bytes): 372816
File Date: Tue Nov 15 00:50:34 2005
Module TimeDateStamp = 0×43798224 – Tue Nov 15 01:37:24 2005
Module Checksum = 0×0006538c
Module SizeOfImage = 0×00059940
Module Pointer to PDB = [vsdatant.pdb]
Module PDB Signature = 0×43798224
Module PDB Age = 0×1
So remove that and let's see if the BSODs go away.
(By remove that, I mean completely remove all Zone Labs software on the machine, reboot, and enable the built-in Windows firewall, and then check how the machine works.)
What tools do you use to analyze the minidumps? I opened this one up in notepad and could not find the string "ZONE" nore "Z O N E". Is there special software that can make this soemwhat more readable?
TVonPC Elite – 2000+ Tv Channels And Radio Stations On PC And Laptop
Re:Don't guess. C'mon guys! Dumps are available…. with those, we don't need to guess – we can know what's going on (with a pretty good amount of certainty.)
You've posted the minidumps, so let's look at those. I looked at the most recent dump from 1-5-06, and that said your problem is Zone Lab's software:
Module[ 19] [C:\WINDOWS\SYSTEM32\VSDATANT.SYS]
Company Name: Zone Labs, LLC
File Description: TrueVector Device Driver
Product Version: (6.1:737.0)
File Version: (6.1:737.0)
File Size (bytes): 372816
File Date: Tue Nov 15 00:50:34 2005
Module TimeDateStamp = 0×43798224 – Tue Nov 15 01:37:24 2005
Module Checksum = 0×0006538c
Module SizeOfImage = 0×00059940
Module Pointer to PDB = [vsdatant.pdb]
Module PDB Signature = 0×43798224
Module PDB Age = 0×1
So remove that and let's see if the BSODs go away.
(By remove that, I mean completely remove all Zone Labs software on the machine, reboot, and enable the built-in Windows firewall, and then check how the machine works.)
How Your Mind Change Will Change Your Mind
Re:In my experience, PAGE_FAULT_IN_NONPAGED_AREA is almost always bad memory or a flaky motherboard/memory controller.
Burn the bootable memtest86+ to a CD (or download the boot floppy version) and let it run on the machine overnight. Any errors indicate bad memory or a misbehaving memory controller (ie, bad motherboard), or rarely a CPU problem.
If that passes, download prime95 and run its torture tests ('Blend' seems to be the most demanding) for at least 12-24 hours. Errors indicate hardware instability, or possibly a corrupted OS/drivers (but usually bad hardware).
Re:Originally posted by: guy
Most likely a bad driver of some sort. If not that, do a memory check (memtest86). Also a small possibility it's the PSU.
What is the error message on the BSODs? Is that consistent? Does it consistently list the same driver *.sys file causing it? Disable automatic reboot and enable minidumps as well.
Please see my edited post. I had neglected to link to the real technical information that I was able to gather.
Re:Most likely a bad driver of some sort. If not that, do a memory check (memtest86). Also a small possibility it's the PSU.
What is the error message on the BSODs? Is that consistent? Does it consistently list the same driver *.sys file causing it? Disable automatic reboot and enable minidumps as well.
0 Comments.