HELP BF2 Blue Screen Crash

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GreatWhiteShark

    #16
    Originally posted by SerbSniper1
    OK GOT THE NUMBERS AFTER THE CRASH!

    Tech INfo:
    STOP 0x0000008E [0xC0000005, 0xB336701A, 0xA82565E8, 0x00000000]
    1R446 Address B336701A Base at B3365000, Date stamp, 42e15f86
    begining dump physical memory

    what do you think? one thing is for sure I'm getting tired of this ****.
    my virtual memory is 2046 max 4092

    One thing I did was turn to low the shading and textures and now I can play longer, but it aint fixed.

    I think the problem is in this new shading and textures nvidia is using trying to be the top dog and the games makers are ahead of there cards?
    IMHO your starting to flame more rather than fix. Stick with the facts plz.

    Your getting ahead of yourself and not keeping us posted to what "exactly" you have and have not done.
    What "N" drivers are you using now ?

    It's still pointing to your RAM and poss the N divers, what have you done to look into the way your RAM is working, if anything at all.

    Comment

    • Sir. S.A.S

      #17
      i think the problem is either graphics card related or Ram reltaed id try rollling back your drivers. resitting your ram trying 1 stick at a time.

      Comment

      • SerbSniper1

        #18
        WAIT I wasn't being a flame. I just said YES! Sorry for confusion. This game is getting on my nerves now though.

        But to clarify, I have lowered my setting and NOW I can play for one round before the map changes. After the server shows stats etc, then goes to start a new game NOW it crashes and restarts.

        Comment

        • GreatWhiteShark

          #19
          The game dose not like OC vid cards reset to default and try.

          Then lower your "game" and "desktop resolution" "not to the same values" and try.

          It is advised by EA that after altering hardware settings that you need to reinstall the game for the game, to recognise the alterations and adjust the BF2 game programing, in accordance with anything you have done.

          Comment

          • 22CW Cainius

            #20
            hardware issue seems more likely...

            try defragging before and after installation

            Comment

            • SerbSniper1

              #21
              OK, have now reinstalled this damn game for the third or fourth time. :cry: Still does it, although I can usually play one map cycle before it crashes to the blue screen. I also tried an order nvidia 6800 driver. I also tried setting my desktop to 1024x768 prior to loading the game the first time. In the options I have turned everything down. Have defragged and all that stuff. Tried the delete the cache stuff and had to reinstall after deleting those. I'm stumped.

              Once again this only occurs during multiplayer games, wtf?

              Comment

              • GreatWhiteShark

                #22
                If the following works plz get back to me

                Use the
                http://drivercleaner.net and remove traces of nforce drivers (If you wish)

                Solution:
                Simply download the new NVIDIA nForce4 drivers for you motherboard chipset! For the AMD its driver version 6.53 (not the beta version). Surprisingly no freezes!
                Just follow this link to get the drivers:
                http://www.nvidia.com/content/drivers/drivers.asp

                Thread mentions 6.53, but they aren't the latest drivers anymore 6.66 was released on July 15.

                Quote ...Nvidias did the trick. I played all night with everything cranked to the max. If you are having stuttering/rubberbanding issues just turn off your dynamic lighting and shadows, but if you are getting the hard locks where you have to hit the reset button do yourself a big favor and update your chipset drivers from Nvidia's site and not your boards website. Thanks for the tip EuqirneSelbor!! Works great!!

                Thanks to .. EuqirneSelbor, TRS*MajorPaynE, Gunny Highway.
                Source http://forums.totalbf2.com/showthread.php?t=9418&page=1&pp=20&highlight=Athlo n+freeze

                Failing that PM nicely, to Gunny Highway and ask him to look into this post he has way more knowledge than me.

                Comment

                • SerbSniper1

                  #23
                  Okay did a little more tinkiering, spoke to Kingston, and EA again. Buttt... No help from either. Kingston says its not the ram, I figured that out myself. EA, went through the whole turn everything off then delete the BF2 folder in my documents and reset to default, ya LADADA, didn't work either. I was waiting for the ALL SO FAMILIAR TECH (cause I don't know come back), reinstall reinstall, but it didn't come. Anyway, downloaded the NEW (to me) nvidia BETA driver, was able to play for a good 2-3 hours before a crash to the blue screen. I also turned my video options to:

                  800x600@60mhz
                  LOW
                  CUSTOM
                  LOW
                  LOW
                  LOW
                  MED
                  LOW
                  OFF
                  OFF
                  OFF
                  LOW
                  75%
                  IMHO I think it's the NVIDIA Drivers or EA needs another patch. OR BOTH! PROBABLY BOTH.

                  Comment

                  • GreatWhiteShark

                    #24
                    Originally posted by SerbSniper1
                    Okay did a little more tinkiering, spoke to Kingston, and EA again. Buttt... No help from either. Kingston says its not the ram, I figured that out myself. EA, went through the whole turn everything off then delete the BF2 folder in my documents and reset to default, ya LADADA, didn't work either. I was waiting for the ALL SO FAMILIAR TECH (cause I don't know come back), reinstall reinstall, but it didn't come. Anyway, downloaded the NEW (to me) nvidia BETA driver, was able to play for a good 2-3 hours before a crash to the blue screen. I also turned my video options to:

                    800x600@60mhz
                    LOW
                    CUSTOM
                    LOW
                    LOW
                    LOW
                    MED
                    LOW
                    OFF
                    OFF
                    OFF
                    LOW
                    75%
                    IMHO I think it's the NVIDIA Drivers or EA needs another patch. OR BOTH! PROBABLY BOTH.
                    Ouch man, those are not funny settings, like I said PM nicely, to Gunny Highway in this forum and ask him to look into this post, he has way more knowledge than me. He's one of the good guys that tells it how it is.

                    Comment

                    • SerbSniper1

                      #25
                      Oh PS........The EA tech said the memory dump was from my fast system, which is too powerful for most servers when it sends back and forth the data. ?????????WTF????

                      Comment

                      • GreatWhiteShark

                        #26
                        Originally posted by SerbSniper1
                        Oh PS........The EA tech said the memory dump was from my fast system, which is too powerful for most servers when it sends back and forth the data. ?????????WTF????

                        My, oh My, oh My, I LMAO at that answer from EA it's amazing what answers they pull out of that magic hat at a tech support.

                        I have heard lots of times that mem dumps were caused by "slow" rigs that I can get my head around. But a rig that is to fast at sending / receiving info, I just can't get my head around that m8.

                        IMHO, your 3.4 rig is fast, so what, your rig dose not throw the collated information down the cable, dose it, that is the transferring of information part via ISP router etc.
                        The performing of the program is handled by your rig, it processes the transferred information that it has received (downlink) you work the information received (via the program) then the results of you working the program are transferred back to the server (uploaded) so as you say WTF?

                        I did not/have not seen anywhere that you can have a rig that is to fast for the game, because of this you could ask EA tech for a more in-depth explanation than the one given.

                        I'm still smiling as I tap this out, I bet you are not.

                        Comment

                        • SerbSniper1

                          #27
                          Still Crying :cry: , yelling , and banging my computer, hey wait a minute .... Its not my computer.........................now starts throwing BF2 cd discs around, stomping on EA/BF2 installation booklet .

                          Comment

                          • imported_ColonelPanic

                            #28
                            Typically, that would indicate memory problems. I had the same problems when I was using differing RAM in dual mode. Changed it so that all the RAM was exactly the same (IE manufacturer) and all the problems stopped. Note that I didn't get problems in some other games but consistently blue screen in BF2 until the RAM change.

                            Comment

                            • SerbSniper1

                              #29
                              Thats my ram is the same Kingston Dual Channel Hyper x 3500 NOT OC though,
                              2x512 2x256

                              Comment

                              • imported_Davis

                                #30
                                Originally posted by SerbSniper1
                                Thats my ram is the same Kingston Dual Channel Hyper x 3500 NOT OC though,
                                2x512 2x256

                                If you could swap memory from a different computer, relative or friend. The error you get is not caused by Battlefield 2, it is caused by Windows not allocating the threads.

                                Comment

                                Working...