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 on new components need help finding out why?

16 Feb 2012   #1
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSOD on new components need help finding out why?

x64 windows 7 home premium
Its the first OS on the hard drive
It is purchased from a retailer
The hardware is all new arrived on Wednesday the 15th of February

Hi I recently have done a mass upgrade to my system and I have been getting BSOD and I'm not sure why? I have heard it may be a memory problem , but at first I believed it to be power issues but having gotten a 600w power supply which will happily run all components, but there was no luck and I still am getting them. If anyone could analyse this for me I would be very grateful, Cheers


My System SpecsSystem Spec
.
17 Feb 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Documents\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\021612-43181-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c53670
Debug session time: Thu Feb 16 11:36:21.150 2012 (GMT-7)
System Uptime: 0 days 0:22:55.726
Loading Kernel Symbols
.............................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800730e028, b6004000, 8f000175}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800730e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000008f000175, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00b9cc68 fffff880`06d3a72d : 00000000`00000001 fffffa80`07739e90 ffffffff`fffffffe 00000000`000058bd : 0xfffff880`06d3a6e4
fffff800`00b9cc70 00000000`00000001 : fffffa80`07739e90 ffffffff`fffffffe 00000000`000058bd 00000000`00000001 : 0xfffff880`06d3a72d
fffff800`00b9cc78 fffffa80`07739e90 : ffffffff`fffffffe 00000000`000058bd 00000000`00000001 fffff800`02a944a9 : <Unloaded_Unknown_Module_00000000`00000000>+0x1
fffff800`00b9cc80 ffffffff`fffffffe : 00000000`000058bd 00000000`00000001 fffff800`02a944a9 00000000`002cb479 : 0xfffffa80`07739e90
fffff800`00b9cc88 00000000`000058bd : 00000000`00000001 fffff800`02a944a9 00000000`002cb479 fffffa80`0773b9d0 : 0xffffffff`fffffffe
fffff800`00b9cc90 00000000`00000001 : fffff800`02a944a9 00000000`002cb479 fffffa80`0773b9d0 fffff800`02c00e80 : 0x58bd
fffff800`00b9cc98 fffff800`02a944a9 : 00000000`002cb479 fffffa80`0773b9d0 fffff800`02c00e80 00000000`00000000 : <Unloaded_Unknown_Module_00000000`00000000>+0x1
fffff800`00b9cca0 fffff800`02a8293c : fffff800`02c00e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN

BUCKET_ID:  X64_0x124_AuthenticAMD__UNKNOWN

Followup: MachineOwner
---------
Start with Stop 0x124 - what it means and what to try and post back if you need further help. In the course of that thread, the following may be useful.
  • If you are overclocking any hardware, please stop.


  • Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.

    Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in Screenshots and Files - Upload and Post in Seven Forums.


  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.


  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.


  • 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.



Uninstall Gigabyte Easy Tune 6 (known issues w/Win7) and Gigabyte Easy Saver - mobo power utility (issues with some systems causing crashes).



Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.



I also note that you use a TP-LINK Wireless USB Adapter. Wireless USB adapters are inherently unreliable. The drivers often are outdated, and they do not have adequate power to be stable. We recommend replacing with a wireless adapter PCI card instead.
My System SpecsSystem Spec
18 Feb 2012   #3
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Thank you for the reply and the detailed info! I will get back to you on how it goes!
My System SpecsSystem Spec
.

24 Feb 2012   #4
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Hmmm still no luck although I still need to do memtest but these are my more recent ones which I think are registering different things, at the moment I have my processor downclocked from 3000 to 2900 just because it seems to make it a lot more stable, so please once again take a glance over,r eally don't know what to do, cheers
My System SpecsSystem Spec
24 Feb 2012   #5
writhziden

Windows 7 Home Premium 64 Bit
 
 

Antivirus software:
Code:
avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1296	8	200	1380	25/02/2012 01:05	6.0.1367.0	43.72 KB (44,768 bytes)	15/02/2012 17:21
avastui.exe	c:\program files\avast software\avast\avastui.exe	3692	8	200	1380	25/02/2012 01:05	6.0.1367.0	3.57 MB (3,744,552 bytes)	15/02/2012 17:21


Possible unstable device:
Code:
                           [01]: TP-LINK Wireless USB Adapter


Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022512-29562-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c47670 Debug session time: Fri Feb 24 18:04:48.154 2012 (UTC - 7:00) System Uptime: 0 days 0:00:11.746 Loading Kernel Symbols ................................................ Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa80073ba8f8, 0, 0} Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa80073ba8f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_AuthenticAMD CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`031bd6f0 fffff800`02cc4c59 : fffffa80`073ba8d0 fffffa80`06427680 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`031bdc10 fffff800`02ba4f57 : fffffa80`073ba8d0 fffff800`02c1f2b8 fffffa80`06427680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`031bdc40 fffff800`02b0c5d5 : fffff800`02c80ae0 00000000`00000001 fffffa80`073b9820 fffffa80`06427680 : nt!WheapProcessWorkQueueItem+0x57 fffff880`031bdc80 fffff800`02a89001 : fffff880`00c3be00 fffff800`02b0c5b0 fffffa80`06427600 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`031bdcb0 fffff800`02d19fee : 00000000`00000000 fffffa80`06427680 00000000`00000080 fffffa80`0639d9e0 : nt!ExpWorkerThread+0x111 fffff880`031bdd40 fffff800`02a705e6 : fffff880`02f64180 fffffa80`06427680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd220 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\021912-15459-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4f670 Debug session time: Sun Feb 19 13:18:10.462 2012 (UTC - 7:00) System Uptime: 0 days 3:30:12.038 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {28, 2, 0, fffff880043475cd} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+35 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000028, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880043475cd, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb9100 0000000000000028 CURRENT_IRQL: 2 FAULTING_IP: USBPORT!USBPORT_Xdpc_iSetState+35 fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff88002f22d10 -- (.trap 0xfffff88002f22d10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880043475cd rsp=fffff88002f22ea0 rbp=fffffa8007f06a00 r8=fffffa80075bd1a0 r9=0000000000000000 r10=00000000ffffffff r11=fffffa80075bd1a0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc USBPORT!USBPORT_Xdpc_iSetState+0x35: fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9 ds:ffff:00000000`00000028=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a861e9 to fffff80002a86c40 STACK_TEXT: fffff880`02f22bc8 fffff800`02a861e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02f22bd0 fffff800`02a84e60 : fffffa80`08cd1340 fffffa80`075bd101 00000000`00000002 fffffa80`075bdd28 : nt!KiBugCheckDispatch+0x69 fffff880`02f22d10 fffff880`043475cd : fffffa80`0771e418 00000000`00000022 00000000`00000000 00000000`ffffffff : nt!KiPageFault+0x260 fffff880`02f22ea0 fffff880`04347f89 : fffffa80`075bd050 00000000`00000000 fffffa80`075bdd02 fffffa80`075bdd28 : USBPORT!USBPORT_Xdpc_iSetState+0x35 fffff880`02f22ed0 fffff800`02a920ac : fffff880`009ea180 fffffa80`075bdd28 fffffa80`075bdd40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`02f22f00 fffff800`02a89765 : 00000000`00000000 fffffa80`07fc2b60 00000000`00000000 fffff880`04347db0 : nt!KiRetireDpcList+0x1bc fffff880`02f22fb0 fffff800`02a8957c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`02badff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: USBPORT!USBPORT_Xdpc_iSetState+35 fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iSetState+35 FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c08 FAILURE_BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35 BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35 Followup: MachineOwner ---------
  1. Still a stop 0x124.
  2. A USB related crash. Probably due to your network wireless USB adapter.

Stop 0x124 - what it means and what to try is still recommended. What were the results of the stress tests? Definitely do the RAM tests, as well. Underclocking your CPU may also mean the RAM settings are not configured properly.

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.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability



You could try USB Driver - General Fix for Problems to fix any USB driver related problems.

You could also try Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English) (works for all computers, not just HP Pavilions) to reset the USB ports themselves in case your USB ports entered a different power state to protect the system from a power surge.
My System SpecsSystem Spec
25 Feb 2012   #6
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Could the fact I have my wireless adapter attached to a USB extension? So basically PC -> usb extension -> wireless adapters lead -> Usb adapter ?
My System SpecsSystem Spec
25 Feb 2012   #7
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

My screenshots are here also
My System SpecsSystem Spec
25 Feb 2012   #8
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Mikewix View Post
Could the fact I have my wireless adapter attached to a USB extension? So basically PC -> usb extension -> wireless adapters lead -> Usb adapter ?
As I said in my previous post, USB does not provide a very stable solution for wireless devices. I would guess with your current setup, it is even more of an issue to provide the adequate power for the adapter.

Quote   Quote: Originally Posted by Mikewix View Post
My screenshots are here also
How comfortable are you with changing settings in the BIOS?
My System SpecsSystem Spec
25 Feb 2012   #9
Mikewix

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I know basic stuff if you tell me clearly I will be fine
My System SpecsSystem Spec
25 Feb 2012   #10
writhziden

Windows 7 Home Premium 64 Bit
 
 

Alright, in order to better help guide you, I will need you to fill out your system specs. You can use this guide for filling them out: System Info - See Your System Specs
My System SpecsSystem Spec
Reply

 BSOD on new components need help finding out why?




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD after upgrading components
Earlier this week I have done a small upgrade to my PC which consisted of a new Motherboard, CPU and RAM. The Graphics card (Nvidia GTX260) is the same. Shortly after upgrading all of this I noticed Chrome would repeatedly crash on any website at all, after playing a game I usually play, I've...
BSOD Help and Support
New components, random BSOD and reboots
Hello. I've been trying to google my problem and now I think it is time to let people with more experience to look at what might be wrong with my computer. Actual problem is that I've been having quite random blue screens, reboots and even complete system hangings for past few weeks, after I...
BSOD Help and Support
New components - BSOD flashes for 1 second - booting from usb
Hi all I recently upgraded my CPU, PSU, RAM and motherboard and kept my original hard drive and dvd drive which are about 8 years old - still working though. I have been told that I am getting the error as by keeping the original hard drive it would require a clean install of windows. I plan to...
Installation & Setup
BSOD maybe due to new components?
Hi, i recently had a new graphics card, processor and power supply fitted to my pc. The pc itself was only 2 months old. After 2 days of using it, i got a BSOD whilst gaming. It happened again about 2 hours later. I believe all my drivers are up to date, i tried to run windows memory diagnostic...
BSOD Help and Support
BSOD Win7 X64 error! changed major components and still BSOD!
Windows 7 x64 Windows 7 is the original installed OS Retail Vers. System is a year old OS install is less than 2 Months old I am having issues trying to narrow down what is causing my computer to keep crashing. I have just about changed every single part in my computer and am going nutts....
BSOD Help and Support
BSOD while gaming after new components installed
I have played 2 different games and both have locked up after a few minutes of playing. Never had a problem before with my old setup. New component's... BFG 1000 watt Power supply 2 ATI 5770's in crossfire mode This was the information windows gave me after rebooting... Problem...
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 05:29.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App