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: Random BSOD's want to figure this out once and for all

14 Mar 2012   #1

Windows 7 Professional x64
 
 
Random BSOD's want to figure this out once and for all

Basically they just come up at random. I don't even know anymore. It's probably some hardware thing, I'm thinking maybe my graphics card or hard drive.

But anyway I finally decided that I should try to figure this out since I just want an overall stable system.

I've done the jcgriff2 report thing. But before I post it as an attachment I just have one question. There's a lot of info in the report; will it contain any Personally Identifiable Information?

I just want to get this figured out before I go around publicly posting my system info on the internet. Although I do appreciate the help from everyone who will be diagnosing my system errors I just like to take caution. You can never be too sure you know?

Thanks for replies

My System SpecsSystem Spec
.

14 Mar 2012   #2

Windows 8 Pro 9200 x64 w/Media Center
 
 

No personal information is included in the jcgriff report, only machine specific data which will show us what your problem is.
My System SpecsSystem Spec
14 Mar 2012   #3

Windows 7 Professional x64
 
 

Blah only one response to my inquiry. Very well then.

Guess I'll have to take your word for it.

Attached the files below. Thanks for your help
My System SpecsSystem Spec
.


16 Mar 2012   #4

Windows 7 Professional x64
 
 

Can someone please help me try to get my blue screens worked out?

Sorry I didn't give a very good description but they are so random I have nothing else to say really except I think it might be my graphics card.

Any responses will be very appreciated as I really want a stable system. Thank you so much!!
My System SpecsSystem Spec
16 Mar 2012   #5

Windows 7 Home Premium 64 Bit
 
 

Possible out of date driver:
Code:
Lycosa	fffff880`0836f000	fffff880`08373980	Fri Jan 18 01:51:42 2008 (4790689e)	0000e99d		Lycosa.sys
Update the above driver and see if it helps before proceeding with the rest...


Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\obidon\Windows_NT6_BSOD_jcgriff2\031412-22635-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`0324be70 Debug session time: Wed Mar 14 12:05:06.290 2012 (UTC - 6:00) System Uptime: 0 days 0:00:50.272 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800318c6e8, fffff8800318bf50, fffff880012d2900} Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+16818 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800318c6e8 Arg3: fffff8800318bf50 Arg4: fffff880012d2900 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800318c6e8 -- (.exr 0xfffff8800318c6e8) ExceptionAddress: fffff880012d2900 (Ntfs! ?? ::NNGAKEGL::`string'+0x0000000000016818) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800318bf50 -- (.cxr 0xfffff8800318bf50) rax=fffff8a001cfe5c0 rbx=fffff8800318c9b0 rcx=000000000000122a rdx=fffff88002f00000 rsi=0002000000000000 rdi=fffffa8005916120 rip=fffff880012d2900 rsp=fffff8800318c920 rbp=fffff800032235a0 r8=0000000000009150 r9=0000000000000040 r10=fffff8000300f000 r11=fffff8a001cfe5c0 r12=fffff8a001cfe5c0 r13=fffffa800479c180 r14=fffff8800318c9a1 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 Ntfs! ?? ::NNGAKEGL::`string'+0x16818: fffff880`012d2900 488b8e88000000 mov rcx,qword ptr [rsi+88h] ds:002b:00020000`00000088=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b60e0 ffffffffffffffff FOLLOWUP_IP: Ntfs! ?? ::NNGAKEGL::`string'+16818 fffff880`012d2900 488b8e88000000 mov rcx,qword ptr [rsi+88h] FAULTING_IP: Ntfs! ?? ::NNGAKEGL::`string'+16818 fffff880`012d2900 488b8e88000000 mov rcx,qword ptr [rsi+88h] BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff88001266cfa to fffff880012d2900 STACK_TEXT: fffff880`0318c920 fffff880`01266cfa : fffff800`032235a0 fffff880`0318cb01 fffff880`0318c9a1 fffff8a0`01cfe5c0 : Ntfs! ?? ::NNGAKEGL::`string'+0x16818 fffff880`0318c980 fffff880`012ee3dc : fffffa80`05916120 fffffa80`0479c180 fffff8a0`01cfe5c0 fffff8a0`01cfe958 : Ntfs!NtfsTeardownFromLcb+0x1ea fffff880`0318ca10 fffff880`0126f602 : fffffa80`05916120 fffffa80`05916120 fffff8a0`01cfe5c0 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc fffff880`0318ca90 fffff880`013058f3 : fffffa80`05916120 fffff800`032235a0 fffff8a0`01cfe5c0 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2 fffff880`0318cad0 fffff880`012dfc9f : fffffa80`05916120 fffff8a0`01cfe6f0 fffff8a0`01cfe5c0 fffffa80`0479c180 : Ntfs!NtfsCommonClose+0x353 fffff880`0318cba0 fffff800`0308c6e1 : 00000000`00000000 fffff800`03377400 fffffa80`03705601 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f fffff880`0318cc70 fffff800`0331e726 : 00000000`00000000 fffffa80`03705680 00000000`00000080 fffffa80`036da040 : nt!ExpWorkerThread+0x111 fffff880`0318cd00 fffff800`0305dac6 : fffff880`02f63180 fffffa80`03705680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0318cd40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c9b0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Ntfs! ?? ::NNGAKEGL::`string'+16818 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79996d STACK_COMMAND: .cxr 0xfffff8800318bf50 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!_??_::NNGAKEGL::_string_+16818 BUCKET_ID: X64_0x24_Ntfs!_??_::NNGAKEGL::_string_+16818 Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...
Thanks to Dave76 for help understanding possible causes.

Event Viewer Errors associated to your crash...
Code:
Event[353]:
  Log Name: System
  Source: Ntfs
  Date: 2012-03-14T12:45:44.757
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: x0bi7
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume1.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

  • I would also recommend following the steps laid out in HD Diagnostic


Update to Service Pack 1 (SP1)
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
My System SpecsSystem Spec
17 Mar 2012   #6

Windows 7 Professional x64
 
 

Ok updated the Lycosa driver and haven't had a bluescreen yet. I'll post the chkdsk results once they finish. Thanks for the informative reply.
My System SpecsSystem Spec
17 Mar 2012   #7

Windows 7 Home Premium 64 Bit
 
 

You're welcome. For any drives that do not give the message:
Windows has checked the file system and found no problems
run the disk checks again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
My System SpecsSystem Spec
17 Mar 2012   #8

Windows 7 Professional x64
 
 

Here is the chkdsk log found in the Event Viewer log.

Code:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  562176 file records processed.                                          File verification completed.
  1348 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              101 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  669212 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  562176 file SDs/SIDs processed.                                         Cleaning up 16 unused index entries from index $SII of file 0x9.
Cleaning up 16 unused index entries from index $SDH of file 0x9.
Cleaning up 16 unused security descriptors.
Security descriptor verification completed.
  53519 data files processed.                                            CHKDSK is verifying Usn Journal...
  35082984 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  562160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  4677735 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 312560608 KB total disk space.
 292910592 KB in 471995 files.
    264492 KB in 53520 indexes.
         0 KB in bad sectors.
    674584 KB in use by the system.
     65536 KB occupied by the log file.
  18710940 KB available on disk.

      4096 bytes in each allocation unit.
  78140152 total allocation units on disk.
   4677735 allocation units available on disk.

Internal Info:
00 94 08 00 d6 04 08 00 f0 e1 0e 00 00 00 00 00  ................
c2 15 00 00 65 00 00 00 00 00 00 00 00 00 00 00  ....e...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
17 Mar 2012   #9

Windows 7 Home Premium 64 Bit
 
 

How many times did you need to run the disk check to get that message?

How is the system responding after the disk check(s)?
My System SpecsSystem Spec
18 Mar 2012   #10

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by writhziden View Post
How many times did you need to run the disk check to get that message?

How is the system responding after the disk check(s)?
I only had to run it once, but it took a really long time to complete. I've done check disk before at startup, but I don't think it ever got to cycle through all 5 stages. It usually only did 3 stages before.

Overall the system seems to be fairly stable, no bluescreens since I've updated the Lycosa driver. I really hope it stays that way. Also the reliability history is clear so far today except for one "Video hardware error". I'll let you know if anything else happens.

Also I did a chkdsk on my external Hitachi drive I have connected at the moment. I'll attach the log file of this drive too since it says that some problems were found and fixed.

Code:
Chkdsk was executed in read/write mode.  

Checking file system on F:
Volume label is Hitachi.

CHKDSK is verifying files (stage 1 of 5)...
  146176 file records processed.                                          File verification completed.
  61 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
The two index entries of length 0x80 and 0x70 are either identical
or appear in the wrong order.
7f 56 01 00 00 00 01 00 80 00 6e 00 00 00 00 00  .V......€.n.....
3d 56 01 00 00 00 01 00 88 38 eb 75 d5 bc cc 01  =V......ˆ8u....
00 98 92 b6 fd 54 ca 01 98 5f eb 75 d5 bc cc 01  .˜’.T..˜_u....
88 38 eb 75 d5 bc cc 01 00 20 00 00 00 00 00 00  ˆ8u..... ......
9c 1e 00 00 00 00 00 00 20 00 00 00 00 00 00 00  œ....... .......
16 01 4c 00 44 00 22 00 50 00 61 00 74 00 68 00  ..L.D.".P.a.t.h.
20 00 6f 00 66 00 20 00 44 00 65 00 73 00 74 00   .o.f. .D.e.s.t.
69 00 6e 00 79 00 2e 00 66 00 78 00 70 00 00 00  i.n.y...f.x.p...
70 00 01 00 00 00 01 00 70 00 d6 75 d5 bc cc 01  p.......p..u....
----------------------------------------------------------------------
80 56 01 00 00 00 01 00 70 00 5e 00 00 00 00 00  €V......p.^.....
3d 56 01 00 00 00 01 00 ca d4 eb 75 d5 bc cc 01  =V........u....
00 98 92 b6 fd 54 ca 01 db fb eb 75 d5 bc cc 01  .˜’.T....u....
ca d4 eb 75 d5 bc cc 01 00 20 00 00 00 00 00 00  ..u..... ......
9c 1e 00 00 00 00 00 00 20 00 00 00 00 00 00 00  œ....... .......
0e 01 4c 00 44 00 20 00 50 00 69 00 72 00 61 00  ..L.D. .P.i.r.a.
6e 00 68 00 61 00 2e 00 66 00 78 00 70 00 00 00  n.h.a...f.x.p...
81 56 01 00 00 00 01 00 78 00 66 00 00 00 00 00  V......x.f.....
Sorting index $I30 in file 87613.
Unable to locate the file name attribute of index entry LD"Path of Destiny.fxp
of index $I30 with parent 0x1563d in file 0x1567f.
Deleting index entry LD"Path of Destiny.fxp in index $I30 of file 87613.
  166756 index entries processed.                                         Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.

Recovering orphaned file LD Path of Destiny.fxp (87679) into directory file 87613.

CHKDSK is verifying security descriptors (stage 3 of 5)...
  146176 file SDs/SIDs processed.                                         Cleaning up 87 unused index entries from index $SII of file 0x9.
Cleaning up 87 unused index entries from index $SDH of file 0x9.
Cleaning up 87 unused security descriptors.
Security descriptor verification completed.
  10291 data files processed.                                            CHKDSK is verifying Usn Journal...
  34187632 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x1d31ac9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ad8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ba9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bad000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c8e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c98000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31bae000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c99000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c99000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c9a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31c9a000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31cfb000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d02000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d03000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d03000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d04000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d04000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d65000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6d000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31d6e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dcf000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd5000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd6000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd6000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31dd8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e39000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e3f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e40000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e40000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e41000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31e41000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea4000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea5000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea5000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea6000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea6000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31ea9000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8e000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f8f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f90000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f90000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f91000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x1d31f91000 for 0x1000 bytes.
Windows replaced bad clusters in file 18723
of name \VMWARE~1\MYVIRT~1\TESTOP~1\WINDOW~1.VME.
  146160 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  3957347 free clusters processed.                                         Free space verification is complete.
Adding 31 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 195350368 KB total disk space.
 179213184 KB in 132997 files.
     55680 KB in 10292 indexes.
    251992 KB in use by the system.
     65536 KB occupied by the log file.
  15829388 KB available on disk.

      4096 bytes in each allocation unit.
  48837592 total allocation units on disk.
   3957347 allocation units available on disk.
Thanks for the help.
My System SpecsSystem Spec
Reply

 Random BSOD's want to figure this out once and for all





Thread Tools



Similar help and support threads for2: Random BSOD's want to figure this out once and for all
Thread Forum
Solved bsod cant figure this one out BSOD Help and Support
Random shutdowns playing Mass Effect 2 (need to figure out what from) BSOD Help and Support
Trying to figure out this BSOD BSOD Help and Support
BSOD i cant figure out BSOD Help and Support
Random BSOD can't figure it out! Been happening for a couple weeks now BSOD Help and Support
BSOD help i cant figure it out HELP!!! BSOD Help and Support
BSOD while OC'ing, just trying to figure it out. 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 11:37 PM.
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