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 General Useage 0x000000d1


06 Oct 2013   #11

windows 7 home premium 64bit
 
 

Also Power supply Reports - from bios

3.3V= it was moving between 3.408 <most of the time> and sometimes 3.392
5v=5.120
12v=12.192

i also have some power going to my Vcard <2 of them> not sure if i need to check those as well.

the cpu voltage at the time <in bios> was bouncing between 1.088 and 1.096


My System SpecsSystem Spec
.

07 Oct 2013   #12

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Your voltages look fine to me.
My System SpecsSystem Spec
07 Oct 2013   #13

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck 3B, {c0000005, fffff800032705a8, fffff88008e73a60, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeInitializeApc+0 )
Code:
0: kd> lmvm atikmpag

start             end                 module name
fffff880`04214000 fffff880`042b2000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Aug 30 23:32:32 2013 (52211D80)
    CheckSum:         0009C9D2
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Are you sure you have updated the graphics card driver?

Code:
 fffff88008e73a60 -- (.cxr 0xfffff88008e73a60)
rax=fffffa8008d0a980 rbx=fffff88008e744c8 rcx=0000000000000000
rdx=fffffa8008d0a930 rsi=fffff900c226da20 rdi=0000000000000020
rip=fffff800032705a8 rsp=fffff88008e74448 rbp=0000000000000005
 r8=0000000000000000  r9=0000000000000000 r10=fffff900c0200000
r11=fffffa8008d0a930 r12=0000000000000000 r13=000000000025fd20
r14=000000000025cdb0 r15=0000000075122450
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KeInitializeApc:
fffff800`032705a8 c60112          mov     byte ptr [rcx],12h ds:002b:00000000`00000000=??
Code:
0: kd> dt nt!_KAPC
   +0x000 Type             : UChar
   +0x001 SpareByte0       : UChar
   +0x002 Size             : UChar
   +0x003 SpareByte1       : UChar
   +0x004 SpareLong0       : Uint4B
   +0x008 Thread           : Ptr64 _KTHREAD
   +0x010 ApcListEntry     : _LIST_ENTRY
   +0x020 KernelRoutine    : Ptr64     void 
   +0x028 RundownRoutine   : Ptr64     void 
   +0x030 NormalRoutine    : Ptr64     void 
   +0x038 NormalContext    : Ptr64 Void
   +0x040 SystemArgument1  : Ptr64 Void
   +0x048 SystemArgument2  : Ptr64 Void
   +0x050 ApcStateIndex    : Char
   +0x051 ApcMode          : Char
   +0x052 Inserted         : UChar
The last instruction which seems to be caused a context switch to save the thread's context and then produce a bugcheck is nt!KeInitializeApc (undocumented), which is used to create and fill the fields of the above data structure.

The function prototype for nt!KeInitializeApc is here:

Code:
NTKERNELAPI VOID KeInitializeApc (

IN PRKAPC Apc,

IN PKTHREAD Thread,

IN KAPC_ENVIRONMENT Environment,

IN PKKERNEL_ROUTINE KernelRoutine, <-- Called at IRQL Level 2

IN PKRUNDOWN_ROUTINE RundownRoutine OPTIONAL,

IN PKNORMAL_ROUTINE NormalRoutine OPTIONAL,

IN KPROCESSOR_MODE ApcMode,

IN PVOID NormalContext

);
The KernelRoutine parameter contains a pointer to the function which will be called when the APC is dispatched, and is executed at the IRQL Level of 2, although, the current thread only has a IRQL Level of 0, so my best guess is that routine was called at the wrong IRQL Level?

Please run Video Card - Stress Test with Furmark for a few hours, and do not let the temperature exceed 90*C.

GPU-Z Video card GPU Information Utility is a good program for monitoring GPU temperature.
My System SpecsSystem Spec
.


07 Oct 2013   #14

windows 7 home premium 64bit
 
 

Are you sure you have updated the graphics card driver?

If it is not showing the correct driver i can again try updating it thats strange though,

I uninstalled the old driver, used DriverSweeper
Guru3D - Driver Sweeper

<kind of an older version but i like it>

and Reinstalled with the new driver,

AMD Catalyst? Display Driver for Windows 7/Windows 8 64-bit
http://www2.ati.com/drivers/13-9_win...d_ccc_whql.exe


i ran furmark for about 1 hour before coming to this forum, however i can try it again for about 2 hours if you think it will help i dont mind

Please run http://www.sevenforums.com/bsod-help...t-furmark.html for a few hours, and do not let the temperature exceed 90*C.



the Gfx Card i have is a...

XFX Double D FX-787A-CDFC Radeon HD 7870 GHz Edition 2GB 256-bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX Support Video Card - Newegg.com


P.S.

We have not had a crash in 1 day, what "seems" to have at least temporary stop the crashing was i removed all usb devices from usb 3.0 ports and am currently only using 2 usb 2.0 ports that are a totally different bus<chipset>/wtv that the other ports.
My System SpecsSystem Spec
07 Oct 2013   #15

windows 7 home premium 64bit
 
 

we had 2 more crashes today.

here are the minidumps and the loaded drivers.

100713-15724-01.dmp 10/7/2013 3:00:58 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`000d3aa0 fffff880`059e8b50 00000000`00000000 Ntfs.sys Ntfs.sys+93c6f NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100713-15724-01.dmp 4 15 7601 277,192 10/7/2013 3:02:09 PM

100713-13338-01.dmp 10/7/2013 2:58:07 PM ATTEMPTED_WRITE_TO_READONLY_MEMORY 0x000000be fffff880`03bce444 00000002`0f126121 fffff880`08a6e020 00000000`0000000a USBPORT.SYS USBPORT.SYS+2d444 USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100713-13338-01.dmp 4 15 7601 277,192 10/7/2013 2:59:17 PM


Attached Files
File Type: zip wnight77.zip (57.0 KB, 1 views)
My System SpecsSystem Spec
08 Oct 2013   #16

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Remember to look for any screen distortions or artifacts during Furmark.

Code:
BugCheck BE, {fffff88003bce444, 20f126121, fffff88008a6e020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )
Code:
0: kd> !dpx
Start memory scan  : 0xfffff88008a6deb8 ($csp)
End memory scan    : 0xfffff88008a6f000 (Stack Base)

0xfffff88008a6dec8 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e018 : 0xfffff800032d5cae : nt!KiPageFault+0x16e
0xfffff88008a6e020 : 0x0000000000002710 :  Trap @ fffff88008a6e020
0xfffff88008a6e038 : 0xfffff88003bce42c : USBPORT!USBPORT_IsrDpc
0xfffff88008a6e058 : 0xfffff800034dc8a0 : nt!IopTimerQueueHead
0xfffff88008a6e060 : 0xfffff88003bce434 : USBPORT!USBPORT_IsrDpc+0x8
0xfffff88008a6e068 : 0xfffff80003512240 : nt!IopTimerLock
0xfffff88008a6e088 : 0xfffff800032da0ea : nt!KeWaitForMultipleObjects+0x272
0xfffff88008a6e0f0 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e188 : 0xfffff800036d5777 : nt!IoInitializeTimer+0x77
0xfffff88008a6e1d8 : 0xfffff88003ba2628 : USBPORT!MPf_Get32BitFrameNumber+0xa0
0xfffff88008a6e208 : 0xfffff88003bae34d : USBPORT!USBPORTBUSIF_UsbdBusQueryBusTime+0x6d
0xfffff88008a6e238 : 0xfffff88006000f7a : usbaudio!USBHwGetCurrentFrame+0x26
0xfffff88008a6e268 : 0xfffff88006001081 : usbaudio!UsbHwFrameCountTimestamp+0x89
0xfffff88008a6e298 : 0xfffff8000340b30d : nt!ExFreePoolWithTag+0x22d
0xfffff88008a6e2e8 : 0xfffff880060012ca : usbaudio!USBHwGetClockRatio+0x186
0xfffff88008a6e358 : 0xfffff880060016f0 : usbaudio!USBType1RenderBytePosition+0x70
0xfffff88008a6e3d8 : 0xfffff88006010247 : usbaudio!PropertyGetAudioPositionEx+0x4b
0xfffff88008a6e3f8 : 0xfffff880044a7500 : ks!PinAutomationTable+0x110
0xfffff88008a6e418 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f
0xfffff88008a6e458 : 0xfffff80003467588 : nt!NonPagedPoolDescriptor+0x8
0xfffff88008a6e460 : 0xfffff8800449f590 : ks!WPP_ThisDir_CTLGUID_AvStream+0xe0
0xfffff88008a6e468 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e488 : 0xfffff880044a9b47 : ks!KspHandleAutomationIoControl+0x2c7
0xfffff88008a6e4c8 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
0xfffff88008a6e4f0 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
0xfffff88008a6e4f8 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e508 : 0xfffff880044aa183 : ks!CKsPin::DispatchDeviceIoControl+0x11f
0xfffff88008a6e568 : 0xfffff880044a97bb : ks!KsDispatchIrp+0xdb
0xfffff88008a6e598 : 0xfffff88004490560 : ks!CKsDevice::PassThroughIrp+0xc0
0xfffff88008a6e638 : 0xfffff8000340bd0e : nt!ExAllocatePoolWithTag+0xfe
0xfffff88008a6e658 : 0xfffff80003489b80 : nt!ObTypeIndexTable
0xfffff88008a6e748 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f

[...]
Code:
0: kd> lmvm ladfGSRamd64
Browse full module list
start             end                 module name
fffff880`060db000 fffff880`060f2880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 15 19:39:15 2013 (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your driver for the Logitech GSeries Headset seems to be causing problems, please check for any updates/patches from here - http://www.logitech.com/en-us/support

The driver most likely has attempted to execute a virtual address which has the Executable protection bit clear, the !pte would have been useful but this is Minidump and this information wasn't retained.
My System SpecsSystem Spec
09 Oct 2013   #17

windows 7 home premium 64bit
 
 

Quote   Quote: Originally Posted by x BlueRobot View Post
Remember to look for any screen distortions or artifacts during Furmark.

Code:
BugCheck BE, {fffff88003bce444, 20f126121, fffff88008a6e020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )
Code:
0: kd> !dpx
Start memory scan  : 0xfffff88008a6deb8 ($csp)
End memory scan    : 0xfffff88008a6f000 (Stack Base)

0xfffff88008a6dec8 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e018 : 0xfffff800032d5cae : nt!KiPageFault+0x16e
0xfffff88008a6e020 : 0x0000000000002710 :  Trap @ fffff88008a6e020
0xfffff88008a6e038 : 0xfffff88003bce42c : USBPORT!USBPORT_IsrDpc
0xfffff88008a6e058 : 0xfffff800034dc8a0 : nt!IopTimerQueueHead
0xfffff88008a6e060 : 0xfffff88003bce434 : USBPORT!USBPORT_IsrDpc+0x8
0xfffff88008a6e068 : 0xfffff80003512240 : nt!IopTimerLock
0xfffff88008a6e088 : 0xfffff800032da0ea : nt!KeWaitForMultipleObjects+0x272
0xfffff88008a6e0f0 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e188 : 0xfffff800036d5777 : nt!IoInitializeTimer+0x77
0xfffff88008a6e1d8 : 0xfffff88003ba2628 : USBPORT!MPf_Get32BitFrameNumber+0xa0
0xfffff88008a6e208 : 0xfffff88003bae34d : USBPORT!USBPORTBUSIF_UsbdBusQueryBusTime+0x6d
0xfffff88008a6e238 : 0xfffff88006000f7a : usbaudio!USBHwGetCurrentFrame+0x26
0xfffff88008a6e268 : 0xfffff88006001081 : usbaudio!UsbHwFrameCountTimestamp+0x89
0xfffff88008a6e298 : 0xfffff8000340b30d : nt!ExFreePoolWithTag+0x22d
0xfffff88008a6e2e8 : 0xfffff880060012ca : usbaudio!USBHwGetClockRatio+0x186
0xfffff88008a6e358 : 0xfffff880060016f0 : usbaudio!USBType1RenderBytePosition+0x70
0xfffff88008a6e3d8 : 0xfffff88006010247 : usbaudio!PropertyGetAudioPositionEx+0x4b
0xfffff88008a6e3f8 : 0xfffff880044a7500 : ks!PinAutomationTable+0x110
0xfffff88008a6e418 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f
0xfffff88008a6e458 : 0xfffff80003467588 : nt!NonPagedPoolDescriptor+0x8
0xfffff88008a6e460 : 0xfffff8800449f590 : ks!WPP_ThisDir_CTLGUID_AvStream+0xe0
0xfffff88008a6e468 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e488 : 0xfffff880044a9b47 : ks!KspHandleAutomationIoControl+0x2c7
0xfffff88008a6e4c8 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
0xfffff88008a6e4f0 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
0xfffff88008a6e4f8 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e508 : 0xfffff880044aa183 : ks!CKsPin::DispatchDeviceIoControl+0x11f
0xfffff88008a6e568 : 0xfffff880044a97bb : ks!KsDispatchIrp+0xdb
0xfffff88008a6e598 : 0xfffff88004490560 : ks!CKsDevice::PassThroughIrp+0xc0
0xfffff88008a6e638 : 0xfffff8000340bd0e : nt!ExAllocatePoolWithTag+0xfe
0xfffff88008a6e658 : 0xfffff80003489b80 : nt!ObTypeIndexTable
0xfffff88008a6e748 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f

[...]
Code:
0: kd> lmvm ladfGSRamd64
Browse full module list
start             end                 module name
fffff880`060db000 fffff880`060f2880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 15 19:39:15 2013 (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your driver for the Logitech GSeries Headset seems to be causing problems, please check for any updates/patches from here - Logitech Support - Downloads, Manuals, FAQs & More

The driver most likely has attempted to execute a virtual address which has the Executable protection bit clear, the !pte would have been useful but this is Minidump and this information wasn't retained.

i installed the new version of the driver, lets hope the pc finally settles down and stops bluescreening, its like every day it develops a new reason to bluescreen :/ its been good since the last crash so far tho. <after updating the driver>
My System SpecsSystem Spec
10 Oct 2013   #18

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

That's good news, please keep me posted
My System SpecsSystem Spec
02 Nov 2013   #19

windows 7 home premium 64bit
 
 

welp the blue screens have reappeared again for some reason, nothing was changed either...

110113-10358-01.dmp 11/1/2013 10:25:25 PM APC_INDEX_MISMATCH 0x00000001 00000000`75332e09 00000000`00000000 00000000`0000ffff fffff880`0840fb60 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-10358-01.dmp 4 15 7601 277,192 11/1/2013 10:26:24 PM
110113-11388-01.dmp 11/1/2013 7:48:48 PM BUGCODE_USB_DRIVER 0x000000fe 00000000`00000006 fffffa80`08280a18 00000000`63706458 00000000`00000000 USBPORT.SYS USBPORT.SYS+2d27d USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-11388-01.dmp 4 15 7601 277,192 11/1/2013 7:49:55 PM
110113-10717-01.dmp 11/1/2013 4:18:44 PM ATTEMPTED_WRITE_TO_READONLY_MEMORY 0x000000be fffff880`0442d444 00000002`0f159121 fffff880`09512020 00000000`0000000a USBPORT.SYS USBPORT.SYS+2d444 USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-10717-01.dmp 4 15 7601 277,192 11/1/2013 4:19:44 PM
110113-11840-01.dmp 11/1/2013 12:29:37 AM 0x00000116 fffffa80`07e85010 fffff880`040f0e5c 00000000`00000000 00000000`00000002 dxgkrnl.sys dxgkrnl.sys+5d140 DirectX Graphics Kernel Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18228 (win7sp1_gdr.130731-2222) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-11840-01.dmp 4 15 7601 615,640 11/1/2013 12:30:45 AM


Attached Files
File Type: zip wnight77.zip (98.7 KB, 1 views)
My System SpecsSystem Spec
02 Nov 2013   #20

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck BE, {fffff8800442d444, 20f159121, fffff88009512020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )
Code:
0: kd> lmvm ladfGSRamd64
start             end                 module name
fffff880`03fb8000 fffff880`03fcf880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Timestamp:        Mon Apr 15 19:39:15 2013 (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your Logitech Headset driver seems to be causing problems again, did you manage to update the driver? If so, it may be a good idea to remove the driver completely and then see if any problems arise.

Code:
BugCheck 1, {75332e09, 0, ffff, fffff8800840fb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
We can see from the above bugcheck, that a thread has disabled Special APC's and Kernel APC's without re-enabling again, leading to the bugcheck. This is caused by drivers.

The thread must have entered a Guarded Region, which is synchronization mechanism used to allow only one thread to use a certain resource, the resource acquisition is protected from other threads.

Code:
0: kd> !irql
Debugger saved IRQL for processor 0x0 -- 0 (LOW_LEVEL)
We can see that the IRQL Level has dropped back to 0, and is no longer at IRQL Level 2, therefore APC's should have been enabled again when leaving the Guarded Region.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
information   Information
My System SpecsSystem Spec
Reply

 BSOD General Useage 0x000000d1




Thread Tools



Similar help and support threads for2: BSOD General Useage 0x000000d1
Thread Forum
Solved Solution to RAM useage Performance & Maintenance
WLM Primary Contact Email Useage Problem Browsers & Mail
BSOD 0x000000d1 BSOD Help and Support
bsod when idle or little useage BSOD Help and Support
Solved BSOD - 0x0000007E,0X000000D1,0X000000A,0X000000D1 BSOD Help and Support
BSOD - 0x000000d1 BSOD Help and Support
cpu useage allways at 100% issue Performance & Maintenance

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:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33