BSOD playing ESO, BCCode a.

NoelDP · 09 Jun 2015

KB3022345 still looks to be installed - unless it's MS's new incarnation of it, KB3068708 (I have no knowledge of whether removing this update will affect anything.)

Requimatic · 09 Jun 2015

I'm uninstalling it right now. I'm being prompted for a restart at this point.

Do you want me to try another sfc /scannow once I do?

Edit: I restarted and ran SFC; this time it found no errors. However, Windows Update has appeared with two important updates to install: KB3045999 (4/14/2015), and KB2882822 (10/8/2013, whaattt?).

NoelDP · 09 Jun 2015

I suspect that KB2882822 was uninstalled by either of the later two updates, you should install it.
KB3045999 should definitely be installed.

Requimatic · 09 Jun 2015

Alrighty, they're both reinstalled.

NoelDP · 09 Jun 2015

Great - Hopefully the next incarnation of these two updates (KB3022345 and KB3068708) will actually work properly, without annoying everybody.

Requimatic · 09 Jun 2015

That would be pretty great, haha.

No new BSODs today, but the other user had Modern Warfare 2 crash on them. I actually managed to get some details on the crash this go around, and they said that... the sound continued as if the game were still running, then it closed with an error. From the event viewer:

Code:

Faulting application name: iw4sp.exe, version: 0.0.0.0, time stamp: 0x4af4bdcc
Faulting module name: nvd3dum.dll, version: 9.18.13.5286, time stamp: 0x55515d5a
Exception code: 0xc0000005
Fault offset: 0x00758043
Faulting process id: 0xcb0
Faulting application start time: 0x01d0a2e97f84ca43
Faulting application path: C:\Program Files (x86)\Activision\Modern Warfare 2\iw4sp.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 7e79e414-0ede-11e5-8296-001fbc09890f

The odd thing, though: I played WoW almost the entirety of the night (between working with Noel) and had zero issues. MW2 seems to want to crash, and Elder Scrolls Online seems to want to crash. It's kiiiinddd of starting to look like a problem with the video card itself, the driver, or it's some weird intermittent thing that's going to be nearly impossible to isolate.

But this whole mess started happening before I updated the driver... so I don't know about that.

Do you think perhaps the card isn't getting enough power for those games? For instance, I could try changing the power leads from the PSU to the GPU, as I believe I have a few of the 4/6-pin cords available (modular PSU).

Fun!

essenbe · 09 Jun 2015

Yes it is possible the card isn't getting enough power, but I wouldn't think it was the leads. At least I have never had one or heard of one with bad leads, especially from Corsair. I think I would be more concerned that the PSU itself is having 'hiccups'.

Sometimes it is the game itself though. Although I played MW2 a while back and never had a problem.

Requimatic · 10 Jun 2015

Another BSOD, this time while playing TF2. The game got hung up at first, so I closed it via the Windows prompt. Seconds later, another PNF_LIST_CORRUPT; BCCode 4e; memory_corruption BSOD.

(Note: due to the frustration of being unable to analyze my own dump files, I've installed/configured WinDBG following the instructions on a thread from these forums. :) )

This is saying memory problems. The 10+ hours of memtest86+ I ran earlier in the thread passed it. I'm assuming I should probably run it again. Intermittent errors are... extremely annoying. In any event, I'm no expert on analyzing dump files, so I'll attach the zip file created by the log collector.

Based on that, what would you suggest? Another round of memtest?

essenbe · 10 Jun 2015

here's what it said

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 1b3a5, 2, 1c524}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner

Code:

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000001b3a5, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000001c524, 0
Debugging Details:
------------------

BUGCHECK_STR:  0x4E_99
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
CURRENT_IRQL:  2

Requimatic · 11 Jun 2015

Worth asking, since I'm still grasping at straws trying to figure this out, but:

I downloaded HWMonitor to see if there were any discrepancies in temperatures between it and the LED on the motherboard. There isn't, however: HWMonitor states that my core temps, while idle, are: 68/67/66/66c, with a variance of 1-2c.

Question is: are those core temps too high? If so, this whole issue could be as simple as this system getting too hot, and it shutting down because of it. I never thought it was an issue due to the LED displaying nothing above 64c, but if the cores are hotter just by default, it stands to reason that they could be getting too hot during those 3 CPU-heavy games (MW2, TF2, ESO) and BSODing as a result.

I'll say this though: our air conditioner hasn't been turned on yet, and the ambient temperature in the room is fairly high; about 75-80F.

If it being too hot is the issue, then this is solved, and I need to stress the use of the A/C to cool it down in here, just for the sake of the PC and the laptop.