BSOD sometime on my system

Page 2 of 7 FirstFirst 1234 ... LastLast

  1. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #11

    Possible outdated drivers:
    Code:
    ASACPI	fffff880`04295000	fffff880`0429d000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
    ctac32k	fffff880`04b1f000	fffff880`04bcd000	Wed Jul 02 02:38:22 2008 (486b3e7e)	00095082		ctac32k.sys
    yk62x64	fffff880`0fe00000	fffff880`0fe63000	Mon Feb 23 08:02:27 2009 (49a2ba83)	0006049b		yk62x64.sys
    NuidFltr	fffff880`057f3000	fffff880`057fc000	Fri May 08 02:53:31 2009 (4a03f30b)	0000559d		NuidFltr.sys
    GEARAspiWDM	fffff880`0742a000	fffff880`07437000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
    ASACPI.sys
    ctac32k.sys
    yk62x64.sys
    NuidFltr.sys
    GEARAspiWDM.sys



    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\022612-49951-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.16841.amd64fre.win7_gdr.110622-1503
    Machine Name:
    Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e70
    Debug session time: Sun Feb 26 07:36:12.384 2012 (UTC - 7:00)
    System Uptime: 0 days 13:26:02.008
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 34, {50830, fffff880083ab768, fffff880083aafd0, fffff8000303146b}
    
    Probably caused by : ntkrnlmp.exe ( nt!PfCheckDeprioritizeFile+16b )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050830
    Arg2: fffff880083ab768
    Arg3: fffff880083aafd0
    Arg4: fffff8000303146b
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff880083ab768 -- (.exr 0xfffff880083ab768)
    ExceptionAddress: fffff8000303146b (nt!PfCheckDeprioritizeFile+0x000000000000016b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880083aafd0 -- (.cxr 0xfffff880083aafd0)
    rax=005c006500630069 rbx=0000000000000001 rcx=007600650044005c
    rdx=0f505c3adea72267 rsi=fffff8a013055140 rdi=0000000000000000
    rip=fffff8000303146b rsp=fffff880083ab9a0 rbp=0000000000000000
     r8=0000000000004000  r9=fffff8a013055140 r10=ffffffffffffffff
    r11=fffff80002e17c30 r12=0000000000000001 r13=00000000031b6478
    r14=0000000000000000 r15=0000000000000011
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!PfCheckDeprioritizeFile+0x16b:
    fffff800`0303146b 488b4108        mov     rax,qword ptr [rcx+8] ds:002b:00760065`00440064=????????????????
    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 fffff80002eae0e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!PfCheckDeprioritizeFile+16b
    fffff800`0303146b 488b4108        mov     rax,qword ptr [rcx+8]
    
    FAULTING_IP: 
    nt!PfCheckDeprioritizeFile+16b
    fffff800`0303146b 488b4108        mov     rax,qword ptr [rcx+8]
    
    BUGCHECK_STR:  0x34
    
    LAST_CONTROL_TRANSFER:  from fffff80002fac5fe to fffff8000303146b
    
    STACK_TEXT:  
    fffff880`083ab9a0 fffff800`02fac5fe : fffffa80`0ae0c910 fffff8a0`13055140 00000000`00000000 00000000`00000000 : nt!PfCheckDeprioritizeFile+0x16b
    fffff880`083aba10 fffff800`02c8f3b7 : 00000000`00000000 fffffa80`0be70920 00000000`00000000 00000000`00100000 : nt! ?? ::NNGAKEGL::`string'+0x18c56
    fffff880`083aba50 fffff800`02c66144 : 00000000`00000001 fffffa80`0bf56940 fffffa80`0ae0c900 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
    fffff880`083abae0 fffff800`02c69bdc : fffffa80`0ae0c910 00000000`00000000 fffffa80`0ae0c910 fffffa80`07af8900 : nt!CcDeleteSharedCacheMap+0x140
    fffff880`083abb50 fffff800`02c6a3ec : 00000000`10000000 fffff880`083abc58 00000000`00000000 00000000`00000000 : nt!CcWriteBehind+0x5bc
    fffff880`083abc00 fffff800`02c837e1 : fffffa80`06a20ee0 fffff880`01253270 fffff800`02e7d160 fffff880`00000000 : nt!CcWorkerThread+0x1c8
    fffff880`083abcb0 fffff800`02f166fa : 00000000`00000000 fffffa80`07af89b0 00000000`00000080 fffffa80`06a06040 : nt!ExpWorkerThread+0x111
    fffff880`083abd40 fffff800`02c54b46 : fffff880`02f64180 fffffa80`07af89b0 fffffa80`06a16040 fffff880`0125e534 : nt!PspSystemThreadStartup+0x5a
    fffff880`083abd80 00000000`00000000 : fffff880`083ac000 fffff880`083a6000 fffff880`083aad20 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!PfCheckDeprioritizeFile+16b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44
    
    STACK_COMMAND:  .cxr 0xfffff880083aafd0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!PfCheckDeprioritizeFile+16b
    
    BUCKET_ID:  X64_0x34_nt!PfCheckDeprioritizeFile+16b
    
    Followup: MachineOwner
    ---------
    This appears to be related to your memory or data corruption. I do note your .nfo file is corrupted, so you may have corruption of data on your system.

    Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

    • If you are overclocking any hardware, please stop.


    • Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
      1. Going to the Asus motherboard support site
        When you reach the website:
      2. Scroll down the page and click Utilities
      3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
      4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
      5. Download and install the driver.
      6. After installation is complete, verify that it installed correctly.
        • Click Start Menu
        • Click My Computer
        • Go to C:\WIndows\System32\drivers\
        • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)


      Thanks to JMH and zigzag3143 for the above information.
      You may not have to proceed with the following steps after this because your system may be stable after updating, but I do still recommend at the very least installing all Windows updates. I also recommend making sure the first four drivers in the list above are updated (ASACPI is the first, so this should already be done).

      The fifth driver may be part of iTunes and therefore cannot be updated, so do not worry about it unless you continue to have crashes, in which case you may want to uninstall iTunes with the steps in Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7 to test.


    • 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


    • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.


    • Install all Windows updates. I notice you do not have Service Pack 1 installed yet. Update to Service Pack 1 (SP1)
      Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH


    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.
      My Computer


  2. Posts : 57
    Windows 7 64 Bits
    Thread Starter
       #12

    Hello, I updated the first driver with any problem (ASACPI.SYS)

    I check on SoundBlaster website for newer driver for my SB0460 and it seem that I have the last driver... I don't know if I can find a driver newer then what I got on internet.

    For the 3rd driver... yk62x64 (Yukon Marvell etc) I checked my model (I have a BELAC report) and it was the model 88E8056 so I downloaded the driver on the site and unzip it. I checked how to update an existing driver... here how : To update the driver:

    1. On the desktop, right-click on MY COMPUTER.
    2. Select MANAGE.
    3. In the "Device Manager", double-click your adapter.
    4. Select DRIVER.
    5. Click UPDATE DRIVER...
    6. Follow the instructions given by the operating system to locate the
    driver.
    7. If the driver which is found to be the latest is not the one you want to
    install, select the check box "Install one of the other drivers".
    8. Click NEXT.
    9. From the driver list, select the driver to be installed.
    10. Click NEXT.
    11. If a message is displayed saying the driver is not digitally signed by
    Microsoft, click YES.
    12. Click FINISH to complete the installation.

    So as soon I choose "MANAGE" BANG......another blue screen so I post it to you.

    Thank..........
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #13

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\022612-34725-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.16841.amd64fre.win7_gdr.110622-1503
    Machine Name:
    Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e70
    Debug session time: Sun Feb 26 12:07:14.673 2012 (UTC - 7:00)
    System Uptime: 0 days 0:26:40.296
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffffa7fffffffea, 0, fffff80002cb1dcf, 7}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa7fffffffea, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cb1dcf, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000007, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb40e0
     fffffa7fffffffea 
    
    FAULTING_IP: 
    nt!MiMapPageInHyperSpaceWorker+1b
    fffff800`02cb1dcf 458a481a        mov     r9b,byte ptr [r8+1Ah]
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88003db6820 -- (.trap 0xfffff88003db6820)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000058000000000 rbx=0000000000000000 rcx=ffffffffffffffff
    rdx=fffff88003db6a40 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002cb1dcf rsp=fffff88003db69b8 rbp=0000058000000000
     r8=fffffa7fffffffd0  r9=fffff88003db6901 r10=0000000000000002
    r11=fffff88003db6990 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MiMapPageInHyperSpaceWorker+0x1b:
    fffff800`02cb1dcf 458a481a        mov     r9b,byte ptr [r8+1Ah] ds:6c70:fffffa7f`ffffffea=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cfb729 to fffff80002c7c5c0
    
    STACK_TEXT:  
    fffff880`03db66b8 fffff800`02cfb729 : 00000000`00000050 fffffa7f`ffffffea 00000000`00000000 fffff880`03db6820 : nt!KeBugCheckEx
    fffff880`03db66c0 fffff800`02c7a6ae : 00000000`00000000 ffffffff`ffffffff 00000000`00000200 fffff800`02c8109a : nt! ?? ::FNODOBFM::`string'+0x40ccb
    fffff880`03db6820 fffff800`02cb1dcf : fffff800`02cdd229 ffffffff`ffffffff 00000000`0016c3b8 fffffa80`071fd060 : nt!KiPageFault+0x16e
    fffff880`03db69b8 fffff800`02cdd229 : ffffffff`ffffffff 00000000`0016c3b8 fffffa80`071fd060 00000000`00000000 : nt!MiMapPageInHyperSpaceWorker+0x1b
    fffff880`03db69c0 fffff800`02f36b4a : fffff780`00000000 00000000`00000000 00000000`00000001 fffffa80`069a0f30 : nt! ?? ::FNODOBFM::`string'+0x17166
    fffff880`03db6a40 fffff800`02f3681b : fffffa80`071fd060 00000000`00000008 fffffa80`00000000 fffffa80`00000002 : nt!MmDeleteProcessAddressSpace+0x42
    fffff880`03db6a80 fffff800`02c81754 : 00000000`00000000 fffffa80`071fd060 fffffa80`071fd030 fffff800`0300a465 : nt!PspProcessDelete+0x177
    fffff880`03db6ae0 fffff800`02d821b9 : fffffa80`071fd060 fffffa80`075e8000 fffffa80`075e8ea8 fffffa80`075e8ea0 : nt!ObfDereferenceObject+0xd4
    fffff880`03db6b40 fffff800`030cdc7e : fffffa80`00000530 fffffa80`0768d000 fffffa80`071fd060 fffffa80`075e8ea8 : nt!MmFreeAccessPfnBuffer+0x29
    fffff880`03db6b70 fffff800`030ef2a0 : fffffa80`087b5b01 00000000`00000080 fffffa80`06a06040 fffff800`02e0a568 : nt!PfpFlushBuffers+0x23e
    fffff880`03db6c10 fffff800`02f1c6fa : ffffffff`ff676980 fffffa80`087b5b60 00000000`00000000 fffff800`02c74447 : nt!PfTLoggingWorker+0xe0
    fffff880`03db6d40 fffff800`02c5ab46 : fffff800`02df6e80 fffffa80`087b5b60 fffff800`02e04c40 fffff880`012412b4 : nt!PspSystemThreadStartup+0x5a
    fffff880`03db6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiMapPageInHyperSpaceWorker+1b
    fffff800`02cb1dcf 458a481a        mov     r9b,byte ptr [r8+1Ah]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiMapPageInHyperSpaceWorker+1b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiMapPageInHyperSpaceWorker+1b
    
    BUCKET_ID:  X64_0x50_nt!MiMapPageInHyperSpaceWorker+1b
    
    Followup: MachineOwner
    ---------
    Pointing to a memory issue. Proceed to the Memtest86+ step (or you can wait and run it tonight). It is important that it is run soon, though.

    Also continue with the other steps, testing stability after each by doing your normal routine.
      My Computer


  4. Posts : 57
    Windows 7 64 Bits
    Thread Starter
       #14

    You want me that i run memtest again even if last week i run it for 14 hrs and run 7 pass ? How long you want me to run it ?? Thank
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #15

    Memtest86+ sometimes does not throw errors the first few times it is run. It should be run seven passes each time it is run, and it sometimes needs to be run more than a few times to determine whether there are errors in the modules. I have heard of people needing to run it for 20+ passes before an error is found.



    If you do not want to run it again for a long period of time, there is one other option: Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

    This will give us an idea of what your system makeup is so we can provide different steps for RAM troubleshooting.
      My Computer


  6. Posts : 57
    Windows 7 64 Bits
    Thread Starter
       #16

    writhziden said:
    Memtest86+ sometimes does not throw errors the first few times it is run. It should be run seven passes each time it is run, and it sometimes needs to be run more than a few times to determine whether there are errors in the modules. I have heard of people needing to run it for 20+ passes before an error is found.



    If you do not want to run it again for a long period of time, there is one other option: Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

    This will give us an idea of what your system makeup is so we can provide different steps for RAM troubleshooting.
    Hello again, here my screenshots and I might start another MEMTEST but I have some work to do also so... If I start i I will try to keep it for 20 hrs :)
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #17

    So based on the modules you have, what I would recommend is running in sets of two and seeing if one set works better than another set with Windows running. Try to narrow down which module might be bad (if there is a bad module). If a set of two works in two slots and does not cause crashes, try the other pair of slots to see if you might have bad slots. Then test one at a time in any possibly bad slots with a known good module.

    Make sure to use safe ESD practices as laid out in post #11.
      My Computer


  8. Posts : 57
    Windows 7 64 Bits
    Thread Starter
       #18

    writhziden said:
    So based on the modules you have, what I would recommend is running in sets of two and seeing if one set works better than another set with Windows running. Try to narrow down which module might be bad (if there is a bad module). If a set of two works in two slots and does not cause crashes, try the other pair of slots to see if you might have bad slots. Then test one at a time in any possibly bad slots with a known good module.

    Make sure to use safe ESD practices as laid out in post #11.
    Ok, so if I try to translate (I'm speak french heh) You want me to remove 2 module from there slot.. (I will remove the last one I bought) and run MEMTEST for at least 7 pass... ? to see if I have error... and you said I might have memory slot defect on my motherboard ?
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #19

    symetric said:
    Ok, so if I try to translate (I'm speak french heh) You want me to remove 2 module from there slot.. (I will remove the last one I bought) and run MEMTEST for at least 7 pass... ? to see if I have error... and you said I might have memory slot defect on my motherboard ?
    I'm saying you may have a bad module, a bad slot, or both. You will need to test all modules and all slots. Doing it in sets of two will be faster than doing it with one module at a time.

    Also, I did not realize you had mixed and matched RAM (yes they are basically the same, but they were obviously bought at two different times since one set has a trailing DHX on it). This can cause instability, even if the modules are the same type and the same timings. Buying RAM at two different times can cause crashes on systems.
    Last edited by writhziden; 26 Feb 2012 at 21:11. Reason: Different RAM sets...
      My Computer


  10. Posts : 57
    Windows 7 64 Bits
    Thread Starter
       #20

    Ok no problem. I just remove 2 module in slot 1 and 3 (it is the last memory that I bought)

    I updated the Yukon Marvell without any problem for now...no BSOD

    Do you want me to delete the dump in my minidump dir ?
      My Computer


 
Page 2 of 7 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About 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 04:52.
Find Us