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 0x3B and 0x1E

29 Dec 2013   #1
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 
BSOD 0x3B and 0x1E

Seems it doesn't matter what I am doing, I will get a BSOD after the computer has ran for a bit. It has crashed while playing flash games, Steam games, and just sitting and idling. I have pulled the computer apart and cleaned any dust in there just in case it was a dust insulated overheating issue. I have checked drivers, reinstalled drivers, reinstalled Windows and I am at my wits end on what to do.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled for your computer.

On Sun 12/29/2013 5:30:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-30404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AC2AA5, 0xFFFFF88007298700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/29/2013 3:41:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-25178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F850)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/28/2013 7:59:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x109 (0xA3A039D89844BA20, 0xB3B7465EEAC18C16, 0xFFFFF80002A6E5A0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/28/2013 7:56:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xFC (0xFFFFF880088A9800, 0x800000019C344963, 0xFFFFF880088A9600, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



My System SpecsSystem Spec
.
29 Dec 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi SekitaLuna.

Quote:
Event[4087]:
Log Name: System
Source: Ntfs
Date: 2013-12-29T03:08:40.622
Event ID: 55
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Sekita-PC
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
Test the HDD using Data Lifeguard Diagnostic for Windows.

Also ....
Code:
fffff880`030cc950 fffff880`0101e242 ataport!IdeCompleteScsiIrp+0x62
fffff880`030cc980 fffff880`01018e32 ataport!IdeCommonCrbCompletion+0x5a
fffff880`030cc9b0 fffff880`010217ed ataport!IdeTranslateCompletedRequest+0x236
fffff880`030ccae0 fffff880`010210ec ataport!IdeProcessCompletedRequests+0x4d5
fffff880`030ccc10 fffff800`02a84f7c ataport!IdePortCompletionDpc+0x1a8
Scan the system for possible virus infection with the following programs.
Let us know the results.

Will decide the further steps after knowing these.
hardware
My System SpecsSystem Spec
29 Dec 2013   #3
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Thanks!! will try these now and report on the outcome.
My System SpecsSystem Spec
.

29 Dec 2013   #4
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Update:

Data Lifeguard Quicktest:


TDSSKiller:


Windows Defender Offline: Clean scan

Any more suggestions? Note: Running an Extended Test with Lifeguard.

Update: Extended Test Complete.

My System SpecsSystem Spec
30 Dec 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Good to see that the Data Lifeguard test passed. It rectifies some errors.

Now use the computer normally and let us know how it is working.

If the issue repeats, we have to think about the physical parts.

Edit: Like that Cheshire Cat!
My System SpecsSystem Spec
30 Dec 2013   #6
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

System crashed while trying to do a start up repair. Beginning to think SOMETHING is dying.

Cheshire Cat has personality! Doing a grab all and adding it to this post.
My System SpecsSystem Spec
30 Dec 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by SekitaLuna View Post
System crashed while trying to do a start up repair.
Two bad news in one.

First, there was a need to run a startup repair.

Second, it BSOD'd at a time when almost no drivers are active.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.
Hardware - Stress Test With Prime95

Try to update the BIOS to the latest (though that one is old, too) version F11 from GIGABYTE - Motherboard - Socket 1156 - GA-P55M-UD2 (rev. 1.1). Your installed version is F8.

Open the computer. Try to apply the SATA cable to an unused SATA port on the motherboard.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
______________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a02020fc40, 0, fffff8800124c30a, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

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

5: 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: fffff8a02020fc40, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800124c30a, 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 fffff80002cc30e0
 fffff8a02020fc40 

FAULTING_IP: 
Ntfs!NtfsSnapshotScbInternal+10a
fffff880`0124c30a 8b8380000020    mov     eax,dword ptr [rbx+20000080h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005610d30 -- (.trap 0xfffff88005610d30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=fffffa80081ccdc8
rdx=fffff8a00020fbc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800124c30a rsp=fffff88005610ec0 rbp=0000000000000727
 r8=0000000000000000  r9=0000000000000000 r10=fffffa80081ccc70
r11=fffffa80081ccdc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po cy
Ntfs!NtfsSnapshotScbInternal+0x10a:
fffff880`0124c30a 8b8380000020    mov     eax,dword ptr [rbx+20000080h] ds:00000000`20000080=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0a072 to fffff80002a8b880

STACK_TEXT:  
fffff880`05610bc8 fffff800`02b0a072 : 00000000`00000050 fffff8a0`2020fc40 00000000`00000000 fffff880`05610d30 : nt!KeBugCheckEx
fffff880`05610bd0 fffff800`02a8996e : 00000000`00000000 fffff8a0`0020fbc0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40440
fffff880`05610d30 fffff880`0124c30a : 00000000`00000000 fffff880`01249e49 00000000`00000001 fffffa80`077e2b40 : nt!KiPageFault+0x16e
fffff880`05610ec0 fffff880`012e300d : fffff8a0`0020fbc0 00000000`00000000 fffff8a0`0020fa90 fffffa80`07d47050 : Ntfs!NtfsSnapshotScbInternal+0x10a
fffff880`05610ef0 fffff880`012e985c : fffffa80`081ccc70 fffff8a0`0020fa90 00000000`00000000 fffffa80`08481fb0 : Ntfs!NtfsCreateScb+0x12d
fffff880`05610fb0 fffff880`012d7e65 : fffffa80`081ccc70 fffffa80`08481fb0 fffffa80`07912180 fffff8a0`0020fed0 : Ntfs!NtfsOpenAttribute+0xac
fffff880`056110c0 fffff880`012d474f : fffff880`05611880 fffff800`00001000 00000000`08afc000 00000000`00000012 : Ntfs!NtfsOpenExistingAttr+0x145
fffff880`05611180 fffff880`012d4f1f : fffffa80`081ccc70 fffffa80`08481c10 fffff8a0`0020fed0 fffff880`00000012 : Ntfs!NtfsOpenAttributeInExistingFile+0x50f
fffff880`05611310 fffff880`012e5dd6 : fffffa80`081ccc70 fffffa80`08481c10 fffff8a0`0020fed0 fffffa80`0797b801 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`05611400 fffff880`012e01ed : fffffa80`081ccc70 fffffa80`08481c10 fffff880`056115e0 fffff880`05611628 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`056114d0 fffff880`0124f06d : fffffa80`081ccc70 fffffa80`08481c10 fffff880`05611880 fffff880`00000000 : Ntfs!NtfsCommonCreate+0x3dd
fffff880`056116b0 fffff800`02a9b01a : fffff880`056117f0 fffff880`056118b8 fffff880`0561189c 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`056116e0 fffff880`0124ef8f : fffff880`0124f050 fffff880`056117f0 00000000`00000000 fffff880`012eb28d : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`056117c0 fffff880`012e6920 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08481c10 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`05611820 fffff880`0108e3a2 : fffffa80`07912030 fffffa80`08481c10 fffffa80`0797b800 fffff880`6d4e6f49 : Ntfs!NtfsFsdCreate+0x1b0
fffff880`056119d0 fffff800`02d8aa45 : 00000000`00000060 fffff800`02d89560 fffffa80`0773d878 fffff8a0`00228430 : fltmgr!FltpCreate+0x392
fffff880`05611a80 fffff800`02d7f784 : fffffa80`076ce9d0 00000000`00000000 fffffa80`067569f0 fffff8a0`0192bb00 : nt!IopParseDevice+0x14f0
fffff880`05611be0 fffff800`02d8445d : fffffa80`067569f0 fffff880`05611d40 fffffa80`00000240 fffffa80`06734b40 : nt!ObpLookupObjectName+0x585
fffff880`05611ce0 fffff800`02d8c597 : fffff880`05611d88 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x1cd
fffff880`05611d90 fffff800`02d2e88b : fffffa80`07d2c0e8 fffffa80`00100001 00000000`00000000 fffff880`05611f50 : nt!IopCreateFile+0x2b7
fffff880`05611e30 fffff880`01091dca : fffffa80`07d2c010 00000000`00000017 00000000`00000000 fffffa80`0773d878 : nt!IoCreateFileEx+0xfb
fffff880`05611ed0 fffff880`0109001e : fffffa80`0773d878 00000000`00000028 00000000`00000000 00000000`00000028 : fltmgr!FltpNormalizeNameComponent+0x16a
fffff880`05611fd0 fffff880`01091361 : fffffa80`00000032 00000000`00000032 00000000`00000029 00000000`00000000 : fltmgr!FltpExpandShortNames+0x14e
fffff880`05612030 fffff880`0109113e : fffffa80`07d2c010 fffff880`01080000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`05612070 fffff880`0107254b : fffffa80`075ca280 00000000`00000000 fffffa80`07dbf8e0 fffff880`05613000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`056120d0 fffff880`0107dad4 : 00000000`00008000 fffffa80`07dbf8e0 00000000`00000000 00000000`00000401 : fltmgr!FltpGetFileNameInformation+0x26b
fffff880`05612150 fffff880`010c136b : fffffa80`07d2c010 fffff8a0`019300e0 00000000`00000001 fffff880`05612280 : fltmgr!FltGetFileNameInformation+0x184
fffff880`056121e0 fffff880`010bfbdb : fffff140`00de06a7 00000000`00000001 00000000`00000000 00000000`0000034a : fileinfo!FIStreamGetInfo+0x11f
fffff880`05612260 fffff880`01070242 : 00000000`00000000 fffff8a0`019300e0 fffffa80`08973fb0 00000000`00000000 : fileinfo!FIPostCreateCallback+0x1c7
fffff880`056122f0 fffff880`0106f38b : fffffa80`07912030 fffffa80`0840b5c0 fffffa80`0779dbb0 fffffa80`0779ddd0 : fltmgr!FltpPerformPostCallbacks+0x392
fffff880`056123c0 fffff880`0108e2b9 : fffffa80`08973c10 fffffa80`0797b800 fffffa80`08973c00 fffffa80`0771f8e0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
fffff880`05612450 fffff800`02d8aa45 : 00000000`00000005 fffff800`02d89560 fffffa80`08462f20 00000000`00000000 : fltmgr!FltpCreate+0x2a9
fffff880`05612500 fffff800`02d7f784 : fffffa80`076ce9d0 00000000`00000000 fffffa80`07dbfb10 fffff8a0`00000200 : nt!IopParseDevice+0x14f0
fffff880`05612660 fffff800`02d8445d : fffffa80`07dbfb10 fffff880`056127c0 fffffa80`00000240 fffffa80`06734b40 : nt!ObpLookupObjectName+0x585
fffff880`05612760 fffff800`02d8c597 : 00000000`80000000 00000000`00000001 00000000`00000000 00000000`00052b3c : nt!ObOpenObjectByName+0x1cd
fffff880`05612810 fffff800`02d48f4a : fffff880`05612a48 fffff800`001200a9 00000000`000002d8 fffff880`056129c0 : nt!IopCreateFile+0x2b7
fffff880`056128b0 fffff960`000227f6 : fffffa80`00000021 fffff800`43465454 fffff880`04dace60 00000000`00000082 : nt!IoCreateFile+0x8a
fffff880`05612940 fffff960`00023327 : fffffa80`07eea610 00000000`00000000 00000000`00000000 00000000`0000004c : win32k!EngSaveFloatingPointState+0xe6
fffff880`05612a40 fffff960`0002561b : 00000000`000004e4 fffff880`000001b5 00000000`00000000 00000000`00000000 : win32k!InitFNTCache+0x227
fffff880`05612b30 fffff960`00025830 : fffffa80`08418b30 fffffa80`08418b30 fffffa80`08418b30 000007fe`fd99e740 : win32k!InitializeGreCSRSS+0x13b
fffff880`05612be0 fffff800`02a8aad3 : fffffa80`07dbdb60 00000000`001f0003 00000000`00000007 fffff880`05612c01 : win32k!NtUserInitialize+0xa0
fffff880`05612c20 000007fe`fd9333ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0021fac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd9333ea


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8800124c30f - Ntfs!NtfsSnapshotScbInternal+10f
    [ 00:20 ]
1 error : !Ntfs (fffff8800124c30f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
My System SpecsSystem Spec
30 Dec 2013   #8
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Used my Reinstallation DVD to successfully do a startup repair using system restore.
The wattage of the PSU is 700, and the Calculator says 422 BUT I don't know all the specs. I just put in what I knew.

*removed Speccy Link*

Downloaded and updated Bios using http://www.gigabyte.com/MicroSite/121/tech_a_bios.htm
Now need to power cycle.

Update: Successfully updated BIOS
Got a message after rebooting.. SATA running as (something) Change Y or N (Never seen this before)
My System SpecsSystem Spec
30 Dec 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by SekitaLuna View Post
Got a message after rebooting.. SATA running as (something) Change Y or N (Never seen this before)
What have you done there?

Let us see ..... upload your MSINFO32.nfo file.
  1. Click on the start button
  2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
  3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
  4. Give the time for processing, it will save a .nfo file on your desktop.
  5. Zip it, and upload it following the instruction.
Also perform the other tests too?
My System SpecsSystem Spec
30 Dec 2013   #10
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

I think it stated Run SATA as AHCI if I am not mistaken Y or N and counted down waiting for a response. It booted normally when no response was given. The mem test has been run multiple times (twice overnight with 9 passes) with no red lines.

I have not run the stress test as of yet.

Reviewing some of the stats of my computer I realized that SP1 was not installed, and was "hidden". It would not install via Windows Update, so I used a readiness tool and installed it manually.

Update: Stress test showed no issues after 2 hours of running.
My System SpecsSystem Spec
Reply

 BSOD 0x3B and 0x1E




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Intermittent BSOD; 0x1e, 0x7e, 0x3b
Having to type quickly as crashes are random, so apologies for mistakes. Removed programs commonly related to causing problems, updates graphics driver on APU, cant update wireless drivers as its discontinued (possible culprit?). Crashes are very random, can be days between or a loop of 5...
BSOD Help and Support
BSOD whenever playing games, 0x1E or 0x3B
Hi everyone, So sorry to be just dropping in--I've been lurking since my first laptop (now on third) and I've been able to fix BSODs just reading. But this one's really a pain. I get BSODs whenever I game--this happens whatever game I play, sometimes a few minutes after I start, sometimes a...
BSOD Help and Support
BSOD 0x3B / 0x1E @ ntoskml.exe during gaming
Over the last few days I've been having constant crashes. It's not always a bluescreen, sometimes just an instant restart, others a total lockup with audio still coming out. (Just a loud continuous noise of what it was playing before crash) Sometimes it actually blue screened so I did get mini...
BSOD Help and Support
BSOD at random intervals, primarily 0x1e, 0x3b and 0x7e
Windows 7 Enterprise 64-bit Retail GA-MA770T-UD3P Motherboard 2 2x2gb CM3X2G1333C9 Corsair DDR3 AMD Phenom II X4 B50 (4 cores at 3.1ghz stock speeds, 1.4v) NVIDIA Geforce GTX 260 768mb Fresh install of windows, roughly 1 month ago 2-3 years old hardware, 4 year old harddisks
BSOD Help and Support
New installation - Win 7 (64 bit) - BSOD 0xa, 0x3b, 0x1e, etc
System Specs: OS: Windows 7 Home Premium (64-bit) MOBO: Asus M4A89GTD-Pro/USB3 CPU: Athlon Phenom II x4 955 Black Edition VID: Nvidia 9500 GT (Upgraded to ATI HD 5770) AUDIO: Realtek (Motherboard Default) PSU: OCZ Modular - 500 watts Related Errors: 0x0000003b
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 19:25.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App