EQII unplayable due to BSOD

[Zedzorander]

Hello all,<div>I am in the midst of a bit of an upgrade to my system and in need of some assistance.</div><div></div><div>To start off with, my current problem.  Every single time I log into the game my computer will blue screen.  When this happens appears to depend on which character I log into so perhaps being affected by which zone I am logging into I would guess.  It is the worst on my fury who is leveling in timorous deep.  The game will successfully load and I am usually able to just stand there unmoving without issues, however as soon as I try to move my character and sometimes make it to attacking a mob I will bsod every single time.  I have made it as long as a minute or so on my necro who is standing in thundering steppes at this time before I randomly bsod.  I have attempted googling the stop code I get to no avail.  I have not been able to find anything fitting to my situation.  I can post the stop code when i get home if anyone would be able to make use of this.</div><div></div><div>To give some background of my situation I would like to start off with my general specs.</div><div></div><div>cpu- AMD Athlon XP 3200+</div><div>mb- MSI K7N2 delta-ilsr (nforce 2 chipset)</div><div>ram- 2gb pc3200 (running dual-channel, have tried single channel with no change in stability for eq2)</div><div>case/psu- antec sonata 1- 380 watt psu that came with the case (definitely on the low side but has worked fine so far)</div><div>vid card-  old- Radeon 9800pro;  new- Sapphire radeon HD 2600 pro 512mb</div><div></div><div>This Motherboard only has an agp slot on it so I am very limited on my options for this system, but the hd2600 should be fine for this game and WOW at low to mid settings.  I am aware that the driver support for agp cards is very limited and not up to par at this time, but I have had success making this work with wow.</div><div></div><div></div><div>  I had a friend help build my system about 3-4 years ago.  He clearly did a shoddy job of the installation and I will never look to him for assistance again.  I have had many performance and crashing issues on this system over the years so this is not a new thing to me.  In the last week I have upgraded from my old video card of a radeon 9800 pro 128mb up to a radeon HD 2600 pro 512mb.  I installed the most recent hotfix drivers from the sapphire website over the drivers from the installation disk.  I found that overall this card was giving me a downgrade in performance from my previous card which did not make sense.  After a ton of research I finally found my base problem-  my friend never installed any form of chipset drivers for my system.  This meant my system was running with agp disabled this whole time...</div><div></div><div>  Due to this mb being so old I had a difficult time finding any relatively recent chipset and gart drivers, however I found what looks to be a decent set and installed it.  My system now runs with perfect stability with world of warcraft where I used to consistently get from 5-15 crashes on any given day.  I have not had a single one since doing the upgrade.</div><div></div><div>  To clarify the total changes I made-  1. New video card  2. New video card drivers  3. Installed chipset driver package including gart and several other drivers (was never anything installed before)</div><div></div><div>  Before I upgraded my system (in eq2) I used to get a few crashes and very rarely I would get a bsod, however it was generally playable.</div><div></div><div>  Here is my dilemma.  I have returned to this game to play with a friend and see if i like it, making use of the living legacy program.  I have been having fun with the game, however my priority is keeping my system working for wow because I have a raid guild depending on me being there to tank raids.  I am reluctant to essentially start from scratch and get a completely new set of chipset and vid card drivers because this could potentially bring issues back for wow.  If it would be of assistance I can post the dxdiag files when I get home from work if requested.</div><div></div><div>  My hopes are perhaps someone out there with more experience working on windows based pc's will have some suggestions on at least troubleshooting this issue to figure out where my problem is.  This is my first and only windows pc I have ever owned (previously a mac user but wasn't of much use for gaming at the time), so I am somewhat lacking on where to go from here.</div><div></div><div>Thanks in advance.</div><div></div><div>p.s. I apologize in advance if my post is a bit jumbled.  I have had to retype it up due to my terrible work internet connection failing while submitting previously...</div>

[dirtymeat80]

What's the blue screen error?If you didn't write it down, right click My Computer, Manage, and goto the Event Viewer.Done a memtest lately?<a href="http://www.memtest86.com/" target="_blank" rel="nofollow">http://www.memtest86.com/</a>

[Zedzorander]

For the sake of comparison giving the last 3 bsod messages incase that will help-The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0xe5c667c7, 0xf7706890, 0x00000000). A dump was saved in: C:WINDOWSMinidumpMini072008-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0xe41a5c25, 0xf7506890, 0x00000000). A dump was saved in: C:WINDOWSMinidumpMini071908-06.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0xe419dc25, 0x9c98f890, 0x00000000). A dump was saved in: C:WINDOWSMinidumpMini071908-05.dmp.I have not ran a memtest during the last week. Due to the fact that it was comparatively working fine prior to the changes I made and now not working at all, I have to suspect something I did rather than the memory going bad as the cause. It seems to me the most likely culprit would be in something I changed between it working and now not working rather than the ram which I haven't changed, though I suppose it could have gone bad. I have been having a tough time finding any decent agp drivers for this card to try as a test. I think I tried loading the game after installing vid card and drivers but before updating chipset driver and had same issue of getting a bsod so it seems reasonable to start with that driver (just thought of this this morning). edit: a new vid card driver just came out this morning, installed and gave it another try with the same result :/

[TSR-TrevorG]

The error 0x1000008e after reading up on this, could be caused by bad memory, or a faulty mobo.  I've seen some get fixed by reseting CMOS and updating BIOS.Try removing one of your sticks of memory for a little bit, run the game, if no error, try again but with the other stick removed.At the least you can run these types of tests and still be able to reconfigure quickly for a raid on Molten Core ( or w/e the best WoW raid zone is) <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />

[Zedzorander]

Thanks for the reply.<div></div><div>I will try each memory stick independently as well as in different slots so I can try to verify that at least one of the sticks isn't bad.  From the searches I did I found similar info, also stating it can be a cpu issue causing this bsod.  I suppose the next step prior to a new system would be to update the bios.  I have avoided this option since it seems to me to be pretty irreversible if screwed up.  It doesn't appear Msi has any updated bios out (last one in 2004) so it will be one modded by someone else which is my primary concern.  I suppose as a last resort it would be worth it.  Feel free to correct me if I am wrong here as my knowledge in this area is quite limited.</div><div></div><div>Current raids to waste my time in wow are Sunwell and Black Temple by the way <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></div><div></div><div>Looking back at it, I suppose the simplest thing to check after the ram would be to reinstall my old vid card and drivers and see how it runs with the existing bios, ram, and chipset drivers.  Likely it would run better than before since agp should actually be enabled now.</div><div></div><div>Any other users out there happen to be using an agp Hd 2600 pro and successfully have it working?</div>

[Mindrel]

<p>Hi there</p><p>            I have the exact same problem you have with a brand new computer just built. Each time my char log and I try to start a fight, after a few hit I get the blue screen and a reboot. I also play LoTR  and can play all day without a crash, so not sure if it is a Ram problem.</p><p>Vista 64 home,  Evga 780i motherboard,  2x Geforce 8800 gtx 768mo in SLI,  Q6700 2.66GHz CPU,  1000w SLI rdy Antec Powere supply,    8gig OC SLI ram.</p><p>           Also crash when I tryed playing AoC.  Both AoC and EQ2 are direct 9x,  and LoTR is 10x copatible... thought it could be the problem. But I see it happens to u as well... </p>

[TSR-TrevorG]

<cite>Zedzorander@Blackburrow wrote:</cite><blockquote>Thanks for the reply.<div></div><div>I will try each memory stick independently as well as in different slots so I can try to verify that at least one of the sticks isn't bad.  From the searches I did I found similar info, also stating it can be a cpu issue causing this bsod.  I suppose the next step prior to a new system would be to update the bios.  I have avoided this option since it seems to me to be pretty irreversible if screwed up.  It doesn't appear Msi has any updated bios out (last one in 2004) so it will be one modded by someone else which is my primary concern.  I suppose as a last resort it would be worth it.  Feel free to correct me if I am wrong here as my knowledge in this area is quite limited.</div><div></div><div>Current raids to waste my time in wow are Sunwell and Black Temple by the way <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></div><div></div><div>Looking back at it, I suppose the simplest thing to check after the ram would be to reinstall my old vid card and drivers and see how it runs with the existing bios, ram, and chipset drivers.  Likely it would run better than before since agp should actually be enabled now.</div><div></div><div>Any other users out there happen to be using an agp Hd 2600 pro and successfully have it working?</div></blockquote>If you do replace the video card, be sure to remove all drivers in safe mode with <a href="http://downloads.guru3d.com/download.php?det=745" rel="nofollow" target="_blank">Driver Cleaner</a>. Reboot and then reinstall again. This is just to make sure no old drivers remain.I'd try all the rest of course before you try th bios.

[TSR-TrevorG]

<cite>Mindrel wrote:</cite><blockquote><p>Hi there</p><p>            I have the exact same problem you have with a brand new computer just built. Each time my char log and I try to start a fight, after a few hit I get the blue screen and a reboot. I also play LoTR  and can play all day without a crash, so not sure if it is a Ram problem.</p><p>Vista 64 home,  Evga 780i motherboard,  2x Geforce 8800 gtx 768mo in SLI,  Q6700 2.66GHz CPU,  1000w SLI rdy Antec Powere supply,    8gig OC SLI ram.</p><p>           Also crash when I tryed playing AoC.  Both AoC and EQ2 are direct 9x,  and LoTR is 10x copatible... thought it could be the problem. But I see it happens to u as well... </p></blockquote>Let us know what the error is on the BSOD.  If you missed it like dirtymeat (lol bad name) said, you can find it here.Right click My Computer, Manage, and goto the Event Viewer.

[Mindrel]

<p>ok =) </p><p>            Since I had almost no Idea what to do after : computer, manage, Event viewer ;  I went to errors and copy 3 who happend at the same time I crashed. Hope it help, if not let me know what u need <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p><p>Application Popup  :   SystemRootSysWow64DriversULCDRHlp.sys    000000000200300000000000240400C0000000006C0300C000 000000000000000000000000000000 </p><p>Even Log:     17:57:20    2008-07-24            619            D807070004001800110039001400A302D80707000400180015 0039001400A302600900003C00000001000000600900000000 0000B00400000100000000000000 </p><p>Http event : DeviceObject DeviceHttpReqQueue   SecurityPackage Kerberos    000004000200300000000000A83A00C0000000000000000000 0000000000000000000000000000000E030980 </p><p>Bah I hope it is what u asked for, cause I just dont write fast enough for the blue screen report. I'll restart as needed tho if you need the blue sceen word for word</p>

[Wingrider01]

<cite>Mindrel wrote:</cite><blockquote><p>ok =) </p><p>            Since I had almost no Idea what to do after : computer, manage, Event viewer ;  I went to errors and copy 3 who happend at the same time I crashed. Hope it help, if not let me know what u need <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p><p>Application Popup  :   SystemRootSysWow64DriversULCDRHlp.sys    000000000200300000000000240400C0000000006C0300C000 000000000000000000000000000000 </p><p>Even Log:     17:57:20    2008-07-24            619            D807070004001800110039001400A302D80707000400180015 0039001400A302600900003C00000001000000600900000000 0000B00400000100000000000000 </p><p>Http event : DeviceObject DeviceHttpReqQueue   SecurityPackage Kerberos    000004000200300000000000A83A00C0000000000000000000 0000000000000000000000000000000E030980 </p><p>Bah I hope it is what u asked for, cause I just dont write fast enough for the blue screen report. I'll restart as needed tho if you need the blue sceen word for word</p></blockquote>Turn off auto restart on system reset - My computer --> Properties --> Advanced --> Startup and recover --> Settings ---> remove check mark from Automaticly Restart. You will have ot power cycle or punch the reset button to restart the machine

[Mindrel]

<p>Awsome thx Wingrider..</p><p>       Here's the blue screen report :   Stop: 0x00000116 (0xFFFFFA800E8DB010, 0xFFFFFA6003415E00, 0x0000000000000000, 0x0000000000000002)</p><p>                                                           nvlddmkm.sys - Adress FFFFFA6003415E00 Base at FFFFFA6003408000 datestamp 482e07f5.</p><p>   Hope that helps.</p>

[TSR-TrevorG]

You may wish to go to your bios and change your memory frequency to 666Mhz (or 333Mhz if you have DDR) I've seen that work for other issues with nvlddmkm.sys problems.You may also want to try make sure UAC is turned off as well.

[Wingrider01]

<cite>TSR-TrevorG wrote:</cite><blockquote>You may wish to go to your bios and change your memory frequency to 666Mhz (or 333Mhz if you have DDR) I've seen that work for other issues with nvlddmkm.sys problems.You may also want to try make sure UAC is turned off as well.</blockquote>Havent seen that stop for awhile, thought it was fixed in the Nvidia drivers a long time ago. Normally coincides with OC'd memory or video card. What driver level are you running?

[Mindrel]

Run on the lastest driver  for my cards, the 175.19.  Well that is the latest on Nvidia site anyway...