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 After every startup. Works fine until the next day.

28 Apr 2013   #1

BSOD After every startup. Works fine until the next day.

I am so lost, I have tried everything I can to try to figure this problem out. I have switched out videocards, reset my CMOS, formatted and re installed Windows 7 but still have the same problem. Troubleshooting this problem has been really slow since each time I go to try something new I need to wait until the next day for it to happen. Any help is greatly appreciated. Thank you.

**Also I have noticed this thread is very similar to my problem
BSOD on start up, atikmdag.sys, dxgkrnl.sys, dxgmms1.sys

PROBLEM FIXED Replaced powerstrip and everything works fine.

My System SpecsSystem Spec
28 Apr 2013   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit


System Optimisers

Please remove the following software:
Start Menu\Programs\TuneUp Utilities 2013	Public:Start Menu\Programs\TuneUp Utilities 2013	Public
Start Menu\Programs\TuneUp Utilities 2013\All functions	Public:Start Menu\Programs\TuneUp Utilities 2013\All functions	Public
This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence. If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything. 10 Tips on How to Properly Maintain Your Computer

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

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)

AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
AMD OverDrive

(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.
The below is for information purposes only. Contains relevant information from the blue screen analysis:
Debug session time: Sun Apr 28 22:03:46.397 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042813-39686-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:02:04.583
Probably caused by : memory_corruption ( nt!MiInsertNode+20 )
BugCheck 1E, {ffffffffc0000005, fffff80002ef6100, 0, ffffffffffffffff}
Bugcheck code 0000001E
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ef6100, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiInsertNode+20
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
Debug session time: Sat Apr 27 22:08:14.361 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042713-32526-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:02:00.531
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BugCheck 4A, {77cd137a, 2, 0, fffff88007e14ca0}
Bugcheck code 0000004A
Arg1: 0000000077cd137a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88007e14ca0, 0
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_svchost.exe_nt!KiSystemServiceExit+245
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
Debug session time: Sat Apr 27 19:14:19.829 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042713-24445-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:03:18.000
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+173 )
BugCheck 3B, {c0000005, fffff80002f8fbae, fffff8800783eab0, 0}
Bugcheck code 0000003B
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f8fbae, Address of the instruction which caused the bugcheck
Arg3: fffff8800783eab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+173
BiosVersion = 080015 
BiosReleaseDate = 08/11/2010
SystemManufacturer = ECS
SystemProductName = A885GM-A2
My System SpecsSystem Spec
28 Apr 2013   #3

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

For troubleshooting a video card you could follow this:
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:

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.

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.

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.

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.

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

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.

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

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

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.

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.

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.

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.

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

29 Apr 2013   #4


Thank you for your help. I'll start running the tests later in the evening. Here are the .dmp from this morning if it helps. [note: I did not see this post prior to this bsod dump]

edit: Ran "System File Checker" end result - Windows Resource Protection did not find any integrity violations.

edit2: Ran Memory Test overnight for about 8 hours, No errors found
My System SpecsSystem Spec
29 Apr 2013   #5

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Trying rolling back to a older ATI driver as well.

Good luck,
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff3000b965158, 1, fffff8800737a6ff, 7}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+15e6ff )

Followup: MachineOwner

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

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.
Arg1: fffff3000b965158, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800737a6ff, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000007, (reserved)

Debugging Details:

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
GetUlongFromAddress: unable to read from fffff800030b11c0
 fffff3000b965158 Nonpaged pool

fffff880`0737a6ff 4a89442420      mov     qword ptr [rsp+r12+20h],rax





PROCESS_NAME:  csrss.exe


TRAP_FRAME:  fffff880027bf110 -- (.trap 0xfffff880027bf110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880027bf2d0 rbx=0000000000000000 rcx=fffffa80091a5f28
rdx=00000000fffffffe rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800737a6ff rsp=fffff880027bf2a0 rbp=fffff880027bf300
 r8=0000000000000000  r9=0000000000000000 r10=000000000000000f
r11=fffff900c00d6038 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff880`0737a6ff 4a89442420      mov     qword ptr [rsp+r12+20h],rax ss:0018:fffff880`027bf2c0=0100000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ef652b to fffff80002e79c00

fffff880`027befa8 fffff800`02ef652b : 00000000`00000050 fffff300`0b965158 00000000`00000001 fffff880`027bf110 : nt!KeBugCheckEx
fffff880`027befb0 fffff800`02e77d2e : 00000000`00000001 fffff300`0b965158 fffffa80`091a6900 fffff880`027bf3c0 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`027bf110 fffff880`0737a6ff : fffff880`027bf2d0 fffff880`07378887 fffff880`074828e0 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`027bf2a0 fffff880`027bf2d0 : fffff880`07378887 fffff880`074828e0 00000000`00000001 00000000`00000001 : atikmdag+0x15e6ff
fffff880`027bf2a8 fffff880`07378887 : fffff880`074828e0 00000000`00000001 00000000`00000001 fffff880`0000000f : 0xfffff880`027bf2d0
fffff880`027bf2b0 fffff880`074828e0 : 00000000`00000001 00000000`00000001 fffff880`0000000f 42100000`43020000 : atikmdag+0x15c887
fffff880`027bf2b8 00000000`00000001 : 00000000`00000001 fffff880`0000000f 42100000`43020000 42820000`44ecc000 : atikmdag+0x2668e0
fffff880`027bf2c0 00000000`00000001 : fffff880`0000000f 42100000`43020000 42820000`44ecc000 3f0f92c6`3c088889 : 0x1
fffff880`027bf2c8 fffff880`0000000f : 42100000`43020000 42820000`44ecc000 3f0f92c6`3c088889 3f15c28f`3f6d5555 : 0x1
fffff880`027bf2d0 42100000`43020000 : 42820000`44ecc000 3f0f92c6`3c088889 3f15c28f`3f6d5555 00000000`00000000 : 0xfffff880`0000000f
fffff880`027bf2d8 42820000`44ecc000 : 3f0f92c6`3c088889 3f15c28f`3f6d5555 00000000`00000000 00000000`00000000 : 0x42100000`43020000
fffff880`027bf2e0 3f0f92c6`3c088889 : 3f15c28f`3f6d5555 00000000`00000000 00000000`00000000 fffff880`027bf340 : 0x42820000`44ecc000
fffff880`027bf2e8 3f15c28f`3f6d5555 : 00000000`00000000 00000000`00000000 fffff880`027bf340 fffff880`07379bc1 : 0x3f0f92c6`3c088889
fffff880`027bf2f0 00000000`00000000 : 00000000`00000000 fffff880`027bf340 fffff880`07379bc1 fffff880`027bf3c0 : 0x3f15c28f`3f6d5555


fffff880`0737a6ff 4a89442420      mov     qword ptr [rsp+r12+20h],rax


SYMBOL_NAME:  atikmdag+15e6ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys


FAILURE_BUCKET_ID:  X64_0x50_atikmdag+15e6ff

BUCKET_ID:  X64_0x50_atikmdag+15e6ff

Followup: MachineOwner

1: kd> lmvm atikmdag
start             end                 module name
fffff880`0721c000 fffff880`07d8f000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Mar 29 08:27:04 2013 (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
30 Apr 2013   #6

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

If you have an update/progress please post a new reply. Do not edit your previous post as I will not be notified of that.
My System SpecsSystem Spec
01 May 2013   #7


I have not had the chance to run the hardrive tests however I did run the command "chkdsk /r" a week back and came up with nothing. Something unusual today though. I turned my pc off from 6:20am to 1:00pm, the usual amount of time for a bluescreen to appear after startup, and did not have a bsod. 2:16 pm and still no bsod. It's strange since my bsod's have been very consistent and this breaks the chain of bsods. Maybe it's fixed? Probably a fluke but i'll let you know.
My System SpecsSystem Spec
01 May 2013   #8

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

I'll wait to hear from you.
My System SpecsSystem Spec
02 May 2013   #9


No BSOD today so far, that's 2 days in a row. Thank you for your help! If i have any in the next few days though i'll reply back to this thread.
My System SpecsSystem Spec
02 May 2013   #10

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

Quote   Quote: Originally Posted by thatsmywhitemam View Post
No BSOD today so far, that's 2 days in a row. Thank you for your help! If i have any in the next few days though i'll reply back to this thread.
Best wishes! :)
My System SpecsSystem Spec

 BSOD After every startup. Works fine until the next day.

Thread Tools

Similar help and support threads
Thread Forum
BSOD shortly after Power On - All works fine after restart
Hi guys, I will try to be as fast as possible while giving all relevant information: - Had this pc for 5 years, and it always worked fine. - CPU Temperatures are around 38 idle - ~72 full load- Recently updated Win 7 to Win 10, then the trouble began to happen: Blue screen each day at the...
BSOD Help and Support
BSOD/freezes a few times, then it works fine for a few hours
Hello there. :) I'm looking for help. I've had some problems with my PC this month and I can't really make it work properly. It freezes/crashes/has a BSOD randomly, mostly a few minutes after it starts. It seems like it isn't caused by overheating since these errors appear independently of stress...
BSOD Help and Support
BSOD GTX 260, works fine in safe mode.
Hi!! I have a BFG GTX 260 video card, when I turn it on in normal mode it displays BSOD but when I turn it on in safe mode it works fine, my motherboard (MSI K9N2 Diamond) has 3 PCI-Ex slots I tried all of them but it still crashes. I also uninstalled and installed the video drivers but no luck,...
BSOD Help and Support
BSOD on formatting 3TB HD connected with e-Sata / USB works fine
Got a new 3TB HD today which I use as external drive. When I connect it with USB it seems to work fine. Windows sees it and I can format it. When I conntect it with e-Sata, Windows says the Drive needs to be reformatted. As soon as I start a Quick format, Windows gives me an BSOD That's a...
BSOD Help and Support
BSOD 4gb ram - Works fine with 2gb
4gb ram bsod on startup or a few minutes later. I tried every combination slots and sticks have no problems. (2 slots, 2x 2gb sticks) ---Additionally, in the little time i had on 4gb ram boot i saw that only 2,94 gb memory is usable. Is Windows 7 . . . - x86 (32-bit) or x64 ?
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 01:04.
Twitter Facebook Google+