[MicTig]

I just got a new computer (and put it together myself, first time) and I've been getting blue screens of death randomly while in Windows (Windows Vista 64 bit Ultimate) and also red screens of death while playing Crysis on DirectX 10. It only crashes when I use DX 9. I really need help! Here's what I have.

Q9550 processor

Palit Sonic Dual edition 4870

Asus P5Q3 Wifi Draft N Mobo

PC Power and Cooling 750W CrossfireX edition

Patriot DDR3 4 GB 1333 Mhz RAM

Antec 900 Gaming Case

Samsung T220 Monitor



Please ask for any adition info if you can. Thanks.

[rgreen4]

The next time you get a BSOD, write down the entire message and post here. The Stop error codes will give us some clues.

Thanks for posting all the system details-

In the meantime - a few more questions.
1. Does it always happen at the same point in time?
2. Does it always happen at the same point in the game?
3, Does it happen randomly?

[coastie65]

I believe the problem is that you trying to play that thing with a 64 bit OS. There are a very very limited number of games that are written for the 64 BIT OS. Crysis is not one of them. There are many more games coming out that support DX10. coastie65

[MicTig]

I tried playing crysis again (DX9) and it didn't crash. I played for ~30 minutes. I did though get another blue screen though, but my computer restarted so fast that I couldn't write it down. I'm trying to have my camera ready for next time. Oh and btw I'm now using the driver that Windows Update automatically got for me. Another thing to note is that after I uninstalled my original driver, I was using the "VGAsafe" mode thing (I had no driver) and that is when I got my most recent BSOD. Another thing is that while I'm playing Crysis my screen randomly goes black around every 10 mins and it quickly recovers back to normal. I really don't know what is going on and this whole ordeal is making me pretty sad beacause I've been saving up $ for a long time to get this computer. Anyways, I will try to get the code next time.

Oh ya.

1. It doesn't happen at the same point in time. It seemingly happens randomly, but I have to be doing something on the computer for it to happen. (eg, surfing the web)

2. I does not happen at the same time in the game. I think that it MIGHT happen at graphically intense parts of the game. But then I should just get lower fps.

3. Yes, I think that both the RSODs and BSODs happen randomly, as far as I can tell. Ask me for any other info you need.

[MicTig]

I thought that 64 bit Vista was getting pretty good at playing 32 bit apps. But then again I can't use the 64 bit version of Crysis - it doesn't work - I have to use the 32 bit version.

Oh I think I forgot to tell you that I'm using a Seagate Barracuda 7200.11 640 Gb harddrive

[coastie65]

Unfortunately as you have found out, the 32 bit version of the game doesn't work so well with the 64 bit OS. I don't know what the deal is with the 64 bit version of the game and why it doesn't work. Are you sure it is a 64 bit version ? I have "The Witcher" and it is Vista Capable for DX10 as well as XP and DX9 but it is still 32 bit. There are very few games, and I do mean a very few games that are 64 bit. You are not the first person to visit the forum with very same issue and that is wondering why games are crashing and your computer is BSODing while playing games with a 64 bit OS. If your HDD is big enough you could always set it up to dual boot by adding a second 32 bit OS. At start up, you could then choose with OS to boot from. OK, I just noticed your second post. You have a 640 Gb HDD. That would give you 320 Gb on each OS. I only have 200 Gb and it is plenty so far and I have a good number of games in here including The Witcher and Oblivion and still have bout 75% free. coastie

[rgreen4]

While the driver situation has been fairly well solved for the 64bit version of Vista, many games have not yet become fully compatible with Vista, especially the 64bit version.

I have a dual/tri boot machine in which I can add bootable OS's at any time. I simply install the OS on a solo drive. By this I mean I disconnect all drives except for the one on which I am installing the OS. Then when the OS is fully installed, I can connect the other drives, and on boot hit the boot menu key and select the drive I want to boot from. Now at this point the BIOS only knows what drives are connected with a boot record, not the OS, so the BIOS only lists the drives by Make and model number.

If you purchased the retail version of Vista, you can get the 32bit version DVD for little cost. If, however, like many of us you save money by purchasing the OEM version, then you have to purchase a new 32bit install package.

If you choose to install the 32bit version of XP instead of Visa as your second boot, you will have to check the BIOS setting for your drive controller. Since you have the Intel CPU, you may have an Intel 82801H AHCI edition of the drive controller chip. It should be in the advanced section of the BIOS and can have two or three settings. If it is set for RAID or AHCI then XP will not install. My MB came from the manufacturer set to IDE for IDE emulation. If yours is set that way then XP will install without problems.

If you change it Vista will not boot without re-installation. (Vista only installs the drivers called for, so if the BIOS is set for RAID, the IDE emulation driver is not installed. XP has only the IDE driver, not the RAID driver). Here is a [document|d-1670] explaining it in greater detail. While most of it was devoted to problems on laptops on which you cannot change the setting, the basics are the same.

[MicTig]

Thanks guys for your help. Ok, the funny thing is that I DID install xp 32 bit on a different portion of my disk. The RSODs stopped on Crysis but the BSODs did not stop. So now I think it might be a problem with my Hardware/Drivers. I'm going to try and find some later.

I've gotten the BSOD 2 times since I last posted but my camera was way too slow at starting up so Windows told me some info on the crash when it started.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 4105
Additional information about the problem:
BCCode: a
BCP1: FFFFFAB0011F3438
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80001C7ED39
OS Version: 606001
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:WindowsMinidumpMini091608-04.dmp
C:UsersMichaelAppDataLocalTempWER-31262-0.sysdata.xml
C:UsersMichaelAppDataLocalTempWERC090.tmp.version.txt
Read our privacy statement:
http://go.microsoft....63&clcid=0x0409



This is from the "WERC090.tmp.version.txt" file. I can get you the other ones I think.

Windows NT Version 6.0 Build: 6001 Service Pack 1
Product (0x1): Windows Vista ™ Ultimate
Edition: Ultimate
BuildString: 6001.18063.amd64fre.vistasp1_gdr.080425-1930
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033



I will now go play Crysis now and test further. I really don't like how sometimes it goes black and lags though - oh well, at least I haven't had RSODs lately. Apparently red screens of death are a worse version of blue screens of death. Kinda makes sense.

[MicTig]

OK I played Crysis for about 20 mins until a BSOD popped up. I'm not getting RSODs anymore just BSODs. I just finished updating my chipset drivers and my SATA drivers before playing (yes, I did restart). Do you guys have any more ideas of what I could do? RMA my GC?

[rgreen4]

The next time you boot the machine, go into the BIOS Setup and look for a BIOS setting about restart on error and change it. Depending on the brand of BIOS, it may say "enabled" so change it to "disabled". This will keep the machine from automatically restarting on error so you can write down the error, or get a photo.

[MicTig]

OK I will. Then I will use the computer heavily so it will crash. :D

[MicTig]

A problem has been detected and Windows has been shut down to prevent damage to your computer
PAGEFAULTINNONPAGEDAREA
If this is the first time you've seen this stop error screen, restart your computer. If this screen apears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for and Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical information:
* STOP: 0x00000050 (0xFFFFFA802395B240, 0x0000000000000000, 0xFFFFF80001D8F363, 0x0000000000000002)

Collecting data for crash dump ...
Initializing disk for crash dump ...
Beginning dump of physical memory.
Dumping physical memory to disk: 100
Physical memory dump complete.
Contact your sysyem admin or technical support group for further assistance.

[rgreen4]

Okay - Stop 0x00000050 indicates a memory error. Since you most likely have 2 memory modules (2 x 2GB to get to 4GB), remove one (we will call it MM1). Now while the machine will not be as balanced (dual channel likes 2 equal modules) it will run with one. Then do what ever it was that triggers the BSOD.
If after a reasonable time you do not get a BSOD, or immediately after you get a BSOD, remove the remaining module (MM2) and place the first module (MM1) you removed in the socket for the second (In other words if MM1 was in socket 1, and MM2 was in socket 3, place MM1 in socket 3) in this manner, we will check the modules and sockets. Again undertake the processes that generate a BSOD.
If after a reasonable time you do not get a BSOD, or immediately after getting a BSOD, place the second module in the first memory socket. (MM2 in Socket 1), and remove MM1. And again, try to generate the BSOD.
If you always get a BSOD with MM1 in the system regardless of the socket, then MM1 is bad. Likewise if you always get a BSOD with MM2 in the system then MM2 is bad. If you always get a BSOD with either MM in socket 1 or socket 3 then you have a MB problem.
If you cannot generate the BSOD after swapping the modules, you had a connection problem between a module and the socket and the act of removal and re-insertion has solved it.

Vista does include a Memory Diagnostic Tool that can be accessed by two methods. The first and easiest is to click the START ORB and then in the search box key mem. At this point the search tool should pop up the following:



A pop up dialog box will open asking if you want to run the memtest on the next restart. If you answer yes, the next time you start the PC it will run a memory diagnostic. The second way is to insert and boot from the Vista installation DVD. Make sure your PC is set to boot from the DVD and when the Vista Installation screen appears, click on "Repair your Computer". It will ask you which copy, (you probably only have the one) so click on your copy, and you should be given some options to test and repair different areas, one of which is the Windows Diagnostic Tool. Note - this is from a reputable book and I have never used this method. Method 1, I have used as it's easier.

Even if you run the memory diagnostic, I would still do the manual test, and the diagnostic tool cannot differentiate a bad socket from a bad module and cannot fix a bad connection between the socket and module. (All is takes is a grain of sand and it won't make contact on a pin.

[MicTig]

Ok I will definately do that. I was at school today and I have to do a project at a friends house today also so I will get it done either tonight but probably tommorow. I also got a RSOD while playing crysis again and it said

STOP: 0x000000C5

Is this also to do with the memory just to make sure? Thanks for all the help ?:|

[coastie65]

OK. I'm not totally 100% sure on this, but it could well be a Video driver conflict. You can not run the same drivers with XP & Vista as each has their own drivers. My advice to those who are planning on gaming on their computer is to stay away from 64 bit unless you want to set up for a dual boot. It this is the case and you have a dual boot system, then you need two sets of drivers, XP drivers and Vista Drivers if the Computer is configured that way. If you have a Vista 64 bit & Vista 32 bit dual boot configuration, I'm not sure how that would work as I don't know if they use seperate drivers or not. coastie

[rgreen4]

Google references do indicate a corrupted driver issue.

[MicTig]

So far I've found out the following:

MM1 in Socket 3 = BSOD

MM1 in Socket 1 = BSOD

Once I get home from school I will check the other memory (MM2)

Also, is it normal for Crysis to "lag" a whole bunch when I only have 2 GBs of RAM because it does and it didn't before. Thanks for all your help guys. I will post back later.

[coastie65]

OK, you didn't say which Video Card you were using. Your system specs are much stouter than mine to be sure ( See my Signature) and I have played the Crysis demo with no problem at all. coastie

[rgreen4]

Yes, any system will run slower to a point with less memory. The higher the memory demand, the slower. Be thankful we don't have to try this with 512K modules, it might not work, but most of us run at a minimum twice the actual minimum memory. This machine I'm on has 4GB, but started as 2, so now it has 4 1GB modules, when the second two matching modules were on sale, I couldn't pass them up, even though I knew my 32bit Vista would only utilize a max of 3.5GB +/-.

[MicTig]

MM2 in SOCKET 1 = RSOD



I think it is a GC issue because Crysis lags soo much on even a low resolution and medium settings. I do think you guys are correct and that it's a driver issue, but I just can't seem to find one that works. Also, I got the BSOD when I didn't even have a GC driver installed! This might be multiple problems... and my GC is a Palit Sonic Dual Edition HD4870. Yep... and it lags. I'm going to go and try some different drivers - that is if I can find any. I really appreciate all of your responses and help guys. :8}