BSOD Windows 7 after black boxes on screen

R

Rutger

Member
Joined
Sep 8, 2014
Posts
12
Dear community,

I'm facing this problem for a while now and I believe I updated all drivers and such. I read some minidumps, event logs et cetera but I am not a computer engineer; it's all scary to me.

This problem only occures when I am gaming, or atleast thus far. Sometimes I can play for a hour (when lucky; two) and sometimes even for just 10 minutes. Before the BSOD I see black boxes on the screen (little boxes, I can still see the game but it's filled with these graphics) and sometimes the game graphics go ape.
This lasts for about 30 seconds and then the BSOD happens.

Weird thing is; yesterday and today I've had the same situation as above, but without BSOD.. The computer simply restarted or the monitor turned black.

I've attached the perfmon log and the output folder as described. I hope you wizards can help me out here.

Best regards,

Rutger.

OS - Windows 7
· 64x
· Windows 7
· I purchased the Windows 7 copy and installed it manually
· About 5 Years (late 2009)
· About 4 months (I reinstalled the computer a couple of months ago)

· CPU - 3.21Ghz AMD Phenom II x4 955 Processor
· Video Card - No idea. I believe it was Radeon (?)
· MotherBoard - Asus
· Power Supply - No clue, it's all inside this big black box (the computer itself).

· System Manufacturer - My brother build this computer some years back
· Exact model number - ^ none.

· Desktop.
 
We have various bugchecks which I will go through.

Code: 
BugCheck 7E, {ffffffffc0000005, fffff88008130e89, fffff8800217d868, fffff8800217d0c0}

First off we have a 0x7E meaning a system thread generated an exception which was unable to be handled.
More specifically it generated an access violation by referencing memory which the CPU couldn't understand.

Code: 
OVERLAPPED_MODULE: Address regions for 'CLASSPNP' and 'Unknown_Module_00000000`00000000' overlap

We can see an unknown module and classpnp were overlapping each other, this is due to bad instruction pointers being used so something wrote to an address already being used.

Code: 
0: kd> [COLOR="#008000"].cxr 0xfffff8800217d0c0;r[/COLOR]
Unable to read context, Win32 error 0n30
rax=0000000000026522 rbx=0000000000000000 rcx=fffffa800575d950
rdx=fffffa80054529a8 rsi=fffff80002ff9e80 rdi=0000000000000001
rip=fffff88002da97f2 rsp=fffff80000b9cc98 rbp=0000000000000000
 r8=0000000000000000  r9=000000002e3e1b97 r10=0000000000021eac
r11=fffff8800d681800 r12=fffffa8005452980 r13=fffffa8005a77500
r14=fffffa8005452900 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=0000  es=0000  fs=0000  gs=0000             efl=00000246
fffff880`02da97f2 ??              ???

The context wasn't saved properly so we'll not get much out of that.

Code: 
fffff800`00b9cc98 fffff800`02e87709 : 00000000`002fe6b0 fffffa80`05a775f8 fffff800`03007cc0 00000000`00000001 : 0xfffff880`02da97f2
fffff800`00b9cca0 fffff800`02e7689c : fffff800`02ff9e80 fffff800`00000000 00000000`00000000 fffff880`01419800 : [COLOR="#800080"]nt!PoIdle+0x52a[/COLOR]
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR="#800080"]nt!KiIdleLoop+0x2c[/COLOR]

All we have in the callstack is the processor waking up from being idle and calling a user mode function, that is all that was saved so we won't get much without a Full memory dump for this bugcheck.



Code: 
BugCheck [COLOR="#FF0000"]10E[/COLOR], {1f, fffff8a00d159660, 0, 12c412}

Next we have a video memory management internal error which is caused by a buggy display driver, this bugcheck we have is an unknown 0x10E so our parameters don't contain any useful information.

Code: 
fffff880`09dfb878 fffff880`03f6822f : 00000000`0000010e 00000000`0000001f fffff8a0`0d159660 00000000`00000000 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR]
fffff880`09dfb880 fffff880`080211d0 : fffff8a0`0e9bd830 fffff8a0`0d159660 00000000`0012c412 00000000`00000000 : [COLOR="#FF0000"]watchdog!WdLogEvent5+0x11b[/COLOR]
fffff880`09dfb8d0 fffff880`0801e9d3 : 00000000`00000000 fffffa80`03bf00a8 00000000`00000c3a fffffa80`06a37200 : [COLOR="#FF0000"]dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148[/COLOR]
fffff880`09dfb910 fffff880`080387d9 : 00000000`00000000 fffff8a0`03040260 fffffa80`00000000 fffffa80`045d9cb0 : [COLOR="#FF0000"]dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b[/COLOR]
fffff880`09dfbae0 fffff880`08038514 : fffff880`009ebf40 fffff880`08037f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`09dfbcd0 fffff880`08038012 : 00000000`00000000 fffffa80`0412aad0 00000000`00000080 fffffa80`06955010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`09dfbd00 fffff800`0311873a : 00000000`043e43d2 fffffa80`065b4b50 fffffa80`039d3040 fffffa80`065b4b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`09dfbd40 fffff800`02e6d8e6 : fffff880`009e7180 fffffa80`065b4b50 fffff880`009f1fc0 4330526d`354a7076 : nt!PspSystemThreadStartup+0x5a
fffff880`09dfbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

We can see some directx routines with a dma buffer being intiated and memory being referenced for allocation.
The watchdog timer is initiated as something has gone wrong and then we bugcheck.



We also see a similar bugcheck error.

Code: 
BugCheck 50, {[COLOR="#FF0000"]ffffffffffffffe8[/COLOR], 0, fffff88006f72c34, 0}

We have a page fault in nonpaged area which means invalid memory was referenced, this isn't allowed at all so we bugcheck.

Code: 
fffff880`0ac8e1c8 fffff800`02ef6bf0 : 00000000`00000050 ffffffff`ffffffe8 00000000`00000000 fffff880`0ac8e330 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR]
fffff880`0ac8e1d0 fffff800`02e76cee : 00000000`00000000 ffffffff`ffffffe8 00000000`00000000 fffff8a0`0e666860 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0ac8e330 fffff880`06f72c34 : fffff8a0`0e666860 fffff880`06f40ee3 00000000`00000002 00000000`00000000 : [COLOR="#FF0000"]nt!KiPageFault+0x16e[/COLOR]
fffff880`0ac8e4c0 fffff880`06f70767 : fffffa80`067fd000 00000000`633a1000 fffff8a0`0ec806f0 ffffffff`ffffffe0 : [COLOR="#FF0000"]dxgmms1!VIDMM_LINEAR_POOL::Free+0x174[/COLOR]
fffff880`0ac8e510 fffff880`06f706c6 : 00000000`00000016 fffffa80`03eb1b30 fffffa80`06db1c00 fffff800`02e7ba8a : [COLOR="#FF0000"]dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0x8b[/COLOR]
fffff880`0ac8e540 fffff880`06f5bc93 : 00000000`00000002 fffff8a0`039fdf80 00000000`00000001 00000000`00000000 : [COLOR="#FF0000"]dxgmms1!VIDMM_PROCESS_HEAP::Free+0x13a[/COLOR]
fffff880`0ac8e570 fffff880`06f56637 : fffffa80`04218940 00000000`00000001 fffff8a0`10278e50 00000000`00000001 : [COLOR="#FF0000"]dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b[/COLOR]
fffff880`0ac8e620 fffff880`06f3cecc : fffffa80`00000000 fffffa80`00000000 fffffa80`00000000 00000000`00000000 : [COLOR="#FF0000"]dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b[/COLOR]
fffff880`0ac8e6f0 fffff880`06e7dccc : 00000000`00000000 fffff8a0`03d67000 fffff8a0`03d67000 00000000`00000001 : [COLOR="#FF0000"]dxgmms1!VidMmCloseAllocation+0x44[/COLOR]
fffff880`0ac8e720 fffff880`06e7d65f : fffff8a0`03d67000 fffff8a0`03d68300 fffff8a0`00000000 00000000`0000001b : [COLOR="#FF0000"]dxgkrnl!DXGDEVICE::DestroyAllocations+0x248[/COLOR]
fffff880`0ac8e810 fffff880`06e7d8e1 : 00000000`00000003 fffff8a0`03d67000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0ac8e860 fffff880`06e81aec : 00000000`00000000 fffff880`0ac8eca0 fffff8a0`1013e720 fffff880`06e483af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0ac8e8b0 fffff880`06e84285 : fffff8a0`03d67000 fffff880`0ac8e990 00000000`4b677800 00000000`00000701 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x44c
fffff880`0ac8e940 fffff960`001e1c0a : 00000000`00000000 fffffa80`03ed3060 00000000`00000020 00000000`7432616c : dxgkrnl!DxgkDestroyAllocation+0xa9d
fffff880`0ac8ebf0 fffff800`02e77e53 : fffffa80`03ed3060 00000000`000004a4 00000000`00000000 fffffa80`03dd68f0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0ac8ec20 00000000`7434141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`11cee3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7434141a

We can see directx is removing allocations which leads to a page fault so they used a bad instruction pointer and tried to terminate the wrong allocation.

Code: 
2: kd> [COLOR="#008000"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`07204000 fffff880`07db7000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="#FF0000"]Tue Apr 30 03:07:09 2013[/COLOR] (517F274D)
    CheckSum:         00B6397D
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card display driver needs updating.

Go to start and type in dxdiag then open up the application.
Under the display tab it will tell you information about your graphics card, go to the AMD website, find that card and download the latest driver.
 
Dear Jared,

Thanks for your swift reply.

I've downloaded the latest driver and installed it. Atleast; that's my best guess.

Do you know how to check if I have the latest driver installed?
 
Go back to dxdiag and it should say a driver timestamp under the display tab.
 
I installed the driver (newest according to AMD's website and autodetect application) twice now. The timestamp on DxDiag still says "4/30/2013".
 
Nah not really. My artifacts are black and bigger (more like bigger squares), and they stay at the same position. Also they are with many!

I have tried to find them on the internet but without any result.

Worth noting: I am also still able to play with the artifacts on the screen. It's just a "warning" that the BSOD is coming or something.
 
In that case I would say your GPU is failing, do you have another on you can test?

The temperatures are important as well, is your computer overheating?
 
I have no spare GPU or something. My computer doesnt feel warmer than usual.

edit: I downloaed GPU Temp.
Currently the temp. of my GPU core is 82 Degrees celcius. I am not gaming, I have firefox running but no heavy applications such as Games.
 
Wow... no wonder your system crashes. Please DON'T play games, clean your graphics card as soon as possible.
 
b2rdark said:
Wow... no wonder your system crashes. Please DON'T play games, clean your graphics card as soon as possible.
Click to expand...

I've now cleaned my computer with a vacuum cleaner. Lots of dust inside. I even unclipped the graphic card (with cool device which was from Sapphire) and removed the dust.
Now the GPU core is at 68C while idle. Is this a more common temperature?
 
I've read that everything under 70C is considered as "cool". Anyways, if 68 is still too hot, how can I decrease this? I do see the fan speed is at 51% (TechPowerUp GPU application). Is my fan broken or something?
 
You should be able to change that via the catalyst control center that you installed with your display driver.

68C isn't too hot under stress but idle it is, think about how hot it will go when you game if the idle temp is 68.
 
My brother's computer has the same hardware as I do (also same age). He doesn't have this problem (his temperature exceeds even 100C sometimes).

I just played a game and had another blue screen, I managed to get the message of it: system_service_exception.
techincal information: 0x0000003B
 
Upload the dump file.
Just because your brother's computer is the same hardware doesn't mean your should act the same.
It may reach 100C but it won't stay in good condition for long unless he brings those temperatures down. His PC will degrade from heat in no time.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top