BSOD while playing games (SC2, Planetside 2, The War Z), 0x00000050

Another KMODE_EXCEPTION_NOT_HANDLED. Wasn't even playing games this time, was just browsing on YouTube and talking on Skype/GChat. Really confused to the root of the problem right now...

==================================================
Dump File : 122012-8970-01.dmp
Crash Time : 12/20/2012 11:09:46 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02ae0ae0
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+2db080
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122012-8970-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 292,840
==================================================

Code:

BugCheck 50, {fffff8b008442118, 0, fffff8800456b135, 5}

Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5 )

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• Screenshots and Files - Upload and Post in Seven Forums

Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:

• Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

Follow these instructions to upload all the dump files:

• https://www.sevenforums.com/crashes-d...tructions.html

Remove avast! (at least to test):

Code:

Start Menu\Programs\avast! Free Antivirus

avast! can cause BSODs with Windows 7.

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation

Here's my CrystalDiskInfo screenshots. The F: Drive I use as my media storage.

Running malwarebytes right now, and I will remove Avast! and install MSE.

Post back the results of Malwarebytes and MSE, and remember to run the hard-drive tests specified in Post #22.

Had a few pieces of malware, that I removed successfully. Seagate Hard drive tests came back clean. Been Bluescreening a lot lately... Been getting The usual Page_fault_in_nonpaged_area, along with IRQ_NOT_LESS_OR_EQUAL, DRIVER_IRQ_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and SYSTEM_SERVICE_EXCEPTION.

I'm sick of this. I will run the driver verifier all night and see if it crashes, but I'm about to just buy new memory and a new motherboard from NewEgg. I've never had a problem like this that I wasn't able to solve, but this has me stumped.

I've uploaded the latest logs.

Code:

BugCheck D1, {122, 2, 1, fffff88001503062}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Code:

Usual causes:  Device driver

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8800150306c - ndis! ?? ::FNODOBFM::`string'+cd54
	[ 48:58 ]
1 error : !ndis (fffff8800150306c)

Code:

2: kd> !chkimg -d -db !ndis
    fffff8800150306c - ndis! ?? ::FNODOBFM::`string'+cd54
	[ 48:58 ]
1 error : !ndis (fffff8800150306c)
fffff88001503060  8b  c5  48  89  88  20  01  00  00  48  8b  00 *58  85  c0  75 ..H.. ...H..X..u

It seems you may have problems with your RAM, or the ndis.sys file has become corrupted by malware; ndis.sys is the Windows Network Interface Controller driver, and Windows drivers rarely are the true cause of BSODs.

Follow these steps:

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• Driver Verifier - Enable and Disable

More Help and Information with Driver Verifier - Using Driver Verifier to identify issues with Drivers

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Scan for any missing, modified or corrupted protected Windows files with:

• SFC /SCANNOW Command - System File Checker

Thank you, x BlueRobot, I will run the driver verifier again all night and see if my machine has crashed when I wake up.

I have ran Memtest 86+ for a total of 15 passes and no errors were found.

I have also ran chkdsk /f /r as well as SFC /Scannow and no errors were detected.

Okay that's good to know, doesn't seem there isn't anything wrong with your system files or RAM, and did you run full scans with the security programs provided?

What were the results of Driver Verifier so far?