BSOD while playing games

[yuskey]

Hey guys,

So just built my new pc about a week ago and everything seemed fine till 3 days ago. My monitor screen would randomly go black when i was playing a game and the tower would stay on. While trying to find a solution to that i keep getting BSODs. I uploaded the .dmp files within the post.

If anyone has any advice id greatly appreciate it, on both issues.

System Specs:
AMD Phenom II x6 1100T
Visiontek Radeon 6850
2x 4g ddr3 ram, corsair
850W psu
MSI 870a power fuzion mobo

 

[Ace]

Since this is a custom build and it's fairly new i'm guessing it could be many things.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88026122584, 0, fffff960001e6112, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff88026122584, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001e6112, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001d12100
 fffff88026122584 

FAULTING_IP: 
win32k!xxxDCEWindowHitTest2+316
fffff960`001e6112 448b9c2404010000 mov     r11d,dword ptr [rsp+104h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800c1222f0 -- (.trap 0xfffff8800c1222f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c0853b40 rbx=0000000000000000 rcx=fffff8800c1224f0
rdx=fffff900c0853b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001e6112 rsp=fffff8800c122480 rbp=00000000fffffffe
 r8=0000000000000000  r9=00000000023b01eb r10=0000023b000001eb
r11=fffff8800c122460 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!xxxDCEWindowHitTest2+0x316:
fffff960`001e6112 448b9c2404010000 mov     r11d,dword ptr [rsp+104h] ss:0018:fffff880`0c122584=0000023b
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001a8a3f0 to fffff80001adfc40

STACK_TEXT:  
fffff880`0c122188 fffff800`01a8a3f0 : 00000000`00000050 fffff880`26122584 00000000`00000000 fffff880`0c1222f0 : nt!KeBugCheckEx
fffff880`0c122190 fffff800`01addd6e : 00000000`00000000 fffff880`26122584 00000000`00000000 fffff900`c0862720 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`0c1222f0 fffff960`001e6112 : fffff900`c0862720 00000000`fffffffe 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`0c122480 fffff960`001e5db3 : 00000000`c0001840 00000000`00000001 ffff01e0`0c25a430 fffff880`0c122b50 : win32k!xxxDCEWindowHitTest2+0x316
fffff880`0c122560 fffff960`001e60f5 : fffff900`c08539f0 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c1225e0 fffff960`001e5db3 : fffff880`0c122710 00000000`00000001 00000000`00000001 00000000`0000029e : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c1226c0 fffff960`001e60f5 : fffff900`c085d6e0 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122740 fffff960`001e5db3 : 00000000`00000000 00000000`00000001 00000000`00000f82 ffffffff`ac120f82 : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122820 fffff960`001e60f5 : fffff900`c080e970 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c1228a0 fffff960`001e5db3 : 00000000`00000000 fffff800`00000000 fffff900`c06c0ce0 00000000`00000001 : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122980 fffff960`001e60f5 : fffff900`c0826840 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122a00 fffff960`001e5db3 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff800`01ae4f32 : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122ae0 fffff960`001e60f5 : fffff900`c0869db0 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122b60 fffff960`001e5db3 : 00000000`00000030 fffff880`0c122d28 00000000`00000000 fffff800`01dcbb66 : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122c40 fffff960`001e60f5 : fffff900`c0825810 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122cc0 fffff960`001e5db3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff960`0017b69b : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122da0 fffff960`001e60f5 : fffff900`c0800b90 00000000`fffffffe 00000000`00000001 00000000`00000001 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122e20 fffff960`001e5db3 : 00000000`00000000 fffff900`c25e5680 fffff880`0c1233e8 00000000`00000001 : win32k!xxxDCEWindowHitTest2+0x2f9
fffff880`0c122f00 fffff960`00140070 : 00000000`00000001 fffff880`0c123520 00000000`000001eb 00000000`00000000 : win32k!xxxDCEWindowHitTest+0xd7
fffff880`0c122f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxScanSysQueue+0x1124


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
6 errors : !win32k (fffff960001e61c1-fffff960001e61f1)
fffff960001e61c0  e3 *d3  1a  00  01  48  89  05  24 *8b  1a  00  85  ff  75  53 .....H..$.....uS
fffff960001e61d0  4c  8b  94  24  00  01  00  00  44 *0f  9c  24  04  01  00  00 L..$....D..$....
fffff960001e61e0  41 *e1  b7  cb  41  0f  b7  c2  c1 *83  10  0b  c8  4c  63  c9 A...A........Lc.
fffff960001e61f0  f0 *44  05  48  33  1a  00  01  c7  44  24  38  01  00  00  00 .D.H3....D$8....

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
---------

Bugcheck 0x50: PAGE_FAULT_IN_NONPAGED_AREA

It could be due to faulty hardware, corrupt system service, and a couple other things. What kind of AntiVirus are you currently running (if any)? Disable it and see if it resolves your problem first if you are currently running one. Disable any overclocking if you have anything like that set up on your custom PC before continuing.

1) Check EventViewer - for any critical messages and/or errors that may be useful
2) Run CheckDisk
-Run this through command prompt

Chkdsk /f /r

This is to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk itself.

Make sure that your RAM is properly re-seated, otherwise try re-seating them, and then proceed by running a memory test on boot:

3) Memtest86

Download and run Memtest86 on boot: http://www.memtest86.com
Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.

If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.

Reply with updated information in this thread and any newer bsod dumps. Your latest one refers to Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION which has been known to be related to graphics drivers but the majority of them are 0x50 and the earlier one is 0x1A. Majority refers to in-memory problems/issues.

My best guess here is that you have corrupted memory. One dump tells me that Internal memory management structures are corrupted (0x1A).

If the above doesn't work I'll provide you with the necessary steps to run Driver Verifier.

 

[yuskey]

Well I'm running memtest86 right now and I have avast anti virus. Do you have any idea what could cause the screen going black but the tower staying on? I assumed it was some sort of overheating but my video card doesn't get higher than 64 when playing Dead island maxed out. My psu is 850 so im assuming its good enough. I should also mention that when the screen went black and i tried turning it off by holding the power button nothing happened. I had to pull the plug to actually get it to turn off.

 

[Ace]

Well I'm running memtest86 right now and I have avast anti virus. Do you have any idea what could cause the screen going black but the tower staying on? I assumed it was some sort of overheating but my video card doesn't get higher than 64 when playing Dead island maxed out. My psu is 850 so im assuming its good enough. I should also mention that when the screen went black and i tried turning it off by holding the power button nothing happened. I had to pull the plug to actually get it to turn off.

No the power button option should work, but it takes about 8-10 seconds to forcibly power off. You probably weren't holding it long enough because the forced power off should work in pretty much any case. Hold for 12 seconds if you want to make sure.

Avast is known to cause some BSOD's though. I personally hate using that AV, but my personal taste doesn't have any influence unless there's proof to why I hate it that I could show you. Uninstall it for the time being, and install Microsoft Security Essentials.

Are you on another computer currently? You couldn't run Memtest at the time of posting this on the same computer. Black screen while still powered on could be numerous things ranging from graphics card problems, to even the most simplistic things like not having a good connector from the tower to your monitor. Make sure there's no breaks in the cable, and that it's plugged in both the tower and monitor securely. Let memtest pass for 6 tests, and provide me information on the test when that's done. I can't really help you until you've successfully completed the steps i've provided. Although extra information is always useful.

If you had an overheating issue, the GPU isn't the only thing that can overheat btw. There's also the CPU, but if there was an overheating issue, the most common results would cause your computer to completely power off or reboot.

 

[yuskey]

Yeah I'm using my laptop right now. Running memtest86 on one of my 4gig ddr3s its on the 4th pass and no errors. After 7 passes I was planning on switching ram cards and checking to see if the other one is good.

I know other things can overheat but all 6 cores for my cpu were at 29 and the second highest thing was my mobo running at 55. The connector is fine I've been using it with my laptop for months now and no such problem. I updated my drivers for my video card and what not.

 

[yuskey]

Alright so I ran memtest86 for both cards and I believe i have a mobo problem. I did my first ram card in slot 1 and it went 6 passes no problem when i tried my second card it wouldn't get past 20% on the first pass before it froze on 3 of the 4 slots, only on the first slot did it actually get through a pass. I tried the first ram card that went 6 passes on the other 3 slots and it works.

Would this be a cause for my problems? I'm confused on whether its the mobo or the ram that isnt working?

 

[Ace]

I tried the first ram card that went 6 passes on the other 3 slots and it works.

This would tell me that it's not your motherboard at all, but you have faulty RAM. If you had a Motherboard problem, none of the cards would work on a specific slot. This is selective.

If you're building this PC yourself do understand that RAM cards are static sensitive and should be handled with extreme care. I keep them in antistatic bags, and when seating them or carrying them around carry them by their edges only. What you wear, and what surface you're on make a difference too. (Common sense: Don't build or assemble it on carpet if you can avoid doing that.)

You need new RAM most likely for starters.

 

[yuskey]

Ah I see, I wasn't aware static had such a huge influence on RAM. I will contact the manufacturer tomorrow and see what they can do, I'm pretty sure I can still return it considering it has only been 10 days since I purchased it. I will update tomorrow after I've either exchanged it or talked to the manufacturer.

Thank you so much for your help so far though, I know a good amount about computers but mostly software related things lol but I really appreciate it and hope you can help me out if this keeps happening.

 

[Ace]

If you are talking about replacing the entire computer, you shouldn't have to, just replace the RAM, otherwise, see what they can do, but for parts like memory cards there's usually very limited warranty on them as soon as you open the packaging on the case/seal provided. You could get them to check the rest of your build as well to see if everything is in order, but that might come at a price.

 

[yuskey]

I'm sorry that's what I meant, I am going to attempt to exchange the RAM cards themselves, nothing else seems to be giving me any problems so far.

 

[zigzag3143]

Hey guys,

So just built my new pc about a week ago and everything seemed fine till 3 days ago. My monitor screen would randomly go black when i was playing a game and the tower would stay on. While trying to find a solution to that i keep getting BSODs. I uploaded the .dmp files within the post.

If anyone has any advice id greatly appreciate it, on both issues.

System Specs:
AMD Phenom II x6 1100T
Visiontek Radeon 6850
2x 4g ddr3 ram, corsair
850W psu
MSI 870a power fuzion mobo

These crashes were caused by a memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Ace]

It might not be a driver in this case, he's having issues with the RAM cards in specific. I believe he has a couple faulty ones: https://www.w7forums.com/107373-post7.html

 

[zigzag3143]

Thats why I had him run memtest and verifier.

 

[Ace]

I already had him run the memtest, just not the verifier

 

[zigzag3143]

I already had him run the memtest, just not the verifier

I saw you had told him to but didnt know what changes he had done in the intervening 2 weeks and he never told us the results,
its on the 4th pass and no errors.

I often find users are reluctant to run the full number of passes because of the time constraints and stop at a single pass.