Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Was anyone else unable to play all weekend due to constant crashes?

2

Comments

  • BergirBergir Member Posts: 299

    You'd be surprised how often its your video drivers. I'm still on the same drivers from July 2010. I know that you always read, update to the latest drivers but what happens is these companies are focusing the drivers on the latest and greatest gen of video cards.



    Over the years so many unknown issues were finally resolved when i made this discovery, DON'T update your video drivers when everything is working well.



    As an example i fired up oblivion one day late last summer, out of the blue it's literally unplayable, been playing the game for years with no issues. I get Dead Island it works no problem then all of sudden black screens. Why.



    I think the straw around that time was Minecraft, been playing forever and never any issues all of a sudden disappears to desktop, no warning just ctd.



    I used Win7 built in Reliability Monitor and immediately noticed an alarming crash rate after i updated away from 258.96 drivers and that all these weird problems started. Before that the graph bar was flat line 100% trouble free. Each new update brought different problems, this game used to black screen now freezes.



    I put 258.96 drivers back in and everything runs trouble free, i went back and played all the games which gave me issues and zero problems even oblivion runs like a dream again.



    After putting Nvidia 258.96 drivers back in my win7 reliability graph bar is running 100% again. Those drivers were tuned for my card i guess, and all the drivers since then are tweaked and tuned for the newest gen which only cause problems for previous gen. When you read upgrade to the latest drivers think twice.

  • victorv1968victorv1968 Member Posts: 24

    Didn't read all the replys but after reinstalling all your drivers did you reinstall DirectX?  I have had issues like that before and after pulling my hair out, reinstalled DirectX and didn't have another issue.

     

    Now my experience with the beta was I had 1 UI freeze and only 3 instances of noticable lag, and really didn't see any bugs.  all in all I had a decent time in game.  On a personal note I DO NOT Like the Voice overs, yes it is emersive but it really slows down the pace of the game. I do read quests and I can read a quest and get moving much much faster then the cut scenes.

  • DerrosDerros Member UncommonPosts: 1,216

    didn't have any crashes at all, fiance didn't either.  Hope they can get whatever issues you guys had resolved, either on their end or your.

  • SasamiSasami Member Posts: 326

    Not single problem here. Your list is pure nightmare, possibly memory related problems. I just hope you haven't done any "speed improving" crap that Internet is full of, and I'm not talking spam crap, but so called expert sites that advice you to screw services and other important parts that they just don't understand. Anyway, when Windows BSOD problem is usually in driver side or broken HW. Having latest non-beta drivers usually helps.

  • Ghost021Ghost021 Member Posts: 84
    You got there a Lan card error and a couple system crashes due to some program accessing something he shouldn't, or the way it was expected.

    image
  • LeucentLeucent Member Posts: 2,371

    No crashes at all. Had the odd lag spike but other then that nothing.

  • ComanComan Member UncommonPosts: 2,178

    Originally posted by rt33



    Over the years so many unknown issues were finally resolved when i made this discovery, DON'T update your video drivers when everything is working well.

    Pretty often I find myself reverting back to older drives to make the newest game work better. Great example was RAGE.

  • ElikalElikal Member UncommonPosts: 7,912

    Yes, I had some crashed, every 2 hours or so.

    People don't ask questions to get answers - they ask questions to show how smart they are. - Dogbert

  • mazutmazut Member UncommonPosts: 988

    Crashed every 2-3 hours and last one finished (MONSTER KILL) my XP (blue screen). Now I have fresh copy, but I might try win7.

  • BergirBergir Member Posts: 299

    Originally posted by victorv1968

    Didn't read all the replys but after reinstalling all your drivers did you reinstall DirectX?

    No, doing that didn't even cross my mind, that's probably not a bad idea though.

  • BergirBergir Member Posts: 299

    Originally posted by Coman

    Originally posted by rt33



    Over the years so many unknown issues were finally resolved when i made this discovery, DON'T update your video drivers when everything is working well.

    Pretty often I find myself reverting back to older drives to make the newest game work better. Great example was RAGE.

    Another great example, thanks.

  • hyllstarterhyllstarter Member UncommonPosts: 203

    I played all 3 days only crashed once. I had a few lag spikes. First day I did get stuck in place twice /stuck all it did was kill me and when I rezed i was still stuck so I had to log out and in. ALso on the first day I couldnt logout I had to shift alt del to get out . I felt it was much more buggy then my first beta weekend.

    image

  • ReizlaReizla Member RarePosts: 4,092

    Had no crashing problems whatsoever. I did find two area's where I got stuck a lot. One was in a private instance when I had o kill Vexx. The other was in the 'open'.

  • RobsolfRobsolf Member RarePosts: 4,607

    BSOD... yikes!

    I don't have any issues like that, fortunately.  One odd thing that's an issue is that you need at least 2 gigs of free space on your C: drive, even if you install it elsewhere.  Not having it usually keeps you from launching, but perhaps if you go under 2 gigs while playing...?

    My main issues were server queues, and an occasional 20-ish second lag spike which seemed to occur in the least opportune moments.

  • Lord.BachusLord.Bachus Member RarePosts: 9,686

    Originally posted by raykor

    Every single driver is up to date...video, audio, bios, ethernet, chipset, etc.  Hardware and virus (deep)  scans all came up clean.  Zero problems with any other game.  Even ran the 3DMark 11 stress test.

    I understand what you're saying but I don't know what else to try. image

    Dump summary of the 11 BSoD crashes...

    ==================================================

    Dump File         : 112711-13728-01.dmp

    Crash Time        : 11/27/2011 12:13:12 AM

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION

    Bug Check Code    : 0x0000003b

    Parameter 1       : 00000000`c000001d

    Parameter 2       : fffff800`033d4aec

    Parameter 3       : fffff880`05dddf40

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112711-13728-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,304

    ==================================================

    ==================================================

    Dump File         : 112611-19219-01.dmp

    Crash Time        : 11/26/2011 10:58:03 PM

    Bug Check String  : BAD_POOL_HEADER

    Bug Check Code    : 0x00000019

    Parameter 1       : 00000000`00000020

    Parameter 2       : fffffa80`06d5c5b0

    Parameter 3       : fffffa80`06d5c700

    Parameter 4       : 00000000`04150015

    Caused By Driver  : dxgmms1.sys

    Caused By Address : dxgmms1.sys+100ba

    File Description  :

    Product Name      :

    Company           :

    File Version      :

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-19219-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,304

    ==================================================

    ==================================================

    Dump File         : 112611-20950-01.dmp

    Crash Time        : 11/26/2011 10:44:38 PM

    Bug Check String  : BAD_POOL_HEADER

    Bug Check Code    : 0x00000019

    Parameter 1       : 00000000`00000020

    Parameter 2       : fffff900`c1dff960

    Parameter 3       : fffff900`c1dffcb0

    Parameter 4       : 00000000`2535000f

    Caused By Driver  : win32k.sys

    Caused By Address : win32k.sys+c55dd

    File Description  :

    Product Name      :

    Company           :

    File Version      :

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-20950-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,280

    ==================================================

    ==================================================

    Dump File         : 112611-15553-01.dmp

    Crash Time        : 11/26/2011 10:19:27 PM

    Bug Check String  : IRQL_NOT_LESS_OR_EQUAL

    Bug Check Code    : 0x0000000a

    Parameter 1       : 00000000`00010027

    Parameter 2       : 00000000`00000002

    Parameter 3       : 00000000`00000001

    Parameter 4       : fffff800`030e6d3d

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-15553-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,296

    ==================================================

    ==================================================

    Dump File         : 112611-14320-01.dmp

    Crash Time        : 11/26/2011 9:18:35 PM

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION

    Bug Check Code    : 0x0000003b

    Parameter 1       : 00000000`c000001d

    Parameter 2       : fffff800`033daaec

    Parameter 3       : fffff880`0760cf40

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-14320-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,240

    ==================================================

    ==================================================

    Dump File         : 112611-17877-01.dmp

    Crash Time        : 11/26/2011 1:49:21 PM

    Bug Check String  : MEMORY_MANAGEMENT

    Bug Check Code    : 0x0000001a

    Parameter 1       : 00000000`00005003

    Parameter 2       : fffff700`01080000

    Parameter 3       : 00000000`000004a5

    Parameter 4       : 000004a7`00000948

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-17877-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,280

    ==================================================

    ==================================================

    Dump File         : 112611-16317-01.dmp

    Crash Time        : 11/26/2011 12:44:07 PM

    Bug Check String  : PFN_LIST_CORRUPT

    Bug Check Code    : 0x0000004e

    Parameter 1       : 00000000`00000007

    Parameter 2       : 00000000`0018b668

    Parameter 3       : 00000000`00000145

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-16317-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,296

    ==================================================

    ==================================================

    Dump File         : 112611-16785-01.dmp

    Crash Time        : 11/26/2011 12:30:44 PM

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION

    Bug Check Code    : 0x0000003b

    Parameter 1       : 00000000`c000001d

    Parameter 2       : fffff800`0317caec

    Parameter 3       : fffff880`09449f40

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-16785-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,232

    ==================================================

    ==================================================

    Dump File         : 112611-14367-01.dmp

    Crash Time        : 11/26/2011 10:50:09 AM

    Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED

    Bug Check Code    : 0x0000001e

    Parameter 1       : 00000000`00000000

    Parameter 2       : 00000000`00000000

    Parameter 3       : 00000000`00000000

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ndis.sys

    Caused By Address : ndis.sys+bf4f1

    File Description  :

    Product Name      :

    Company           :

    File Version      :

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc10

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-14367-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,264

    ==================================================

    ==================================================

    Dump File         : 112611-16645-01.dmp

    Crash Time        : 11/26/2011 9:56:04 AM

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION

    Bug Check Code    : 0x0000003b

    Parameter 1       : 00000000`c000001d

    Parameter 2       : fffff800`0317eaec

    Parameter 3       : fffff880`0633af40

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-16645-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,296

    ==================================================

    ==================================================

    Dump File         : 112611-14523-01.dmp

    Crash Time        : 11/26/2011 8:34:24 AM

    Bug Check String  : SYSTEM_SERVICE_EXCEPTION

    Bug Check Code    : 0x0000003b

    Parameter 1       : 00000000`c000001d

    Parameter 2       : fffff800`031d0aec

    Parameter 3       : fffff880`05b16f40

    Parameter 4       : 00000000`00000000

    Caused By Driver  : ntoskrnl.exe

    Caused By Address : ntoskrnl.exe+7cc40

    File Description  : NT Kernel & System

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

    Processor         : x64

    Crash Address     : ntoskrnl.exe+7cc40

    Stack Address 1   :

    Stack Address 2   :

    Stack Address 3   :

    Computer Name     :

    Full Path         : C:WindowsMinidump112611-14523-01.dmp

    Processors Count  : 2

    Major Version     : 15

    Minor Version     : 7601

    Dump File Size    : 292,280

    ==================================================



    Obviously those crashes are hardware related. And probably temperature related. I don't think they are graphics card related, so that in general leaves you with CPU or Memmory failures.

     

    Download yourself some good testing tools.  http://www.ultimatebootcd.com/ is a freware CD with all testing tools you will ever need. And choose the tools to do a CPU and a Memmory stresstest.

    Best MMO experiences : EQ(PvE), DAoC(PvP), WoW(total package) LOTRO (worldfeel) GW2 (Artstyle and animations and worlddesign) SWTOR (Story immersion) TSW (story) ESO (character advancement)

  • summitussummitus Member UncommonPosts: 1,414

    Nope .. played most of the weekend and not one crash , had no lag and only spotted a couple of minor bugs while I was playing ... Without doubt it was the smoothest most hassle free Beta Test that I have ever done .. hands down . And I've tested nearly every major Mmo over the years.

     

    Cant wait for Launch if the test was anything to go by. :-)

  • raykorraykor Member UncommonPosts: 326

    Thanks for all the suggestions.  I'm going to try rolling back to an older version of the NVidia drivers.  I honestly think it has to be a driver incompatibility with the current build because I have run numerous hardware tests and found no problems.  I'd had hardware problems in the past (RAM, disk, and video card) and in my experience it causes problems all over the place and not in only one single game.


     


    Thanks again.

  • VideoJockeyVideoJockey Member UncommonPosts: 223

    I had BSOD issues about every 40 minutes. For some reason SWTOR taxes my processor more than any other game or program that I run... I was getting core temps over 100C when playing and I had to take my heatsink and fans apart and clean them to get the temps down. Might be worth a look.

  • stringboistringboi Member UncommonPosts: 394

    No crashes here.....Played all weekend without a single one.  Did get my character stuck a few times though =)

  • ShadanwolfShadanwolf Member UncommonPosts: 2,392

    I thought I had updated video card drivers...and I didn't. Could not get on at all....pulled down latest drivers...and the problem was no more. You should check and DL the latest..just because.

  • waynejr2waynejr2 Member EpicPosts: 7,771

    I have been in game testing for a year.  I have had 1 ctd.

    win7 x64.

     

    There have been people over that time who have had heat issues and shutting down.  I would suspect that would be likely.

    http://www.youhaventlived.com/qblog/2010/QBlog190810A.html  

    Epic Music:   https://www.youtube.com/watch?v=vAigCvelkhQ&list=PLo9FRw1AkDuQLEz7Gvvaz3ideB2NpFtT1

    https://archive.org/details/softwarelibrary_msdos?&sort=-downloads&page=1

    Kyleran:  "Now there's the real trick, learning to accept and enjoy a game for what it offers rather than pass on what might be a great playing experience because it lacks a few features you prefer."

    John Henry Newman: "A man would do nothing if he waited until he could do it so well that no one could find fault."

    FreddyNoNose:  "A good game needs no defense; a bad game has no defense." "Easily digested content is just as easily forgotten."

    LacedOpium: "So the question that begs to be asked is, if you are not interested in the game mechanics that define the MMORPG genre, then why are you playing an MMORPG?"




  • raykorraykor Member UncommonPosts: 326

    Originally posted by VideoJockey

    I had BSOD issues about every 40 minutes.


     


    I wish I could have run the game long enough to heat up my CPU. image


     


    But seriously, my system is home built and resides in a spacious Cooler Master Cosmos S with four fans and a chunky 110mm Zalman CPU Cooler for good measure.


     


     

  • NetspookNetspook Member UncommonPosts: 1,583

    Had 3 maybe 4 CTDs. Not bad, consideirng the amount of hours played, and the fact that they were stresstesting the servers.

  • Turns out the really annoying bug I was experiencing was a mouse key getting stuck, and not really the game's fault after all ^^

  • NazgolNazgol Member Posts: 864

    I experienced a lot of CTD throughout the testing period. It lessened over the weeekend though, it was kind of odd. I experienced little lag, some graphical glitches, and had roughly at 40 fps at highest settings, but my computer is not the top of the line so no complaints about that. The crashes were my main concern though, especially on Friday and Saturday. Sunday I had maybe on crash in the 3-4 hours I spent playing. I also noticed the game seems to be running 2 processes, Is one of these the debugger?

    In Bioware we trust!

Sign In or Register to comment.