PDA

View Full Version : Patch Causing System Crash?



Aldroth
08-15-2007, 03:42 PM
I haven't had any problems, but after I installed this patch I've been getting the blue error screen with "Bad_Pool_Header" and "Bad_Pool_Caller". I used the verifier tool to track down the culprit, which was a TDI.sys, but even after a soft reinstall it was still messed up. I had this happen all day yesterday so I decided to completely reformat and reinstall windows. I finished this morning and played GRAW2, which lasted all of 5 minutes before giving me the blue error screen. I decided then to try some other games, to see if they had problems as well. I played a good hour of GRAW1 and about 30 minutes of RS:Vegas with no problems at all. I've checked my drivers and updated graphics, sound, and MB drivers. Finally I uninstalled and reinstalled GRAW2 and downloaded the patch from a different host. It lasted about 20 minutes which is a lot longer than it has, but finally it crashed to the screen. I'm kinda running out of options. One last thing I'm going to try is reinstalling GRAW2 and leaving it on 1.02 and find a server with that patch to play on for a while and see if I encounter the same errors. If anyone else is having the same problems or has any ideas please let me know. The only other thing I can think of is the new windows update had something to do with it, but then why would none of the other games be affected?

My system is as follows:
Windows XP 32bit
ASUS P5N32-E SLI Motherboard
Intel Core 2 Quad CPU @ 2.40GHz
3.00 GB of RAM
BFG Tech Nvidia Geforce 8800 GTX
Turtle Beach Motego DDL Soundcard
Seagate Barracuda 7200.10 320GB HD

Aldroth
08-15-2007, 03:42 PM
I haven't had any problems, but after I installed this patch I've been getting the blue error screen with "Bad_Pool_Header" and "Bad_Pool_Caller". I used the verifier tool to track down the culprit, which was a TDI.sys, but even after a soft reinstall it was still messed up. I had this happen all day yesterday so I decided to completely reformat and reinstall windows. I finished this morning and played GRAW2, which lasted all of 5 minutes before giving me the blue error screen. I decided then to try some other games, to see if they had problems as well. I played a good hour of GRAW1 and about 30 minutes of RS:Vegas with no problems at all. I've checked my drivers and updated graphics, sound, and MB drivers. Finally I uninstalled and reinstalled GRAW2 and downloaded the patch from a different host. It lasted about 20 minutes which is a lot longer than it has, but finally it crashed to the screen. I'm kinda running out of options. One last thing I'm going to try is reinstalling GRAW2 and leaving it on 1.02 and find a server with that patch to play on for a while and see if I encounter the same errors. If anyone else is having the same problems or has any ideas please let me know. The only other thing I can think of is the new windows update had something to do with it, but then why would none of the other games be affected?

My system is as follows:
Windows XP 32bit
ASUS P5N32-E SLI Motherboard
Intel Core 2 Quad CPU @ 2.40GHz
3.00 GB of RAM
BFG Tech Nvidia Geforce 8800 GTX
Turtle Beach Motego DDL Soundcard
Seagate Barracuda 7200.10 320GB HD

ColinCJ
08-16-2007, 10:44 AM
Can you give some details on the Ram and the slots.

Also the windows error log.
Also make sure you are not using any Beta software for your MB.

Aldroth
08-16-2007, 11:04 AM
I tried playing GRAW2 on the 1.02 patch and had no problems, except the fact I was playing single player instead of multiplayer, so its not a fair comparison.

Ram is Corsair XMS2 240-Pin DDR2 SDRAM 800 PC2 6400. Only using 3GB because 32bit won't support 4 so I left the last stick out because it was unstable. Ram is in the first 3 slots. I tested all of them by themselves to make sure none of them were corrupted, and did a memtest with the windows program. It didn't show any problems with the RAM.

Error Logs:

1.
Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 00000000, parameter4 892bdc60.

2.
Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 00000000, parameter4 8932b6b0.

ColinCJ
08-16-2007, 11:39 AM
Error code 000000c2
Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.

I would start on the Ram.
Use 2 gig only in dual channel as long as they are a matched pair.

Before starting download latest drivers for sound and video cards. NOT BETAS.

Uninstall all sound and video drivers.

Use this programme to cleane the drivers out completly.
http://www.guru3d.com/index.php?page=driversweeper

Then use a reg programme to clean registry before though do a back up. pc tools is a good one.

Shut down restart, ignore found new hardware stuff, disable any programmes running, and then reinstal drivers.

In graw 2 once you have restarted redo the hardware check in game. Delete your profile in the Ubi folder, redo your sign and see how it runs.

ColinCJ
08-16-2007, 11:41 AM
PS If this fails consult a GP. http://forums.ubi.com/images/smilies/winky.gif

Want2Snipe
08-16-2007, 03:07 PM
Make sure the bios is using the correct voltage for your Ram... check the mfrg to see what the recommended voltage is and manually change it if bios AUTO has it to a different setting. I had plenty of issues because of that.

Aldroth
08-18-2007, 03:00 PM
Still no luck. I've done two reformats, made sure all of my drivers and BIOS are not betas, and I still get the same problem. http://forums.ubi.com/groupee_common/emoticons/icon_frown.gif

Aldroth
09-08-2007, 05:21 PM
Anyone? http://forums.ubi.com/groupee_common/emoticons/icon_frown.gif

GlenGrainger
09-08-2007, 06:17 PM
Hi,

You may find that even with 3GB of ram that Windows XP is having problems, there was something at Microsoft about a 'switch' that could be added to the boot.ini file to help Windows XP see 3GB ram. But when I tried it myself my system would not even start, kept crashing with a blue screen of death and restarted itself automatically.

This would put me at the boot options as Windows had a problem starting, tried Safe Mode, blue screen of death, system reboot itself. Anyway at the end of it, I had to use recovery console, delete the boot.ini file which caused Windows to give me an error message at startup about invalid boot.ini file and boot straight from C:\Windows\ where I was able to restore a backup of the boot.ini file.

Might be an idea to drop back to 2GB ram and see if that fixes the problem, hope this helps a little... http://forums.ubi.com/groupee_common/emoticons/icon_smile.gif

unpredictabl3
09-08-2007, 10:49 PM
Ok. Patch graw2 again. Before you launch it goto:CLick start, right click 'my computer' select 'properties'/advanced(tab)/select 'settings'and in start-up and recoveries and UNCHECK (automatically restart).CLick ok.start the game.

Enjoy your next BLUE SCREEN OF DEATH cause this time it will tell you exactly what(fault module) driver,dll is giving you the headache. Write down your "blue" error and post back http://forums.ubi.com/images/smilies/16x16_smiley-happy.gif

Aldroth
09-09-2007, 06:01 PM
Ok, I already applied the 1.4 patch. Still have the same problem. I took out 1 gig of ram leaving me 2gigs as suggested, which made the game crash in even less time than it usually takes. Here is the complete BSOD text, along with the technical information it posts when you restart the computer and it pops the send-microsoft-info window:

A problem has been detected and windows has been shut down to prevent damage to your computer.

BAD_POOL_HEADER

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears 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 any 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: 0x00000019 (0x00000020, 0x88B30C10, 0x88B30E78, 0x0A4D0002)

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.


Here is the technical information. This is from two different times:

BCCode : 19 BCP1 : 00000020 BCP2 : 886A57F0 BCP3 : 886A5A58

BCP4 : 0A4D0036 OSVer : 5_1_2600 SP : 2_0 Product : 256_1



BCCode : 19 BCP1 : 00000020 BCP2 : 88B30C10 BCP3 : 88B30E78

BCP4 : 0A4D0002 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Any idea what it means or what 256_1 is?

ThumperDFN
09-09-2007, 07:18 PM
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by Aldroth:
Anyone? http://forums.ubi.com/groupee_common/emoticons/icon_frown.gif </div></BLOCKQUOTE>
I have Corsair DDR2 Twin2X 6400C4 800MHz RAM. I don't have any game problems, but Windows XP Pro doesn't save my desktop settings, i.e. sound and Windows Classic desktop settings permanently. They revert to default settings after a while. This is the first and last time I use Corsair memory. I've always used Crucial, but a friend recommended Corsair and I got it. This is the price I paid for not sticking to what I know best. My Mmobo is abnd Asus CROSSHAIR. That also could be the issue.

Aldroth
09-09-2007, 07:35 PM
The RAM isnt the issue for me. The reason I'm using only 2 out of the 4 gigs i have is a windows xp issue, and the fact that the mobo I have is extremely finicky about ram. I just uninstalled my sound card drivers and I think this may be the culprit. Gonna play a while and see if it crashes. If its this I don't know what I'm gonna do other than report it and return the card and find another one that works with my surround sound headphones http://forums.ubi.com/groupee_common/emoticons/icon_frown.gif

unpredictabl3
09-09-2007, 08:01 PM
Hmmm. Sorry for the delay but the only thing that came with the 1.4 patch is(since you can play it with different versions 1.2) is that Openal came with the patch.

Your ram is fine. You've tested each module and ran mem-test. The STOP: 0x00000019 is a range of things but if we look closely, all other games work... and graw2(but not with the 1.4 patch installed) SOoooooooo goto control panel and uninstall OpenAL and download and run ccleaner (http://www.filehippo.com/download_ccleaner/) and do a "issues scan" and click"fix selected issues" and reboot your pc.

That is the only thing i can come up with before you return your soundcard. And i hope you have disabled the on board sound with your soundcard inplace? This is a hunch but a good one.
Edit:i forgot but take the openal32.dll out of the graw2 folder also.cheers.

Aldroth
09-09-2007, 08:16 PM
I uninstalled my driver for the soundcard, leaving my no sound, however I was able to play GRAW2 for a good hour and a half without any problems (minus sound). I'll try an older driver, but if not I think I'm going to have to return (if they will still take it back).

unpredictabl3
09-09-2007, 08:36 PM
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by Aldroth:
I uninstalled my driver for the soundcard, leaving my no sound, however I was able to play GRAW2 for a good hour and a half without any problems (minus sound). I'll try an older driver, but if not I think I'm going to have to return (if they will still take it back). </div></BLOCKQUOTE>

Don't return your soundcard cause of one game. Just goto add and remove programs in control panel and remove OpenAL. It's not needed.

Aldroth
09-09-2007, 08:53 PM
I installed the older driver and it seems to be working fine. Who do I report this issue to, GRIN/Ubi, or the sound card maker? Not that I think they'll do anything about it, but it would be nice.

unpredictabl3
09-09-2007, 09:33 PM
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by Aldroth:
I installed the older driver and it seems to be working fine. Who do I report this issue to, GRIN/Ubi, or the sound card maker? Not that I think they'll do anything about it, but it would be nice. </div></BLOCKQUOTE>

OpenAL has been around for quite awhile. It would be your sound card manufacturer that would have to make a more compatible driver :P

And by the looks of it your not trying my suggestion, it's like talking to 'GHOSTS'

Aldroth
09-10-2007, 07:36 AM
No, I'm not meaning to ignore your suggestion. I looked for OpenAL, but I didn't see it in programs, so I figure its not an OpenAL problem, but just a soundcard-out-of-date-driver problem.

unpredictabl3
09-11-2007, 12:31 AM
http://i202.photobucket.com/albums/aa48/Geonad/openal2.png

Hmm. Weird. I'm i the only one that got this through the 1.4 patch(openal)? I went to my wifes pc and it wasn't there (programs folder). She also has the game installed on her pc, but i've notice if you goto graw's folder (not graw2) that the openal32.dll has been modified the same day the 1.4 patch for graw2 was released.7/17/2007.

My apologies there Aldroth, but seems like this mysteries openAL just came with my patch or with visual studios. COuld be part of the map editor that came with the patch also. Has anyone tried this editor? I've launched it but its different from graw1. Any successful map making out there?

pchoi04
09-12-2007, 12:11 AM
I'm running Windows XP 64bit and on a fresh install it works fine but after I've updated to the new Patch I can't even get passed the loading screen and sometimes it blue screens. Driving me crazy. I even uninstalled and reinstalled it and installed the 1.3 patch and still having the same problem.

Any Ideas?