Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Full screen Youtube videos and sometimes in games.

02 Jan 2013   #1
itzjt90

Windows 7 64bit
 
 
BSOD Full screen Youtube videos and sometimes in games.

When I first built my pc I watched a video in fullscreen. Got the BSOD.....updated drivers. Now I just dont watch fullscreen videos. I have the Radeon HD 7950 and am using the beta drivers. I was also playing the game Arma 2 (DayZ mod) also I had a map opened on googlechrome in the background and got the BSOD. this was before I installed the beta drivers. I was running the 12.10 drivers at the time. Now I installed the beta and haven't played any games yet. But I wanted to see what caused it. Blue Screen viewer tells me it was caused by the driver ntoskrnl.exe, caused by address ntoskrnl.exe+ 7efc0


My System SpecsSystem Spec
.
02 Jan 2013   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Welcome

Both .dmp files come with Memory_Management 1a

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

BSOD Report
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009c9f30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80009c9f30
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Arma2OA.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef4b50 to fffff80002e88fc0

STACK_TEXT:  
fffff880`0254f6e8 fffff800`02ef4b50 : 00000000`0000001a 00000000`00041790 fffffa80`009c9f30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0254f6f0 fffff800`02ebbb69 : fffffa80`00000000 00000000`403fffff fffff880`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0254f8b0 fffff800`0319be21 : fffffa80`077c1550 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0254f9d0 fffff800`0319c223 : 00000000`00000000 00000000`3fff0000 fffffa80`00000001 00000000`00000a01 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0254fa90 fffff800`02e88253 : fffffa80`07760b50 fffff880`0254fb60 fffffa80`0d2c6630 00000000`0000003f : nt!NtUnmapViewOfSection+0x5f
fffff880`0254fae0 00000000`76f715ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0c02e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f715ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35054
fffff800`02ef4b50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35054

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

Followup: MachineOwner
---------
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009c9f30, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80009c9f30
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f44b50 to fffff80002ed8fc0

STACK_TEXT:  
fffff880`0ada90b8 fffff800`02f44b50 : 00000000`0000001a 00000000`00041790 fffffa80`009c9f30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0ada90c0 fffff800`02ec581f : fffffa80`00000000 00000000`0a45ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0ada9280 fffff800`02ed8253 : ffffffff`ffffffff fffff880`0ada9550 fffff880`0ada95b8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0ada9380 fffff800`02ed4810 : fffff960`000e7110 00000000`00000001 00000000`00000000 fffff900`c32572e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0ada9518 fffff960`000e7110 : 00000000`00000001 00000000`00000000 fffff900`c32572e0 00000000`00000001 : nt!KiServiceLinkage
fffff880`0ada9520 fffff960`000ef381 : 00000000`00000000 fffff880`00000001 fffff900`c32572e0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0ada9670 fffff960`000e6940 : 00000000`00000e70 fffff880`0ada9a00 fffff900`c3c5abf0 fffff880`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`0ada96d0 fffff960`000e6077 : 00000000`00000000 fffff880`0ada9ae0 fffffa80`071beb50 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`0ada9750 fffff800`031aa5c1 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`071beb00 : win32k!W32pProcessCallout+0x6b
fffff880`0ada9780 fffff800`0318db7d : 00000000`c0000005 00000000`00000001 00000000`78457300 fffffa80`06da3b50 : nt!PspExitThread+0x4d1
fffff880`0ada9880 fffff800`02ecbb3a : fffffa80`0c77e9c0 fffffa80`074382e0 00000000`00000000 fffffa80`0c77e8f0 : nt!PsExitSpecialApc+0x1d
fffff880`0ada98b0 fffff800`02ecbe80 : 00000000`00000000 fffff880`0ada9930 fffff800`0318daf0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0ada9930 fffff800`02ed82f7 : fffffa80`071beb50 00000000`0218ecb8 fffff880`0ada9a88 00000000`010fd628 : nt!KiInitiateUserApc+0x70
fffff880`0ada9a70 00000000`74712e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0218ec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74712e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`000e7110 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`000e72c5)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50ad9b54

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

Followup: MachineOwner
---------
My System SpecsSystem Spec
03 Jan 2013   #3
itzjt90

Windows 7 64bit
 
 

Quote   Quote: Originally Posted by koolkat77 View Post
Welcome

Both .dmp files come with Memory_Management 1a

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

BSOD Report
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009c9f30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80009c9f30
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Arma2OA.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef4b50 to fffff80002e88fc0

STACK_TEXT:  
fffff880`0254f6e8 fffff800`02ef4b50 : 00000000`0000001a 00000000`00041790 fffffa80`009c9f30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0254f6f0 fffff800`02ebbb69 : fffffa80`00000000 00000000`403fffff fffff880`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0254f8b0 fffff800`0319be21 : fffffa80`077c1550 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0254f9d0 fffff800`0319c223 : 00000000`00000000 00000000`3fff0000 fffffa80`00000001 00000000`00000a01 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0254fa90 fffff800`02e88253 : fffffa80`07760b50 fffff880`0254fb60 fffffa80`0d2c6630 00000000`0000003f : nt!NtUnmapViewOfSection+0x5f
fffff880`0254fae0 00000000`76f715ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0c02e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f715ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35054
fffff800`02ef4b50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35054

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054

Followup: MachineOwner
---------
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80009c9f30, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80009c9f30
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f44b50 to fffff80002ed8fc0

STACK_TEXT:  
fffff880`0ada90b8 fffff800`02f44b50 : 00000000`0000001a 00000000`00041790 fffffa80`009c9f30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0ada90c0 fffff800`02ec581f : fffffa80`00000000 00000000`0a45ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0ada9280 fffff800`02ed8253 : ffffffff`ffffffff fffff880`0ada9550 fffff880`0ada95b8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0ada9380 fffff800`02ed4810 : fffff960`000e7110 00000000`00000001 00000000`00000000 fffff900`c32572e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0ada9518 fffff960`000e7110 : 00000000`00000001 00000000`00000000 fffff900`c32572e0 00000000`00000001 : nt!KiServiceLinkage
fffff880`0ada9520 fffff960`000ef381 : 00000000`00000000 fffff880`00000001 fffff900`c32572e0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0ada9670 fffff960`000e6940 : 00000000`00000e70 fffff880`0ada9a00 fffff900`c3c5abf0 fffff880`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`0ada96d0 fffff960`000e6077 : 00000000`00000000 fffff880`0ada9ae0 fffffa80`071beb50 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`0ada9750 fffff800`031aa5c1 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`071beb00 : win32k!W32pProcessCallout+0x6b
fffff880`0ada9780 fffff800`0318db7d : 00000000`c0000005 00000000`00000001 00000000`78457300 fffffa80`06da3b50 : nt!PspExitThread+0x4d1
fffff880`0ada9880 fffff800`02ecbb3a : fffffa80`0c77e9c0 fffffa80`074382e0 00000000`00000000 fffffa80`0c77e8f0 : nt!PsExitSpecialApc+0x1d
fffff880`0ada98b0 fffff800`02ecbe80 : 00000000`00000000 fffff880`0ada9930 fffff800`0318daf0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0ada9930 fffff800`02ed82f7 : fffffa80`071beb50 00000000`0218ecb8 fffff880`0ada9a88 00000000`010fd628 : nt!KiInitiateUserApc+0x70
fffff880`0ada9a70 00000000`74712e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0218ec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74712e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`000e7110 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`000e72c5)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50ad9b54

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

Followup: MachineOwner
---------
Just ran the memtest86 Memtest86+ - Advanced Memory Diagnostic Tool and Tested both sticks. Errors came up fast. like 60 something errors. Tested one of the sticks. Two passes, so I stopped and tested out the other one. The 2nd stick came up with 60 something errors. Tried it in different slots, with one ram and with both. Asking newegg for a RMA. Checked the volts 1.5. It was on auto. And I feel if ram cant run on auto than I should replace it.
My System SpecsSystem Spec
.

03 Jan 2013   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Quote   Quote: Originally Posted by itzjt90 View Post
Memtest86+ - Advanced Memory Diagnostic Tool[/url] and Tested both sticks. Errors came up fast. like 60 something errors. Tested one of the sticks. Two passes, so I stopped and tested out the other one. The 2nd stick came up with 60 something errors. Tried it in different slots, with one ram and with both. Asking newegg for a RMA. Checked the volts 1.5. It was on auto. And I feel if ram cant run on auto than I should replace it.
You're right,
Let us know how it went.
My System SpecsSystem Spec
Reply

 BSOD Full screen Youtube videos and sometimes in games.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Black screen when watching videos full screen and exiting games
I've tried updating the drivers, making sure nothing was overclocked, ram memtest and furmark. memtest found no errors, same with chkdsk and it didn't crash in furmark my average temp of gpu is 31 degrees Celsius. It plays sound for a few seconds afterward but then becomes unresponsive to the...
General Discussion
BSOD when exiting full screen videos, or games. 0x0000003B
Hi! I've been navigating the forums for a while now but I finally found myself in the need of creating a thread. I recently made a fresh install of windows on my PC, but I've noticed that I keep getting BSOD's every now and then when I exit a game or a video in full screen. I't not always but it's...
BSOD Help and Support
BSOD randomly from Full Screen Games or Youtube Videos.
Hey, my computer has been blue screening for quite sometime now, if I were to estimate I would say around 8 months and I get 1-2 blue screen every month I would have to say. I have formatted my computer and re-installed windows around 1-2 months ago to check if it would fix the problem but to no...
BSOD Help and Support
Videos and Games are not playing in Full Screen
Hi, I'm tired by searching a solutions for how to play videos and games in full screen I have bought a new lenovo g580 Os window 7 the problem is any kind of videos and games are not opeing in Full Screen, It's has Intel HD 4000 Graphics Please guide me
Music, Pictures & Video
Full screen videos and games lagging
I'm having a serious problem when trying to watch videos in full scream. When in full screen, the videos get slow, lagging in various scenes, sometimes with cuts in the audio too. My config is Sempron 2600+, 1.5gb ram and Geforce 5500 256MB 128 bits. Display 22", 1680x1050 resolution. I'm using...
Performance & Maintenance
Full Screen Videos Laggy (youtube, hulu, etc.)
I'm running a laptop with an ati x1600 (using windows update driver), videos running in full screen are always choppy. Anyone else have this issue?
Graphic Cards


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 03:46.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App