Several BSOD a day, The bugcheck was: 0x0000001e

Page 2 of 2 FirstFirst 12

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

    Code:
    1. Loading Dump File [D:\Kingston\BSODDmpFiles\Lauren17\Windows_NT6_BSOD_jcgriff2\022012-17706-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50 Debug session time: Mon Feb 20 12:14:17.466 2012 (GMT-7) System Uptime: 0 days 0:13:58.229 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002ebf110, fffff88005d7f120, 0} Probably caused by : memory_corruption ( nt!MiGetPreviousNode+10 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002ebf110, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88005d7f120, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!MiGetPreviousNode+10 fffff800`02ebf110 488b10 mov rdx,qword ptr [rax] CONTEXT: fffff88005d7f120 -- (.cxr 0xfffff88005d7f120) rax=ffbffa800a0a0240 rbx=fffffa800a86b010 rcx=fffffa800a86b010 rdx=0000000000000a70 rsi=fffffa8009e7c750 rdi=fffffa800a163060 rip=fffff80002ebf110 rsp=fffff88005d7fb08 rbp=0000000000000000 r8=0000000000000000 r9=00000460006c0001 r10=fffff800031a51fc r11=00000000003156fc r12=000000000012b000 r13=0000000000000000 r14=0000000000b9afff r15=0000000000a70000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!MiGetPreviousNode+0x10: fffff800`02ebf110 488b10 mov rdx,qword ptr [rax] ds:002b:ffbffa80`0a0a0240=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800031a4db2 to fffff80002ebf110 STACK_TEXT: fffff880`05d7fb08 fffff800`031a4db2 : 00000000`0023fd00 fffffa80`09e7c750 fffffa80`0a163030 fffff8a0`01079300 : nt!MiGetPreviousNode+0x10 fffff880`05d7fb10 fffff800`031a525b : 00000000`00000000 00000000`00a70000 fffffa80`00000001 00000000`00000401 : nt!MiUnmapViewOfSection+0x112 fffff880`05d7fbd0 fffff800`02e8e153 : fffffa80`0a163060 fffff880`05d7fca0 fffffa80`09e7c750 fffffa80`06d12ca0 : nt!NtUnmapViewOfSection+0x5f fffff880`05d7fc20 00000000`7724015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02c5fa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7724015a FOLLOWUP_IP: nt!MiGetPreviousNode+10 fffff800`02ebf110 488b10 mov rdx,qword ptr [rax] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiGetPreviousNode+10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 STACK_COMMAND: .cxr 0xfffff88005d7f120 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetPreviousNode+10 BUCKET_ID: X64_0x3B_nt!MiGetPreviousNode+10 Followup: MachineOwner ---------
    2. Loading Dump File [D:\Kingston\BSODDmpFiles\Lauren17\Windows_NT6_BSOD_jcgriff2\022012-18439-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50 Debug session time: Mon Feb 20 00:07:50.915 2012 (GMT-7) System Uptime: 0 days 0:37:15.461 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffff, 0, 1, fffff80002cf70de} Probably caused by : afd.sys ( afd!AfdAllocateMdlChain32+fa ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffff, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002cf70de, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d0e0 ffffffffffffffff CURRENT_IRQL: 0 FAULTING_IP: nt!MmProbeAndLockPages+3ae fffff800`02cf70de 4823f0 and rsi,rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: swtor.exe TRAP_FRAME: fffff880086565d0 -- (.trap 0xfffff880086565d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000fffffffff rbx=0000000000000000 rcx=fffff6fb7dbed000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cf70de rsp=fffff88008656760 rbp=fffff88008656ca0 r8=fffff6fb40003d60 r9=0000000000000002 r10=fffff6fb7da00018 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy nt!MmProbeAndLockPages+0x3ae: fffff800`02cf70de 4823f0 and rsi,rax Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cd6469 to fffff80002cd6f00 STACK_TEXT: fffff880`08656488 fffff800`02cd6469 : 00000000`0000000a ffffffff`ffffffff 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx fffff880`08656490 fffff800`02cd50e0 : 00000000`00000001 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`086565d0 fffff800`02cf70de : 00000000`00000002 00000000`00000102 00000000`00000020 00000000`00000020 : nt!KiPageFault+0x260 fffff880`08656760 fffff880`02bac4ba : fffffa80`06d19180 00000000`00000801 00000000`00000001 00000000`00000002 : nt!MmProbeAndLockPages+0x3ae fffff880`08656870 fffff880`02ba9df4 : fffffa80`00000800 00000000`0d35f3b4 fffffa80`00000001 fffff800`00000001 : afd!AfdAllocateMdlChain32+0xfa fffff880`08656900 fffff800`02fef3a7 : fffffa80`09f514c0 fffffa80`0ab20d40 00000000`00000000 fffffa80`00000020 : afd! ?? ::GFJBLGFE::`string'+0xeecc fffff880`08656a10 fffff800`02fefc06 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`e6e80e70 : nt!IopXxxControlFile+0x607 fffff880`08656b40 fffff800`02cd6153 : fffffa80`06da7b60 fffff880`08656ca0 00000000`0d07e228 fffff880`08656c20 : nt!NtDeviceIoControlFile+0x56 fffff880`08656bb0 00000000`75492dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0d07eb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75492dd9 STACK_COMMAND: kb FOLLOWUP_IP: afd!AfdAllocateMdlChain32+fa fffff880`02bac4ba 4d892f mov qword ptr [r15],r13 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: afd!AfdAllocateMdlChain32+fa FOLLOWUP_NAME: MachineOwner MODULE_NAME: afd IMAGE_NAME: afd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184 FAILURE_BUCKET_ID: X64_0xA_afd!AfdAllocateMdlChain32+fa BUCKET_ID: X64_0xA_afd!AfdAllocateMdlChain32+fa Followup: MachineOwner ---------
    Update to Service Pack 1 (SP1)
    Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH



    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
      My Computer


  2. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #12

    I reinstalled windows and I am still getting BSOD:
    Here is the mini dump file.


    *******************************************************************************
    * *
    * 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: ffffffffffffffad, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff8800171cc13, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
    ffffffffffffffad

    CURRENT_IRQL: 2

    FAULTING_IP:
    tcpip!IpFlcReceivePackets+1b3
    fffff880`0171cc13 00488d add byte ptr [rax-73h],cl

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: fffff88006ef9120 -- (.trap 0xfffff88006ef9120)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000020 rbx=0000000000000000 rcx=ffffffffffffffff
    rdx=fffffa800aa8fca0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800171cc13 rsp=fffff88006ef92b0 rbp=0000000000000000
    r8=0000000000000001 r9=0000000000000001 r10=0000000000000001
    r11=0000000000000800 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    tcpip!IpFlcReceivePackets+0x1b3:
    fffff880`0171cc13 00488d add byte ptr [rax-73h],cl ds:ffffffff`ffffffad=??
    Resetting default scope

    MISALIGNED_IP:
    tcpip!IpFlcReceivePackets+1b3
    fffff880`0171cc13 00488d add byte ptr [rax-73h],cl

    LAST_CONTROL_TRANSFER: from fffff80002e931e9 to fffff80002e93c40

    STACK_TEXT:
    fffff880`06ef8fd8 fffff800`02e931e9 : 00000000`0000000a ffffffff`ffffffad 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`06ef8fe0 fffff800`02e91e60 : fffffa80`079a3000 fffff880`0171fd3a 00000000`00000000 00000000`133057a1 : nt!KiBugCheckDispatch+0x69
    fffff880`06ef9120 fffff880`0171cc13 : 00000000`00000001 fffffa80`079a3000 fffff880`0183f9a0 00000000`08875b01 : nt!KiPageFault+0x260
    fffff880`06ef92b0 fffff880`0171c6a2 : fffffa80`0887b4f0 fffffa80`0aa8fca0 fffffa80`08875b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x1b3
    fffff880`06ef94b0 fffff880`0171bb3a : fffffa80`08875ba0 fffff880`06ef95e0 fffffa80`08875ba0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`06ef9590 fffff800`02ea0618 : fffffa80`0aa8fca0 00000000`00004800 fffffa80`07c84660 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`06ef95e0 fffff880`0171c202 : fffff880`0171ba60 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`06ef96c0 fffff880`015a60eb : fffffa80`08875460 00000000`00000000 fffffa80`0926b1a0 fffffa80`0926b1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`06ef9730 fffff880`0156fad6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`06ef97a0 fffff880`01537a3e : fffffa80`0926b1a0 00000000`00000002 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`06ef9c20 fffff880`01537d33 : fffffa80`0926b1a0 fffffa80`0926b1a0 00000000`00000000 fffffa80`0926c300 : ndis!ndisDoPeriodicReceivesIndication+0x14e
    fffff880`06ef9c80 fffff880`01521f3d : 00000000`00010302 00000000`00000002 00000000`00000000 fffffa80`0926c388 : ndis!ndisPeriodicReceivesWorker+0x63
    fffff880`06ef9cb0 fffff800`0312efee : 88a7e695`00000001 fffffa80`07c84660 00000000`00000080 88a7e695`e82c563d : ndis!ndisReceiveWorkerThread+0x1bd
    fffff880`06ef9d40 fffff800`02e855e6 : fffff880`009e9180 fffffa80`07c84660 fffffa80`08391b60 88a7e695`e82c563d : nt!PspSystemThreadStartup+0x5a
    fffff880`06ef9d80 00000000`00000000 : fffff880`06efa000 fffff880`06ef4000 fffff880`06ef9a00 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    tcpip!IpFlcReceivePackets+1b3
    fffff880`0171cc13 00488d add byte ptr [rax-73h],cl

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: tcpip!IpFlcReceivePackets+1b3

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: X64_IP_MISALIGNED

    BUCKET_ID: X64_IP_MISALIGNED

    Followup: MachineOwner
      My Computer


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

    What antivirus are you running? I see a lot of network related items on the stack.
      My Computer


  4. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #14

    At the moment I am not using an anti virus because I just reinstalled windows a few days ago. I was nervous to install microsoft security essentials because I was afraid that was causing the issue. But since I am still getting BSOD while playing star wars I guess I can rule that out. I just got another BSOD a few min ago...this one is different then the last. Is it possible my mother board went bad?

    Attached is a recent health report and the minidumps.

    Thanks in Advance!
      My Computer


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

    Suspect device for previous crash:
    Code:
                                     802.11n USB Wireless LAN Card
                                     Connection Name: Wireless Network Connection
                                     DHCP Enabled:    Yes
    USB wireless adapters are inherently unstable. USB does not provide enough power for these devices to work properly. We recommend using an actual wireless PCI card rather than a USB wireless dongle. USB wireless is a common cause of crashes reported on these forums.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\Lauren17\Windows_NT6_BSOD_jcgriff2\022312-18252-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
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03048670
    Debug session time: Thu Feb 23 16:11:38.792 2012 (UTC - 7:00)
    System Uptime: 0 days 15:56:38.010
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80002ea81ce, fffff8800b7bbc20, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!RtlGetExtendedContextLength+62 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002ea81ce, Address of the instruction which caused the bugcheck
    Arg3: fffff8800b7bbc20, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!RtlGetExtendedContextLength+62
    fffff800`02ea81ce 41ba04000000    mov     r10d,4
    
    CONTEXT:  fffff8800b7bbc20 -- (.cxr 0xfffff8800b7bbc20)
    rax=0000000000000000 rbx=000000000001003f rcx=0000000000000000
    rdx=0000000000000001 rsi=000000000001003f rdi=fffff8800b7bc664
    rip=fffff80002ea81ce rsp=fffff8800b7bc600 rbp=fffff8800b7bc660
     r8=fffff8800b7bc640  r9=0000000000010040 r10=fffff8800b7bc660
    r11=00000000000002cc r12=000000000c3ddb01 r13=00000000000002cc
    r14=fffffffffffffffe r15=fffffa8007302060
    iopl=0         nv up ei pl zr na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010247
    nt!RtlGetExtendedContextLength+0x62:
    fffff800`02ea81ce 41ba04000000    mov     r10d,4
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  swtor.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ea81ce
    
    STACK_TEXT:  
    fffff880`0b7bc600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlGetExtendedContextLength+0x62
    
    
    FOLLOWUP_IP: 
    nt!RtlGetExtendedContextLength+62
    fffff800`02ea81ce 41ba04000000    mov     r10d,4
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!RtlGetExtendedContextLength+62
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    STACK_COMMAND:  .cxr 0xfffff8800b7bbc20 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlGetExtendedContextLength+62
    
    BUCKET_ID:  X64_0x3B_nt!RtlGetExtendedContextLength+62
    
    Followup: MachineOwner
    ---------
    Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

    Remove your USB wireless network device and replace with something more stable. Then we can determine if it is the cause of the problems you are experiencing or if more troubleshooting needs to be done.


    Did you replace the wireless USB with something more stable?
    Last edited by writhziden; 15 Mar 2012 at 21:00. Reason: Update?
      My Computer


  6. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #16

    it was a bad motherboard
      My Computer


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

    Thank you for letting us know. Glad it was resolved. :)
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 01:41.
Find Us