BSOD 0x10e while watching Youtube vid, but laptop is recently unstable

RJtheShadow · 03 May 2013

Simply put, the past few days, my Laptop has been misbehaving quite badly.

While playing Tera, the laptop sometimes locks up completely, giving the familiar hanging sound that usually comes with a BSOD. But not always yielding one. The two times it did bring up a BSOD, there was no dump file made. In response to this, I renewed the page file a few times. Even going so far as to disable it, rebooting, deleting the file, then re-enabling it. Double-checking if it has re-appeared, which it has. (obviously, yes, it's set to create a dump file upon bsod)

After a few more hangs, I had two more bluescreens. One where the dump creation was 'about to' get started, but simply didn't.
Second time, I wasn't playing Tera by exception, but was actually watching a Youtube video. It actually yielded the familiar result of it slowly creating a dump file. Finally.
It should be included with this post.

I've upgraded my Graphic Card drivers, which didn't stop this thing from acting up.
It always seems to happen more frequently, the longer the laptop has been 'running'. (not counting crashes and reboots)
This made me think something was overheating. But touching the areas where it used to be overheat (before I was as informed about overheating) did not feel exceptionally hot, and even cleaning out the laptop yields no improvement.

Just this afternoon, I've ran a complete diagnostics on the Hardware using the built-in system Dell has for that. This yielded no result. Hardware seems fine.

I hope you can read the specs I filled in when signing up for an account. So you no longer need to ask that.
A final piece of information might be that the laptop is the Alienware M15X.

I've provided all the information I can give from the top of my head. If you require more, you are more than welcome to ask. Any response is better than none.

Help with solving this problem is very welcome, but I would also always like any suspected culprits/theories. To not go into details, I dabble in computers more than frequently, especially networks. However, BSOD's are very much a terrain for me that I've well experienced, but have not been quite taught well in.
a.k.a. Please share your wisdom, if possible.

marsmimar · 03 May 2013

According to the dump file you provided, there seems to be an issue with dxgmms1.sys, a DirectX Graphics MMS driver. This driver is normally updated through Windows Update.

Driver Reference Table - dxgmms1.sys

Also, you are showing bugcheck code 10E which could be an indication of an outdated or "buggy" Nvidia Video driver. If you have the latest driver you might try using a previous version as not all updated drivers "play nice". In the interest of full disclosure, I edited to dump file to a more manageable size.

Random Blue Screens daily - Microsoft Community

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a004304b20
Arg3: 0000000000000000
Arg4: 0000000000008c97

Debugging Details:
------------------
FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`04dce098 c7442450c5f3ffff mov     dword ptr [rsp+50h],0FFFFF3C5h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

BUCKET_ID:  X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148

Followup: MachineOwner
---------

RJtheShadow · 03 May 2013

Yes, BlueScreenView also popped up watchdog.sys as...well, the red line I assume means it had something to say as well. Seeing as I use MSE, and watchdog.sys BSOD's on Google are more often linked to AVG or other AV's, I somewhat ignored it.

The issues began before I updated my driver. I was of the belief too that the latest don't always play nice, but since I was already having issues, I figured 'why not'. Maybe I just added another problem.

On other news, I just had another Bluescreen while playing Tera. And again, it refused to make a dump.
I could paste a .jpg of it, but I suppose typing the essentials will suffice too, no?

IRQL_NOT_LESS_OR_EQUAL
STOP: 0xA (0xFFFFF7000a3276B0, 0x0, 0x0, 0xFFFFF8000AEC10B)

Collecting data for crash dump...

This last line is where it stays, refusing to create a dump. As said, I've removed a corrupt pagefile as a possible culprit.
I've also checked if Tera started with Physx by default. It seems, you need to install something in Tera to make Physx work. So that can't be the culprit either.

I can still provide the actual screenshot of it though, which I took with my smartphone.

Here's a long shot guess:
At my work (where I am, for now, an apprentice) we've had a few computers as well that started acting up with the latest Windows update, and I suspect my troubles began too since the latest update.
They were also Windows 7, but had very old ATI graphic cards (designed for WinXP!).
So maybe that might not be it, but I figured I'd throw it in here.

Thank you for the quick response, by the way.

marsmimar · 03 May 2013

It wouldn't cause any issues if you wanted to uninstall the latest updates to see if that makes a difference.

Windows Update - Uninstall an Update

If the problems are fixed, you could reinstall the updates but just one at a time. Reboot the computer after each update and run the computer for a while to see if the problem returns. If it does, you'll know exactly which update is at fault.

RJtheShadow · 03 May 2013

Alright, I'll try that. Do a rollback of the most recent update, play Tera until either the inevetable happens, or a few days of extensive gaming passes.

If the rollback doesn't help, I'm going to try and rollback the Graphic Card driver. I think I left the driver files somewhere on C:/. I know I removed a few older installing files.

I'll update this topic with any results, unless I forget. (I shouldn't)
Is there anything else you suggest I could do? Or any culprits you're thinking of? I already ran a dxdiag test. It didn't seem to bring up anything.

RJtheShadow · 03 May 2013

It seems the only updates as of recent were the Definition Updates for MSE. Seems unlikely to cause trouble. I'm going to instead do a rollback of my graphic card. See what that yields.

RJtheShadow · 04 May 2013

Sorry for the triply reply, but I had a new development a few hours ago.
I had uninstalled my Nvidia drivers and reinstalled all of them with the 306.97 drivers. Then I was playing Tera, and again got a BSOD. It managed to create a dump file, which should be inclosed.

marsmimar · 04 May 2013

The newest dump file is showing a problem with Bugcheck 50, CIRAP.exe, and the following drivers:
dxgmms1.sys (DirectX Graphics MMS)
dxgkrnl.sys (DirectX Graphics Kernel)
win32k.sys (Multi-User Win32 Driver)
fvevol.sys (BitLocker Driver Encryption Driver)
CLASSPNP.SYS (SCSI Class System Dll)
partmgr.sys (Partition Management Driver)
volmgr.sys (Volume Manager Driver)
rdyboost.sys (ReadyBoost Driver)
nvlddmkm.sys (nVidia Video drivers)
volsnap.sys (Volume Shadow Copy Driver)

The following links give more info about these problem areas including update info.

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA (Windows Debuggers)

What is CIRAP.exe ? CIRAP.exe info (NOTE: This appears to be an advertisement and is offered only for the info about this .exe file.)

Driver Reference Table - dxgmms1.sys

Driver Reference Table - dxgkrnl.sys

Driver Reference Table - win32k.sys

Driver Reference Table - fvevol.sys

Driver Reference Table - CLASSPNP.SYS

Driver Reference Table - partmgr.sys

Driver Reference Table - volmgr.sys

Driver Reference Table - rdyboost.sys

Driver Reference Table - nvlddmkm.sys

Driver Reference Table - volsnap.sys

As before, I took the liberty of editing the dump file to a more manageable size.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880158b2000, 1, fffff80003aa7b41, 2}

Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880158b2000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80003aa7b41, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------
Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cb4100
 fffff880158b2000 

FAULTING_IP: 
nt!RtlpCopyContext+9d
fffff800`03aa7b41 208b0000f30f    and     byte ptr [rbx+0FF30000h],cl

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1
------------------
DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  CIRAP.exe

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

fffff880`059814e8  fffff880`04d2f9a4 dxgmms1!VIDMM_GLOBAL

fffff880`05981588  fffff880`04c45906 dxgkrnl!DXGADAPTER::ReleaseCoreResource+0x146

fffff880`05981608  fffff960`0025c460 win32k!EngReleaseSemaphore+0x2c

fffff880`05981708  fffff880`01cf12bf fvevol!FveReadWrite+0x47

fffff880`05981908  fffff880`01d41445 CLASSPNP!ServiceTransferRequest+0x355

fffff880`05981a48  fffff880`00e340af partmgr!PmGlobalDispatch+0x9f

fffff880`05981a78  fffff880`00e5e18c volmgr!VmReadWrite+0x11c

fffff880`05981cc8  fffff880`01ca4405 rdyboost!SmdDispatchReadWrite+0xd9

fffff880`05981ce8  fffff880`0f6dd627Unable 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+0x1fb627

fffff880`05981cf8  fffff880`01c37df4 volsnap! ?? ::FNODOBFM::`string'+0x57b

I'd start with the basics. Run a full scan with your installed and updated anti-virus suite. No anti-malware product is 100% effective 100% of the time. If there was such a product we'd all be using it. Do another scan with the free Malwarebytes.

Also check all cables, hardware is seated properly, etc

I'd also check for damaged or corrupt system files by running a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and reboot your computer immediately after each scan.

SFC /SCANNOW Command - System File Checker

RJtheShadow · 04 May 2013

So, again, after a few hours of gameplay, I had a bsod which landed a dump file. (maybe that refreshing of the page file did help something)
After I made sure I had it zipped up, I read your instructions, and got started on those.
For good measure, I'll still upload the dump file.

Malwarebytes found no issue after a quick scan and three hours of a full scan. (I canceled it because I am confident that I keep a clean ship on this laptop, at least in terms of software and such being installed)

However, the sfc /scannow did reveal there might have been some corruption going on. I checked the log as it suggested, and the list seems lengthy. Though I don't know if that is normal (say, if it records -everything- that is checked), or if this is an actual list of malfunctioning files.

Regardless, as you said, I am going to reboot and run it three more times (with a reboot after each) and let you know the progress. I figured it was prudent to already update the current progress.

Thank you for the help so far.

RJtheShadow · 04 May 2013

I've ran it three times now, each with a reboot. It stills says there have been files found that are damaged, but can't be repaired.
So there's a good chance my problem may have lied therein. What would your suggestion be to clean up the rest? Run it on boot as per Option 1? It suggests using the installation DVD, but this laptop didn't come with one. (as what seems to be common nowadays if you don't put it together yourself)

Also, the second time, MSE's protection shield was briefly disabled, then started again. I suppose it had something broken as well?

EDIT:
As expected, playing Tera for a little while threw up another BSOD. Dump file should be below.