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 while playing nearly any game, common error 0x000000d1 :(

15 Jun 2013   #1
samosh19

Windows 7 Ultimate
 
 
BSOD while playing nearly any game, common error 0x000000d1 :(

hi people.
i get a BSOD playing nearly any game that has a considerable strain on my computer (i think).
but the odd thing is that i can Age of Empires II forever, while when i play minecraft, it just randomly crashes without warning. i have ran chkdsk multiple times, to no avail. i have no clue what is going on. the computer runs perfectly fine while i am just browsing the web (YouTube, Facebook, etc) but when i launch a game, it lasts for bout 5 minutes, then crashes. League of Legends crashes from 5-10 minutes of gameplay. Minecraft on the other hand plays for bout 20 mins then bluescreens. for the sake of seeing the limits of the computer, i even played runescape and it could not even run that without crashing. the ONLY game that works fine is, like i said AOE 2.
the most common code from the blue screen is 0x000000d1. there have been other codes but i only remember that code as it is the most common occurrence.
No clue what's going on!
thanks in advance
P.S my minidump files are attached below


My System SpecsSystem Spec
.
15 Jun 2013   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Hi and welcome to Seven forums samosh19.

Your errors are pretty straight forward: caused by Avast!

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {18, 2, 0, fffff880040335f5}

*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
Probably caused by : aswTdi.SYS ( aswTdi+45f5 )

Followup: MachineOwner
---------
As a result I would recommend uninstallation of Avast! and replace with Microsoft Security Essentials to see if it provides more stability.
Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

information   Information
  • Do not start the free trial of MalwareBytes, unselect that option when prompted.


  • Update and make full scans with both separately.

AMD OverDrive
Code:
AODDriver2.sys              Thu Apr  5 15:23:37 2012 (4F7D6499)
(AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems. Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program. Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item. Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect. Sometimes the driver remains and continues to cause BSOD's.

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Stress Test

Hardware - Stress Test With Prime95 - Test your Hardware for Stability and Heat Problems with Prime95
CPU - Stress Test Using IntelBurnTest - Test your CPU Stability with IntelBurnTest
Video Card - Stress Test with Furmark - Stress Test a Video Card with Furmark
Monitor temperature of the system during the tests - Speccy - System Information - Free Download
My System SpecsSystem Spec
16 Jun 2013   #3
samosh19

Windows 7 Ultimate
 
 

ok i have done a lot of the things as u mentioned, the game time has increased massively. the blue screening on League of Legends have stopped, but now it freezes without warning. i have come across a new blue screen when i have tried to play chivarly medieval warfare, the stop code of 0x000007E came up. no idea what that is. i put in the new dump files, if that helps.
thank you
My System SpecsSystem Spec
.

16 Jun 2013   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Follow steps in the guide by Capt Jack Sparrow - Bug Check 0x116: VIDEO_TDR_ERROR Troubleshooting Tips | Captain Debugger

Quote   Quote: Originally Posted by TVeblen View Post
What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

A couple of things jump out immediately. Your specs say you have 5GB of RAM, an odd number. That suggests that you added some RAM at some point. Mismatched or failing RAM modules can cause TDRs. You might want to test those sticks one at a time in Slot 1 before anything else. RAM problems can explain some of your other issues too.

Looking at some of your other posts I see you are running dual monitors also. This could be exposing a defect in your 9500GT that is triggering the TDRs. You should test with only one monitor attached to see if this is the case.

You are running lots of stuff on that box, so I would be as deliberate as possible in doing the diagnostic work.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:
  • Poor Cooling
  • Problems with the power supply
  • Overclocking Issues
  • Bad System memory or incorrect memory timings
  • Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using the generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: Installing and updating drivers in 7

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick and testing, and then switch it out for the next stick, etc.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor perforning card in the W7 enviroment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check for and install an updated BIOS, particularly if it says the newer BIOS corrects memory errors or bug fixes. You could also try loading the BIOS defaults.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
Test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
27116: ATIKMDAG has stopped responding error message
My System SpecsSystem Spec
16 Jun 2013   #5
samosh19

Windows 7 Ultimate
 
 

ok i have vanilla drivers. now im just confused. i just got another bluescreen when trying to play lol after putting up my plain drivers. and i got the BSOD STOP code of 0x000000A. everytime i fix a fix screen, another one occurs. am i causing some sort of catalyst in my damn computer? im so lost. i feel like this error will not stop :'(
My System SpecsSystem Spec
16 Jun 2013   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

It does not look like you have the latest drivers:

lmvm atikmdag
start end module name
fffff880`048ab000 fffff880`05362000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: atikmdag.sys
Image name: atikmdag.sys
Timestamp: Sat May 05 01:19:48 2012 (4FA42BD4)
CheckSum: 00A5B71A
ImageSize: 00AB7000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffc3ffff, 2, 1, fffff80002e87f5d}

Probably caused by : ntkrnlmp.exe ( nt!KiSignalSynchronizationObject+15d )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffc3ffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e87f5d, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b9100
GetUlongFromAddress: unable to read from fffff800030b91c0
 ffffffffffc3ffff 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+15d
fffff800`02e87f5d 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  League of Lege

TRAP_FRAME:  fffff880085fb830 -- (.trap 0xfffff880085fb830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffc3ffff rbx=0000000000000000 rcx=ffffffffffd2ffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e87f5d rsp=fffff880085fb9c0 rbp=fffffa80096b7b50
 r8=0000000000000000  r9=0000000000000008 r10=fffffa80069fb720
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiSignalSynchronizationObject+0x15d:
fffff800`02e87f5d 488908          mov     qword ptr [rax],rcx ds:ffffffff`ffc3ffff=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e811a9 to fffff80002e81c00

STACK_TEXT:  
fffff880`085fb6e8 fffff800`02e811a9 : 00000000`0000000a ffffffff`ffc3ffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`085fb6f0 fffff800`02e7fe20 : 0cd204c1`12390c22 047df908`0768fd49 09a50228`0501fa1a fffffa80`091309f8 : nt!KiBugCheckDispatch+0x69
fffff880`085fb830 fffff800`02e87f5d : 00000000`cd6736af fffff800`02e8898f 00000000`000004f4 ffffc05f`7f26341f : nt!KiPageFault+0x260
fffff880`085fb9c0 fffff800`02e86246 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`7ef08001 : nt!KiSignalSynchronizationObject+0x15d
fffff880`085fba10 fffff800`0316b9f0 : fffff880`00000000 00000000`00000001 fffffa80`069fb700 fffff880`085fba01 : nt!KeSetEvent+0x106
fffff880`085fba80 fffff800`02e80e93 : fffffa80`0956cb50 00000000`000004f4 fffff880`00000000 fffffa80`091309f0 : nt!NtSetEvent+0x90
fffff880`085fbae0 00000000`73b22e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0f45f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73b22e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSignalSynchronizationObject+15d
fffff800`02e87f5d 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiSignalSynchronizationObject+15d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0xA_nt!KiSignalSynchronizationObject+15d

BUCKET_ID:  X64_0xA_nt!KiSignalSynchronizationObject+15d

Followup: MachineOwner
---------
Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

Note   Note
Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

Tip   Tip
Do this test overnight.


Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition
  • For how to upload a screenshot or file, read here
Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): How to Run Disk Check in Windows 7
My System SpecsSystem Spec
17 Jun 2013   #7
samosh19

Windows 7 Ultimate
 
 

ok i have ran memtest overnight. the results were clean. apparently no problems were recorded. i can low demand game such as AOE 2 but now, League of Legends will not even launch. i have had another blue screen when trying to see any improvements in FurMark, and it BSOD with STOP code of 0x000000E1. is this a lost cause?
My System SpecsSystem Spec
17 Jun 2013   #8
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Have you run SFC scannow as suggested earlier?
Virus check

Scan your system with the following:

Microsoft Safety Scanner - Microsoft Safety Scanner - System Requirements

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Run the scanners listed here: How to Scan Suspicious Files using Online Scanners

As well as Windows Defender Offline: How to Use Windows Defender Offline
My System SpecsSystem Spec
17 Jun 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If occurred while using Furmark?

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

If not overclocked, Try to reduce the system's heat. Leave one side of the computer open. Apply a fan from outside and try to run furmark again. A BSOD during furmark indicates that the GPU is failing. At least plan to borrow another GPU from somebody else and apply it to observe the situation.

A lot of storage related failures are observed in the crash dump. It might be a failing storage, or backdated controllers, or an antivirus behaving ambitious or a virus.
Scan the system for possible virus infection with the following programs.
Do some Disc checks.
  1. Re-seat the sata and power.
  2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  3. Seatool for dos: SeaTools | Seagate download
    Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
  4. Post a screenshot of your HDD using CrystalDiskInfo - Software - Crystal Dew World
The AMD SATA (AHCI) Controller is very old.
Code:
fffff880`00e00000 fffff880`00e18000   amd_sata   (deferred)             
    Image path: amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Tue Dec 13 02:22:00 2011 (4EE66970)
    CheckSum:         000173E9
    ImageSize:        00018000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the AMD Chipset driver (which includes this driver) from AMD Chipset Drivers

Let us know the results.
My System SpecsSystem Spec
Reply

 BSOD while playing nearly any game, common error 0x000000d1 :(




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD when launching a game, error 0x000000d1
A couple of weeks ago i got the first blue screen of death on this pc. I don't remember what i was doing, but since then i kept track of the events of this BSOD. I noticed it can happen when im on my browser and then as i launch a game (ex. Dead island/ Battlefield ) i will hear the game sound...
BSOD Help and Support
BSOD playing War Thunder, error 0x000000d1
I previously got help from this forum earlier, by a fellow named Golden, but I am still having bluescreen issues. I have updated my graphics drivers to the latest, updated my BIOS, anything I could think of, but I am still having bluescreen issues. Golden advised me to do something in my other...
BSOD Help and Support
BSOD playing BF3 error 0x000000D1 & more
I've been getting BSODs while under load lately, and I'm not sure what the direct cause is. I've installed every GPU driver made for my card, yet it doesn't matter. I even just did a clean install of Windows a couple weeks ago. It usually happens while rendering in Inventor, or BF3, or just under...
BSOD Help and Support
BSOD while playing GPU intensive programs, Common 0xC000000D error
This has begun happening roughly 1-2 weeks ago, prior to this the system ran flawlessly (never had a BSOD) The strangest thing is that the BSOD started happening right after a windows update, and an install of MSE (never had it before this) I have tried many different tests and fixes to try...
BSOD Help and Support
BSOD playing Battlefield 3,error 0x000000d1
So was playing BF3 and then it got BSOD... I got the error 0x000000d1 . Any idea of the problem? I was gonna put my .dmp file but it was 823mb :/
BSOD Help and Support


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 05:54.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App