BSOD - "Pagefault in Nonpaged Area" and "critical_object_termination" - Help!

lexer

Reputable
Jul 1, 2014
9
0
4,510
Does anyone have experience with these particular situation? It's happened a couple times, sometimes right after I click shutdown, sometimes right after I click "quit" in counterstrike.

I don't know if this is related, but CS:GO recently started "stuttering" or "elastic banding" (walk 2 steps, get teleported right back). It's not the GFX card because I've already swapped it with my brother's and the stuttering still occurs (though not as severe).

Anyways, the BSOD is my main concern. I've tried googling the solution, but I'm not as technically advanced as you guys so I figured asking for help would be the best bet!

This is my setup:

Gigabyte Z87-D3H (socket 1150)
Intel i5 4670
Kingston Hyper X Black
Seagate ST1000DM003-1CH162 1TB 7200 RPM 64MB
Samsung SSD 840 Evo (recently purchased, currently running Windows 7 off of this SSD after reformatting, however BSOD occured before I purchased this SSD as well)
Corsair Tx550m
NVIDIA GTX 560 (currently using my brother's 560, I was originally using the GTX 650 Ti Boost when the BSOD started happening)

and Corsair 200r tower and BENQ 2225 21.5'' LED

running 64-bit Windows 7

Here's the most recent BSOD event:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C2D6E030
BCP2: 0000000000000000
BCP3: FFFFF960002DC69D
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070114-6614-01.dmp
C:\Users\xxxxx\AppData\Local\Temp\WER-8330-0.sysdata.xml

And here are the ones in the past that I've copied down:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF96000174283
BCP3: FFFFF88008271020
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050114-65208-01.dmp
C:\Users\xxxxx\AppData\Local\Temp\WER-67985-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002A8A01E
BCP3: FFFFF880092EADE0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050514-64678-01.dmp
C:\Users\xxxxx\AppData\Local\Temp\WER-66160-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C00C07A0
BCP2: 0000000000000000
BCP3: FFFFF9600064DC51
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052214-125721-01.dmp
C:\Users\xxxxx\AppData\Local\Temp\WER-128622-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C00C07A0
BCP2: 0000000000000000
BCP3: FFFFF9600076DC51
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050114-64662-01.dmp
C:\Users\xxxxx\AppData\Local\Temp\WER-66191-0.sysdata.xml

If anyone has any insight into this issue, I would be hugely grateful for your help. Thanks in advance!
 
Solution
that should do it, if i recall, the bug had to do with windows trying to create a buffer in the graphic driver for its own use for when it was about to screen saver image. it was later fixed. The only people that hit it now are the ones who do a clean install with old win 7 RTM and then install a current graphics driver.
oh, be sure to reboot after you install the graphics driver or windows will screw up your graphics drivers when you do all the updates. (otherwise you get a nice black screen you have to deal with) just reboot after running any microsoft update to a graphics driver. or reboot before running the OEM update to a graphics driver


supasieu

Reputable
Mar 10, 2014
475
0
4,960
Locate the .dmp file from C:\Windows\Minidump and use file sharing website (filedropper, tinyupload, sendspace, wikisend) to upload the file. Once uploaded the website will give you a link to download the file. Paste the link in here and others can download it.
 

lexer

Reputable
Jul 1, 2014
9
0
4,510


Here it is:
 

supasieu

Reputable
Mar 10, 2014
475
0
4,960
Go to Start and type in cmd.exe
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the Command-Prompt black window, type SFC.EXE /SCANNOW and press Enter
Let the program run and post the results.
 

lexer

Reputable
Jul 1, 2014
9
0
4,510


Okay I just did that. It says:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

I've gone ahead and located the CBS.log file using the aforementioned path and uploaded onto filedropper.

Here it is:
 
old bug caused because you are using a old version of window release to manufacturing that does not have the updates or service pack. generally you apply the service packs if you want a fix.

in particular your graphics driver is a current version and will expect to be running on a version of windows that has the various fixes installed. Best to apply the service pack or install a very old version of your graphics driver that works around the bug.

you might want to also remove your very old asus utilities, there were lots of issues with memory corruption with them. remove them or update them if you can.
 
that should do it, if i recall, the bug had to do with windows trying to create a buffer in the graphic driver for its own use for when it was about to screen saver image. it was later fixed. The only people that hit it now are the ones who do a clean install with old win 7 RTM and then install a current graphics driver.
oh, be sure to reboot after you install the graphics driver or windows will screw up your graphics drivers when you do all the updates. (otherwise you get a nice black screen you have to deal with) just reboot after running any microsoft update to a graphics driver. or reboot before running the OEM update to a graphics driver






 
Solution