All drivers , save for the sound card drivers (as the new ones cause all sorts of issues) are up to date as of yesterday, as is windows. Ive got a few minidumps in that folder, not sure what ones are new, or old. Should i just wipe that folder and wait for a new error to ensure that minidump is the correct one?
All drivers , save for the sound card drivers (as the new ones cause all sorts of issues) are up to date as of yesterday, as is windows. Ive got a few minidumps in that folder, not sure what ones are new, or old. Should i just wipe that folder and wait for a new error to ensure that minidump is the correct one?
I don't see anything in this dump - the dump says driver, but points to a driver that typically points to hardware. Are you normally clocking everything? Do you have any more dumps you can give me?
I know for a fact that the Bet On Soldier demo uses Starforce (I think that's what it's called) to protect it (copy protection). Unfortunately, this technology uses a device driver attached to your CD/DVD-ROM drive. This could be what's conflicting with Alcohol, or other drivers. As soon as I installed the demo, I immediately uninstalled it after seeing that it uses this technology. I don't trust copy protection at the driver level, too many things can go wrong.
The silly thing is, it's a demo. How am I supposed to pirate a demo anyway?
The silly thing is, it's a demo. How am I supposed to pirate a demo anyway?
All drivers , save for the sound card drivers (as the new ones cause all sorts of issues) are up to date as of yesterday, as is windows. Ive got a few minidumps in that folder, not sure what ones are new, or old. Should i just wipe that folder and wait for a new error to ensure that minidump is the correct one?[/quote]
The dates are the filenames, and you can also sort by date in Windows details view. Just send the latest few dumps made after you've done all the updates.
I used to overclock back in my P3 and P4 1.6a days, but with the high performance of today's hardware there is no reason to do so. All my hardware for the past 2 years has been running stock speeds. I also agree that this could be a driver issue, but I find it kinda odd that I get the same result on 2 completely different machines. The only hardware in these 2 machines that resemble each other would be the video cards. The 7800 GT in my main machine is using the WHQL 77.77 drivers, while my second machine is using the WHQL 77.30 drivers for my 6800 GT.
As stated above: this is just a demo I am having trouble with and it could be that it doesn't really represent what the final product will run like. I hope that is the case because the game looks like it might be a hoot. I really appreciate dclive taking time to help us with our problems, but I think I will wait to see what happens when the full game hits the street. This could be an instance where a demo scared away potential customers.
Sounds good. Bear in mind the AOE3 demo suggests (to my eyes, at least) a flaw in ATI's handling of the AA/AF functionality - when it's turned on, the box bluescreens; when it's off, AOE3 demo works fine.
That isn't an AOE3 demo problem. It's a problem in ATI's driver.
(Again, that's how it looks to me; if someone from ATI could look at that, it would be a vastly, vastly better source than myself, naturally.)
In other words, I'm saying it's not necessarily the demo's problem. The demo could *reveal* a problem in a bad driver, but that doesn't mean it's the demo's fault necessarily.
That isn't an AOE3 demo problem. It's a problem in ATI's driver.
(Again, that's how it looks to me; if someone from ATI could look at that, it would be a vastly, vastly better source than myself, naturally.)
In other words, I'm saying it's not necessarily the demo's problem. The demo could *reveal* a problem in a bad driver, but that doesn't mean it's the demo's fault necessarily.
dclive, it looks to be an add in sound card issue. Even though I had the onboard sound disabled in the bios, my Audigy 2 ZS seems to be the culprit. I'm not much on removing expensive hardware to make a demo run, but this time it was kind of a challenge to see if I could make it work. I read this thread:
http://forums.ocwizard.com/index.php?s=...bdfddc&showtopic=3712&st=0&#entry36799
and it seems to hold the answer for me and my situation. I pulled the Audigy 2 and removed the drivers. Enabled onboard AC97 8 channel sound in the bios, installed drivers on boot and ran the "Bet on Soldier" demo. It worked just fine........go figure.
When I first installed the demo I suspected sound drivers because of the squealing sound associated with the lockup. Shoulda trusted my first hunch.
http://forums.ocwizard.com/index.php?s=...bdfddc&showtopic=3712&st=0&#entry36799
and it seems to hold the answer for me and my situation. I pulled the Audigy 2 and removed the drivers. Enabled onboard AC97 8 channel sound in the bios, installed drivers on boot and ran the "Bet on Soldier" demo. It worked just fine........go figure.
When I first installed the demo I suspected sound drivers because of the squealing sound associated with the lockup. Shoulda trusted my first hunch.
I'm glad you got it resolved. We've now got two cases of demos illustrating a problem in a vendor's driver architecture. It's not the demo's fault....it's a problem with the driver.
Well, ive made sure windows is updated, and the drivers (except for the audio drivers) are all up to date, and i still get my random bsod in eve-online. Did the MPSRpts thing from your sig, just want to make sure ive got the right email.. this is bluescreens@gmail.com right?
Yes. You need the .cab file and the .dmp files (found in c:\windows\minidumps) created since you did all the Windows & driver updates.
Module[ 16] [C:\WINDOWS\SYSTEM32\VSDATANT.SYS]
Company Name: Zone Labs, LLC
File Description: TrueVector Device Driver
Product Version: (6.0:667.0)
File Version: (6.0:667.0)
File Size (bytes): 368256
File Date: Mon Aug 29 19:08:38 2005
Remove Zone Labs from your system, and let me know if your problem persists.
That's "remove", not disable. Fully uninstall it.
Let us know.
Righto.. removed zone alarm (zone labs), made sure everything on the windows firewall was disabled (wasnt sure if this being the error, that perhaps some remnant of the windows firewall was still active and causing the lockups when conflicting with zone alarm), and picked up a lynksys router to handle the security and whatnot.
Gonna poke around eve the rest of the night, and tomorrow when im off work.. see if i still get those blue screens.
*crosses fingers and prays this fixes it *
Thanks for the help sofar dude.. ill post back with my results later/tomorrow.
Gonna poke around eve the rest of the night, and tomorrow when im off work.. see if i still get those blue screens.
*crosses fingers and prays this fixes it *
Thanks for the help sofar dude.. ill post back with my results later/tomorrow.
Yep, seems that did the trick.. played all last night and tonight without a hitch. Much thanks dude.
Glad it worked for you. Fixing Windows BSOD issues are easy - just look at the dump files and you can typically find the problem!
I'm having the same BSOD trouble with the Bet On Soldier demo as well, when i click on the launch mission tab it crashes. I haven't had this much trouble gettin a game to run since Far Cry (i'm sure most people have been there lol) . Please dclive i need your help
Originally posted by: Sea Frost
I'm having the same BSOD trouble with the Bet On Soldier demo as well, when i click on the launch mission tab it crashes. I haven't had this much trouble gettin a game to run since Far Cry (i'm sure most people have been there lol) . Please dclive i need your help
Make sure you have all Windows updates, make sure you have all the driver updates from the hardware vendors, and if you still have issues, send me the dumps (from c:\windows\minidump) and the MPS Reports .cab file (see my .sig) made AFTER you did all those updates.
Originally posted by: Sea Frost
I'm having the same BSOD trouble with the Bet On Soldier demo as well, when i click on the launch mission tab it crashes. I haven't had this much trouble gettin a game to run since Far Cry (i'm sure most people have been there lol) . Please dclive i need your help
Issue points to vsdatant.sys. Remove (ie uninstall) everything from Zone Labs, and let us know if the issue goes away.
Edit #2: Gee whiz - same file, same demo as the previous poster. Looks like Zone Labs better clean up their act if an application can crash the OS just with Zone Labs / Zone Alarm installed.
Uninstalled Zone Labs an the demo ran fine:Q. I'm runnin the free Firewall from Zone Labs at the minute, I wonder if the full version would react better ? I'm wondering now if my random Battlefield 2 crashes are related to Zone Labs's Fire wall hmmmm... Anyway thanks for your help dclive :thumbsup:
Oh yea forgot to ask - which program to you use to open the dump files with dclive?
Oh yea forgot to ask - which program to you use to open the dump files with dclive?
Microsoft's Debugging Tools for Windows (http://www.microsoft.com/ddk).
Kernel dumps are much more useful than Mini dumps though
Kernel dumps are much more useful than Mini dumps though
Originally posted by: Rilex
Microsoft's Debugging Tools for Windows (http://www.microsoft.com/ddk).
Kernel dumps are much more useful than Mini dumps though
For a quick peek, it's fine. Can't imagine getting someone to send me a kernel dump.
Zip works well. If you're only doing an !analyze -v, minis are fine -- for more than that though, e.g. trouble shooting Volume Shadow Copy *sigh* ... you need more.
Actually, local kernel debugging is more fun.
Actually, local kernel debugging is more fun.
The pool. Had a freaking server (primary file server, of course!) that would have 100% utilization in the System image for ~22 minutes, all the while taking up more and more memory. Then the server would stop responding to SMB requests and eventually stop responding at the console.
LKD revealed that it was a problem with vsc. VSC was taking up large amounts of memory. The reason why is because in System Volume Information folder, the vsc snapshots had become corrupt. After deleting the GUID'ed files, the problem disappeared.
This was after having most of the DL380 components replaced, and being on the phone with the HP reps that deal directly with MS PSS.
The HP rep was pretty flabbergasted when I told him what the source problem and solution was.
LKD revealed that it was a problem with vsc. VSC was taking up large amounts of memory. The reason why is because in System Volume Information folder, the vsc snapshots had become corrupt. After deleting the GUID'ed files, the problem disappeared.
This was after having most of the DL380 components replaced, and being on the phone with the HP reps that deal directly with MS PSS.
The HP rep was pretty flabbergasted when I told him what the source problem and solution was.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
News NVIDIA and Intel to Develop AI Infrastructure and Personal Computing Products- Started by poke01
- Replies: 411
Facebook
Twitter