BSOD playing ESO, BCCode a.

Requimatic · 03 Jun 2015

Well, it's been a few days since I updated this. It appears that cleaning the contacts on the memory modules was all that was needed to begin with... since doing that, I've had no weird issues at all, even with Steam. (Although I still haven't reinstalled TF2, so I don't know if that map texture issue was related or perhaps they became corrupted somehow.)

But since doing that, I haven't had any weird things happen, be them games crashing, BSODs, or MSE's service randomly stopping. I figured I'd give it a couple days at least (since things were going well) to post here again, and it's been a few, so there's that at least.

The only odd thing to happen since all of this is that lovely GWX.exe Microsoft slipped in through Windows update starting every time I boot the machine, or switch users, or at 6PM or whenever the task is triggered to start the program. But I (and I assume everyone else here) knows what that is, and how to get rid of it if need be, haha.

In any event, thanks again for the assistance and patience. Hopefully cleaning those modules was all that was needed... they were surprisingly dirty; some black residue, which I assume was just from being in contact with the metal contacts on DIMM slots (like old NES carts), and some brown-ish residue, which I assume was a combination of dust/dirt/? from the air itself.

If any more BSODs happen I may be back with more dump files, but so far everything is good. Kinda hate we went through all that trouble only to have the modules cleaned and have things clear up, but as old as this hardware is, putting it through stress tests and seeing it pass is pretty good I suppose.

Anyway, thanks again, and have a good one!

NoelDP · 03 Jun 2015

GWX is the 'Get Windows 10' notification - if you want to get rid of it, uninstall and hide the KB0305583 update

essenbe · 03 Jun 2015

I'm glad it's working for you.

Requimatic · 08 Jun 2015

Hate to necro the thread, but I'm back again with more BSODs!

I'm fairly certain that it's the hard drive that's causing the problems. After installing a couple optional KB files the other night, after restarting so it could finish installation, Windows randomly decided to run chkdsk. This was after having issues trying to play ESO all day long. It crashed twice, then got to the point that it wouldn't even run. When launching the game it would just crash immediately with a "BEX HashStack_xxxx" error.

In any event, here's the log collector files.

I have a feeling I'm going to be seeing another run of memtest and/or a chkdsk /f /r in my very near future.

Either way, if I can isolate it and replace the hardware I'll be glad to get it done.

Thanks in advance!

essenbe · 08 Jun 2015

Hello again, Requimatic. The dump file is blaming a video error, specifically a video memory error.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880045e1853, fffff880055c55d0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f53 )
Followup: MachineOwner

That is direct X, but it is usually caused by a video driver crashing as was later pointed to in the dump.

Code:

fffff880`055c4c78  fffff880`04b09728Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x27e728

Due to the fact that you are having hard drive problems reported, I would suggest you checking that first. The image that was in use at the time of the crash was iw4sp.exe, which I believe is Modern Warfare 2 . One of your 2 dump files would not open as they were corrupted, which may also point to a hard drive error.

I would run the Diagnostic tests on the hard drive. I believe your system specs list a Western Digital Hard drive. Western Digital's Data Lifeguard for DOS can be found at WD Support / Downloads / SATA & SAS / WD Black Please run the long and short test. There have been some reports of trouble with that program. If you have issues I would run Seatools for DOS, SeaTools for DOS and Windows - How to Use both the short and long test. Also please run check disk Disk Check

If you have any questions, please feel free to ask.

essenbe · 08 Jun 2015

I did some further looking and noticed several errors from eso.exe which is Elder Scrolls. If you believe it to be a Hard drive error, I would strongly suggest you backing up your personal files to an external source, preferably an external hard drive.

Requimatic · 08 Jun 2015

I see. Unfortunately, with our last round of testing earlier in the thread, I was unable to use either DOS-based HD tools (Seagate or WD's). I was able to use both of the Windows-based ones, but with the hard disk currently in use I question their results with how many times the system itself has wanted to run chkdsk in the past 48 hours.

I think what I'll do first, in this case, is go ahead and schedule a /f /r and see what it finds.

Edit: Yeah, all of yesterday I experienced issues with ESO. It started out fine, but then crashed randomly. I started it back up, played again for a bit, and it crashed again. That time, it wouldn't run at all afterwards. I restarted and it would run again, but I exited the game without even logging in to check on why it crashed, and a bit later discovered it wouldn't run due to that "BEX HashStack_xxxx" error. That continued all day. It was later that night that I installed the two optional KB updates and chkdsk ran during a restart while I was up.

I came back just in time to watch it find a boatload of orphaned .jar files.

Layback Bear · 08 Jun 2015

Did you ever complete the test essenbe recommended?

I would suggest forget the games and follow essenbe instruction exactly and let him know the results.

Requimatic · 08 Jun 2015

Layback Bear said:

Did you ever complete the test essenbe recommended?

I would suggest forget the games and follow essenbe instruction exactly and let him know the results.

During the first round of testing, I was unable to run either DOS-based HDD tests. The WD DOS-based test just failed to run entirely (it would go to command prompt as per normal, but trying to run the program resulted in a blank screen that did nothing), and the bootable USB drive wasn't recognized at all when attempting to use the Seagate DOS-based test, even after following instructions to make the drive bootable and whatnot.

The Windows version of both said the HDD passed all tests (the short/long versions, anyway), but seeing as this drive is the only one in this machine, the results of running it on the drive while it's active are questionable; at lest to me. Especially considering the system itself flagged the drive for chkdsk without BSODing first. (Just after a full day of games crashing, and after those two updates installed.)

chkdsk is still running; at the last stage. It hasn't found anything so far, but that doesn't mean it won't during the last step. (I'm on a laptop currently.)

Requimatic · 08 Jun 2015

The results are in, and... chkdsk has determined that the drive is clean. Kind of hard to believe... but it is what it is, I guess.

So with that in mind, and considering that my video drivers are up to date... what would you suggest? Another round of memtest? Maybe a longer-than-a-few-minutes GPU test with Furmark?

I was almost positive it was the hard drive, with how it's been acting, but I am apparently wrong. I suppose I could try replacing the SATA cable; I believe I have a spare.

I'm pretty much at my wits' end with this thing at this point.