BSOD after logon

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate x64
       #1

    BSOD after logon


    hi
    i need help
    i don't know exactly what i did but i keep getting a BSOD everytime i log in since yesterday
    any account i log into gets a BSOD after a few seconds
    i've tried to do a system registry restore, but that didn't work
    i booted from hiren's boot disk (Hiren's BootCD Fan & Discussion Platform) a did some virus checking using avira
    i also used ccleaner
    i've tried everything i could think of but none of them worked...
    can someone please help?
    i zipped up a few minidumps that were created and attached them
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Please provide this information: https://www.sevenforums.com/crashes-d...tructions.html

    OLDER DRIVERS PRESENT IN THE DUMP FILES
    - Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Please feel free to post back about any drivers that you are having difficulty locating.
    - Windows Update exceptions may be noted below for Windows drivers:
    Code:
    
    amdxata.sys      Tue May 19 13:56:59 2009 (4A12F2EB)
    VClone.sys       Sun Aug 09 17:25:45 2009 (4A7F3ED9)
    lvuvc64.sys      Tue Nov 09 21:37:14 2010 (4CDA055A)
    ElbyCDIO.sys     Fri Jan 01 12:20:27 2010 (4B3E2EDB)
    Rt64win7.sys     Tue Nov 30 01:01:28 2010 (4CF49338)
    L8042Kbd.sys     Wed Jun 17 12:50:43 2009 (4A391EE3)
    nvhda64v.sys     Tue Sep 07 16:08:40 2010 (4C869BC8)
    nvlddmkm.sys     Sat Oct 16 13:12:46 2010 (4CB9DD0E)
    nvBridge.kmd     Sat Oct 16 13:06:16 2010 (4CB9DB88)
    RTKVHD64.sys     Mon Feb 22 04:26:08 2010 (4B824DB0)
    LHidFilt.Sys     Wed Jun 17 12:49:39 2009 (4A391EA3)
    LMouFilt.Sys     Wed Jun 17 12:49:43 2009 (4A391EA7)
    lvrs64.sys       Tue Nov 09 21:36:46 2010 (4CDA053E)
    ALSysIO64.sys    Sun Apr 19 15:41:04 2009 (49EB7E50)
    PxHlpa64.sys     Tue Jun 23 19:16:35 2009 (4A416253)
    Rt64win7.sys     Thu Aug 20 12:05:06 2009 (4A8D7432)
    HECIx64.sys      Thu Sep 17 15:54:16 2009 (4AB293E8)
    vmnetadapter.sys Mon Aug 10 08:04:53 2009 (4A800CE5)
    VMNET.SYS        Mon Aug 10 08:04:50 2009 (4A800CE2)
    GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
    VMkbd.sys        Thu Nov 11 15:35:18 2010 (4CDC5386)
    vmci.sys         Thu Nov 11 14:11:58 2010 (4CDC3FFE)
    hcmon.sys        Thu Nov 11 14:44:25 2010 (4CDC4799)
    vmnetbridge.sys  Mon Aug 10 08:05:58 2009 (4A800D26)
    vmx86.sys        Thu Nov 11 16:23:08 2010 (4CDC5EBC)
    vmnetuserif.sys  Thu Nov 11 14:59:16 2010 (4CDC4B14)
    vstor2-ws60.sys  Thu Aug 19 16:28:39 2010 (4C6D93F7)
    LVPr2M64.sys     Fri May 07 21:38:16 2010 (4BE4C088)
    

    http://www.carrona.org/dvrref.html#amdxata.sys
    http://www.carrona.org/dvrref.html#VClone.sys
    http://www.carrona.org/dvrref.html#lvuvc64.sys
    http://www.carrona.org/dvrref.html#ElbyCDIO.sys
    http://www.carrona.org/dvrref.html#Rt64win7.sys
    http://www.carrona.org/dvrref.html#L8042Kbd.sys
    http://www.carrona.org/dvrref.html#nvhda64v.sys
    http://www.carrona.org/dvrref.html#nvlddmkm.sys
    http://www.carrona.org/dvrref.html#nvBridge.kmd
    http://www.carrona.org/dvrref.html#RTKVHD64.sys
    http://www.carrona.org/dvrref.html#LHidFilt.Sys
    http://www.carrona.org/dvrref.html#LMouFilt.Sys
    http://www.carrona.org/dvrref.html#lvrs64.sys
    http://www.carrona.org/dvrref.html#ALSysIO64.sys
    http://www.carrona.org/dvrref.html#PxHlpa64.sys
    http://www.carrona.org/dvrref.html#Rt64win7.sys
    http://www.carrona.org/dvrref.html#HECIx64.sys
    http://www.carrona.org/dvrref.html#vmnetadapter.sys
    http://www.carrona.org/dvrref.html#VMNET.SYS
    http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
    http://www.carrona.org/dvrref.html#VMkbd.sys
    http://www.carrona.org/dvrref.html#vmci.sys
    http://www.carrona.org/dvrref.html#hcmon.sys
    http://www.carrona.org/dvrref.html#vmnetbridge.sys
    http://www.carrona.org/dvrref.html#vmx86.sys
    http://www.carrona.org/dvrref.html#vmnetuserif.sys
    http://www.carrona.org/dvrref.html#vstor2-ws60.sys
    http://www.carrona.org/dvrref.html#LVPr2M64.sys
    If that doesn't fix things, then try running Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 15:17:05.698 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:51.822
    Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  WerFault.exe
    FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
    Bugcheck code 0000000A
    Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`03ab5591
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 15:08:05.732 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:30.856
    Probably caused by : win32k.sys ( win32k!GreAcquireSemaphore+1c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  taskhost.exe
    FAILURE_BUCKET_ID:  X64_0xA_win32k!GreAcquireSemaphore+1c
    Bugcheck code 0000000A
    Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`03a9aa83
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 14:54:15.033 2011 (UTC - 5:00)
    System Uptime: 0 days 0:03:05.157
    Probably caused by : ntkrnlmp.exe ( nt!ObpDeleteNameCheck+2a )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  KHALMNPR.Exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpDeleteNameCheck+2a
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`03dc157a fffff880`029f9cd0 00000000`00000000
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 14:46:28.402 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:11.902
    Probably caused by : ataport.SYS ( ataport!_NULL_IMPORT_DESCRIPTOR <PERF> (ataport+0x29000)+0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  userinit.exe
    FAILURE_BUCKET_ID:  X64_0x50_ataport!_NULL_IMPORT_DESCRIPTOR__PERF__(ataport+0x29000)+0
    Bugcheck code 00000050
    Arguments fffff880`01110000 00000000`00000008 fffff880`01110000 00000000`00000000
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 14:43:53.027 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:51.151
    Probably caused by : memory_corruption ( nt!MiBadRefCount+4f )
    BUGCHECK_STR:  0x4E_9a
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID:  X64_0x4E_9a_nt!MiBadRefCount+4f
    Bugcheck code 0000004E
    Arguments 00000000`0000009a 00000000`00000000 00000000`00000000 00000000`00000000
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 14:36:10.071 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:04.195
    Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  WerFault.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiTryUnwaitThread+28
    Bugcheck code 0000001E
    Arguments ffffffff`c0000005 fffff800`030824d8 00000000`00000000 ffffffff`ffffffff
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 13:00:44.652 2011 (UTC - 5:00)
    System Uptime: 0 days 0:04:25.776
    Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  regsvr32.exe
    FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
    Bugcheck code 0000000A
    Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`030b4591
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 12:53:12.081 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:48.205
    Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
    Bugcheck code 0000000A
    Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`030b0591
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 08:12:49.282 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:08.782
    Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
    Bugcheck code 0000000A
    Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`02463591
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 08:09:23.963 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:21.087
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  taskhost.exe
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
    Bugcheck code 0000000A
    Arguments 00000000`00000300 00000000`00000002 00000000`00000000 fffff800`030e0c06
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Mar  8 08:06:48.944 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:20.068
    Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
    Bugcheck code 0000000A
    Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`030b3591
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    SystemManufacturer = MSI
    SystemProductName = MS-7636
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #3

    hi, thanks for the quick replay
    i forgot to mention i tried to recover from the installation discs
    but all the system restore points i had were useless
    the error checking didn't work either
    nore did scan disk
    also i can't log into safe mode
    the BSOD appears right after logging in there as well
    so i'm left with booting from USB's
    i have Hiren's Bootable CD on a bootable USB
    which can then boot into...
    mini linux or mini windows xp
    i also have a usb of ubuntu 10.10
    what should i do and how should i do it with the things i have?
    how do i repair the drivers from outside the system?
    Last edited by PropheX31; 09 Mar 2011 at 09:12. Reason: typo
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    Sorry, I have eye problems and missed the fact that you can't get into Windows for very long.
    Start with these free bootable diagnostics:
    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)
    Did you also try Startup Repair from the installation disk? It should function even though there's no System Restore points - and it may fix the boot up issues. Startup Repair
      My Computer


  5. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #5

    sorry for the late replay
    there was a large earthquake where i live (japan)
    i'll get right to it with the diagnostics and post the outcome
      My Computer


  6. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #6

    also i tried startup repair from the installation disc, but that didnt help
      My Computer


  7. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #7

    i tried both memory and hdd diagnostics
    for memory, i booted hiren's boot cd and loaded the mem86+ checker
    it came out okay
    for hdd i again booted hiren's boot cd, loaded 3 different hd checkers, they all came out ok
    just in case, i went to hitachi's homepage, downloaded their hdd checker, burned it and booted it
    it came out okay too...
    help me~
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Try Driver Verifier:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session  Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  9. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #9

    how to i use driver verifier from outside windows 7?
    i can't log in to my main windows 7, not even in safe mode
    i CAN boot hiren's boot cd and log in through a stiped down windows xp
    what do i do from there?
      My Computer


  10. Posts : 5,705
    Win7 x64 + x86
       #10

    When you did the virus checking with Hiren's - did it find any viruses? If it found the TDSS virus, there's a couple of necessary steps:
    - run Startup Repair 3 times
    - if that doesn't permit booting, run these 2 commands in the Startup Repair Command Prompt:

    Code:
    bootrec /fixmbr
    bootrec /fixboot
    Type each one in and press Enter. Answer "Y" (for Yes) when it asks if you're sure.

    If that doesn't fix it, then it's likely that your Windows installation is hosed. Try getting into Safe Mode with Command Prompt (different from Startup Repair Command Prompt). If you can get in there, type

    verifier /standard /all
    And press Enter

    Try to get into Windows and let it crash. Do this 3 or 4 times (to ensure that we have a couple of BSOD memory dumps to look at). Then type go back to the Safe Mode Command Prompt and type this:

    Code:
    verifier /reset
    And press Enter. This'll shut off Driver Verifier and we'll see what we can gather from those dumps.

    Since this is likely to point to your Windows installation, I'd suggest getting ready for a format and reinstall of Windows by backing up all of your data.

    Good luck!
      My Computer


 
Page 1 of 2 12 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 11:55.
Find Us