BSoD While Gaming

Page 2 of 2 FirstFirst 12

  1. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #11

    You may have a defective CPU, stop any overclocking and follow the steps below
    Bugcheck 101 is mainly caused by a defective CPU or outdated BIOS

    Details about this bugcheck:
    https://www.sevenforums.com/crash-loc...tml#post567135

    Win 7 A Clock Interrupt... BSOD (101 Error)

    Remove Asus Update or PC Probe
       Warning
    ASACPI.sys the old versions are huge cause of BSOD's
    Please visit this link: http://support.asus.com/download.aspx?SLanguage=en&m=P7P55D%20LE&p=1&s=32&os=29&hashedid=e7Zic83PvQSr80Lm
    Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2004-5).


       Information
    Go to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.

    Run Prime 95 again to test your CPU and your ram. Carefully the instructions in this tutorial:
    CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {61, 0, 807c5120, 1}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 00000000, 0.
    Arg3: 807c5120, The PRCB address of the hung processor.
    Arg4: 00000001, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1c
    
    STACK_TEXT:  
    8db1f154 832a4e13 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
    8db1f190 832a4462 00002711 00000000 0000b400 nt!KeAccumulateTicks+0x242
    8db1f1d0 832a430f 832d097d 0f9d89c1 00000000 nt!KeUpdateRunTime+0x145
    8db1f228 832a967f 832cd402 832cd402 000000d1 nt!KeUpdateSystemTime+0x613
    8db1f228 832d097d 832cd402 832cd402 000000d1 nt!KeUpdateSystemTimeAssist+0x13
    8db1f2c8 83478332 c645a04f 85a893b0 000000b8 nt!KeQueryValuesProcess+0xbb
    8db1f350 83476c34 00091cb8 cc756000 c645a0eb nt!ExpCopyProcessInfo+0x116
    8db1f3f4 8346d8a6 cc756098 0001ff68 8db1f844 nt!ExpGetProcessInformation+0x115
    8db1f874 8346f95c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086
    8db1f890 8327c43a 00000005 cc756098 0001ff68 nt!NtQuerySystemInformation+0x76
    8db1f890 8327ae09 00000005 cc756098 0001ff68 nt!KiFastCallEntry+0x12a
    8db1f918 8bb9dfdf 00000005 cc756098 0001ff68 nt!ZwQuerySystemInformation+0x11
    8db1fc78 8bb7b15e 00000000 00000000 8db1fc98 cng!GatherRandomKey+0x272
    8db1fcdc 8bb7b1bf 00000000 8db1fd00 83459b2f cng!ReadExternalEntropyIntoPool+0x1a6
    8db1fce8 83459b2f 862c25d0 00000000 85aa8238 cng!scavengingWorkItemRoutine+0x15
    8db1fd00 832a703b 85aa8238 00000000 859dca70 nt!IopProcessWorkItem+0x2d
    8db1fd50 834479df 00000001 c645ae8f 00000000 nt!ExpWorkerThread+0x10d
    8db1fd90 832f91d9 832a6f2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    Last edited by yowanvista; 05 May 2011 at 02:58.
      My Computer


  2. Posts : 12
    Windows 7 Ultimate x86
    Thread Starter
       #12

    Hi, I reinstalled my OS to remove any of the straggling old drivers I had or the other causes of BSoDs like the SPTD.sys. I tried running heroes of newerth but got the dxxxxx could not be found, so I downloaded the June 2010 end-user directx runtime, installed that and was able to play. i played one game without BSoD. While moving my backups to their old places (documents, pictures) i got the BSoD. i have attached a zip folder containing 2 BSoDs. BTW, I cannot access that website. this appears "Server Error in '/' Application." What is on that webpage?

    I will try the prime 95 test again. Btw, how can I check if my video card is not defective?
      My Computer


  3. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #13

    Your vsserv.exe process which is related to Bitdefender caused the crash, please remove it
    You can test your video card with the GPU tests of OCCT http://downloads.guru3d.com/OCCT-%28...load-1880.html
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 7d510113, a40eb694, 0}
    
    Probably caused by : ntkrpamp.exe ( nt!KiDeliverApc+111 )
    
    
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 7d510113, The address that the exception occurred at
    Arg3: a40eb694, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    +12a
    7d510113 ??              ???
    
    TRAP_FRAME:  a40eb694 -- (.trap 0xffffffffa40eb694)
    ErrCode = 00000010
    eax=a40eb730 ebx=82a0cb48 ecx=00000001 edx=00000000 esi=86e14580 edi=86de56c8
    eip=7d510113 esp=a40eb708 ebp=a40eb754 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    7d510113 ??              ???
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  vsserv.exe
    
    CURRENT_IRQL:  1
    
    LAST_CONTROL_TRANSFER:  from 82ae5fa9 to 7d510113
    
    STACK_TEXT:  
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a40eb704 82ae5fa9 86e14580 a40eb730 a40eb73c 0x7d510113
    a40eb754 82aacafd 00000000 00000000 00000000 nt!KiDeliverApc+0x111
    a40eb798 82aab403 851a03d0 86de56c8 86de57c4 nt!KiSwapThread+0x24e
    a40eb7c0 82aa76ef 86de56c8 86de5788 00000000 nt!KiCommitThreadWait+0x1df
    a40eb93c 82c70625 00000002 a40eba74 00000001 nt!KeWaitForMultipleObjects+0x535
    a40ebbc8 82c70392 00000002 a40ebbfc 00000001 nt!ObpWaitForMultipleObjects+0x262
    a40ebd18 82a8142a 00000002 0df9fbcc 00000001 nt!NtWaitForMultipleObjects+0xcd
    a40ebd18 76ff64f4 00000002 0df9fbcc 00000001 nt!KiFastCallEntry+0x12a
    0df9fc18 00000000 00000000 00000000 00000000 0x76ff64f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDeliverApc+111
    82ae5fa9 eb78            jmp     nt!KiDeliverApc+0x18b (82ae6023)
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!KiDeliverApc+111
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007
    
    FAILURE_BUCKET_ID:  0x8E_nt!KiDeliverApc+111
    
    BUCKET_ID:  0x8E_nt!KiDeliverApc+111
    
    Followup: MachineOwner
    ---------
      My Computer


  4. Posts : 12
    Windows 7 Ultimate x86
    Thread Starter
       #14

    I have removed bitdefender using the uninstall tool. i was about to unzip the prime95 when I got the disk.sys bsod. Attached is the dump file of said BSoD. :S more and more BSoDs keep popping up!
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #15

    iarvee said:
    I have removed bitdefender using the uninstall tool. i was about to unzip the prime95 when I got the disk.sys bsod. Attached is the dump file of said BSoD. :S more and more BSoDs keep popping up!
    This dump indicates that your Hard Disk was shut down unexpectedly during the crash, are you overclocking any compenents of your computer?
    Run Disk Check
    Please remove EVGA Precision

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 8b2112fc, a0123b74, 0}
    
    Probably caused by : disk.sys ( disk!DiskShutdownFlush+ea )
    
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8b2112fc, The address that the exception occurred at
    Arg3: a0123b74, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    disk!DiskShutdownFlush+ea
    8b2112fc 894704          mov     dword ptr [edi+4],eax
    
    TRAP_FRAME:  a0123b74 -- (.trap 0xffffffffa0123b74)
    ErrCode = 00000002
    eax=85d6de94 ebx=00000000 ecx=85d6d694 edx=85d6de88 esi=85d6dda0 edi=00000000
    eip=8b2112fc esp=a0123be8 ebp=a0123bfc iopl=0         nv up ei ng nz na pe cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
    disk!DiskShutdownFlush+0xea:
    8b2112fc 894704          mov     dword ptr [edi+4],eax ds:0023:00000004=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 8b1b00cf to 8b2112fc
    
    STACK_TEXT:  
    a0123bfc 8b1b00cf 85d6da20 85d6dee0 85d764e8 disk!DiskShutdownFlush+0xea
    a0123c18 8b1af3bf 85d6da20 86b140e8 85d6da20 CLASSPNP!ClassShutdownFlush+0x43
    a0123c2c 82a3e4bc 85d6da20 86b140e8 85d6d718 CLASSPNP!ClassGlobalDispatch+0x20
    a0123c44 8ad49372 86b140e8 86b140e8 a0123c68 nt!IofCallDriver+0x63
    a0123c54 8ad492e5 85d6d718 86b140e8 85d6d660 partmgr!PmFlushBuffers+0x83
    a0123c68 82a3e4bc 85d6d660 86b140e8 86b142b8 partmgr!PmGlobalDispatch+0x1d
    a0123c80 8ad5afff 85d6fc18 85338d48 a0123ca8 nt!IofCallDriver+0x63
    a0123c90 82a3e4bc 85d6fcd0 86b140e8 85d766d0 volmgr!VmFlushBuffers+0xcb
    a0123ca8 8b17a854 a0123cc8 82a3e4bc 85d766d0 nt!IofCallDriver+0x63
    a0123cb0 82a3e4bc 85d766d0 86b140e8 85d764d0 fvevol!FveFilterSkip+0x1e
    a0123cc8 8b153083 a0123d28 85d76418 a0123cf0 nt!IofCallDriver+0x63
    a0123cd8 82a3e4bc 85d76418 86b140e8 85d734e8 rdyboost!SmdDispatchPassthrough+0x6d
    a0123cf0 8b3b1d51 a0123d10 82a3e4bc 85d734e8 nt!IofCallDriver+0x63
    a0123cf8 82a3e4bc 85d734e8 86b140e8 9b4b3b18 volsnap!VolSnapDefaultDispatch+0x2b
    a0123d10 8ae3391c 9b4b3a78 a0123d34 82a7210e nt!IofCallDriver+0x63
    a0123d1c 82a7210e 9b4b3b18 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14
    a0123d1c 82a72205 9b4b3b18 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
    9b4b3a88 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    disk!DiskShutdownFlush+ea
    8b2112fc 894704          mov     dword ptr [edi+4],eax
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  disk!DiskShutdownFlush+ea
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: disk
    
    IMAGE_NAME:  disk.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf20
    
    FAILURE_BUCKET_ID:  0x8E_disk!DiskShutdownFlush+ea
    
    BUCKET_ID:  0x8E_disk!DiskShutdownFlush+ea
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 12
    Windows 7 Ultimate x86
    Thread Starter
       #16

    Yowan, I was able to run a memtest using 86. I first started the test with both of my ram cards in both slots. It failed during the 6th test. Then I took the 2nd ram out (from the 2nd slot), and ran it again. It passed. i took the first ram out and replaced it with the 2nd ram. It passed again. This time, I removed the 2nd ram from the first slot, and put the 1st ram into the 2nd slot. It failed. Did the same with the 2nd ram, it failed.

    ^ was that confusing or were you able to understand?

    So could all of my BSoDs be caused by a faulty memory port? What I have now is just 1 2gb ram inserted into the first slot. I don't have time to test in-game right now.

    If it is caused by a faulty port, will buying a new motherboard fix this problem?
      My Computer


  7. Posts : 12
    Windows 7 Ultimate x86
    Thread Starter
       #17

    Uh, bump?
      My Computer


  8. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #18

    iarvee said:
    Yowan, I was able to run a memtest using 86. I first started the test with both of my ram cards in both slots. It failed during the 6th test. Then I took the 2nd ram out (from the 2nd slot), and ran it again. It passed. i took the first ram out and replaced it with the 2nd ram. It passed again. This time, I removed the 2nd ram from the first slot, and put the 1st ram into the 2nd slot. It failed. Did the same with the 2nd ram, it failed.

    ^ was that confusing or were you able to understand?

    So could all of my BSoDs be caused by a faulty memory port? What I have now is just 1 2gb ram inserted into the first slot. I don't have time to test in-game right now.

    If it is caused by a faulty port, will buying a new motherboard fix this problem?
    Yes your RAM slot on the board may be defective, I suggest getting a new board
      My Computer


  9. Posts : 12
    Windows 7 Ultimate x86
    Thread Starter
       #19

    Spoke too soon. Got these 2 bsods.

    I ran a prime95 test like you stated, it failed. :3 So everything is like, broken?
      My Computer


  10. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #20

    iarvee said:
    Spoke too soon. Got these 2 bsods.

    I ran a prime95 test like you stated, it failed. :3 So everything is like, broken?
    What was the result of Prime95? Are you overclocking your CPU?
    Steam was involved in your crash, I suggest disabling it from starting up
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 82b01cea, 9baffac4, 0}
    
    Probably caused by : ntkrpamp.exe ( nt!ExpReleasePoolQuota+21 )
    
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 82b01cea, The address that the exception occurred at
    Arg3: 9baffac4, Trap Frame
    Arg4: 00000000
    
    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!ExpReleasePoolQuota+21
    82b01cea 8a07            mov     al,byte ptr [edi]
    
    TRAP_FRAME:  9baffac4 -- (.trap 0xffffffff9baffac4)
    ErrCode = 00000000
    eax=00000005 ebx=63577054 ecx=000001ff edx=0000001c esi=86ad4370 edi=79c868f0
    eip=82b01cea esp=9baffb38 ebp=9baffba0 iopl=0         nv up ei pl nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
    nt!ExpReleasePoolQuota+0x21:
    82b01cea 8a07            mov     al,byte ptr [edi]          ds:0023:79c868f0=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  GameOverlayUI.
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 82b6977f to 82b01cea
    
    STACK_TEXT:  
    9baffb40 82b6977f 00000001 84b03788 00000000 nt!ExpReleasePoolQuota+0x21
    9baffba0 82b0b9d1 86ad4378 00000000 848da508 nt!ExFreePoolWithTag+0x779
    9baffbc4 82c6b6f4 84b03788 84b03788 84b03770 nt!ExpDeleteWorkerFactory+0x66
    9baffbdc 82ab2f60 00000000 86b30030 84b03770 nt!ObpRemoveObjectRoutine+0x59
    9baffbf0 82ab2ed0 84b03788 82c8f78c ad8257a8 nt!ObfDereferenceObjectWithTag+0x88
    9baffbf8 82c8f78c ad8257a8 86b30030 ad8257a8 nt!ObfDereferenceObject+0xd
    9baffc38 82cc18d9 9bdd94e8 ad8257a8 863768f0 nt!ObpCloseHandleTableEntry+0x21d
    9baffc68 82cc7227 9bdd94e8 9baffc7c ad8045c8 nt!ExSweepHandleTable+0x5f
    9baffc88 82c92c78 a2eb45ac 00000000 86b30030 nt!ObKillProcess+0x54
    9baffcfc 82cabd37 00000000 ffffffff 0012fe88 nt!PspExitThread+0x5d9
    9baffd24 82a8d42a ffffffff 00000000 0012fe94 nt!NtTerminateProcess+0x1fa
    9baffd24 772564f4 ffffffff 00000000 0012fe94 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012fe94 00000000 00000000 00000000 00000000 0x772564f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExpReleasePoolQuota+21
    82b01cea 8a07            mov     al,byte ptr [edi]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExpReleasePoolQuota+21
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007
    
    FAILURE_BUCKET_ID:  0x8E_nt!ExpReleasePoolQuota+21
    
    BUCKET_ID:  0x8E_nt!ExpReleasePoolQuota+21
    
    Followup: MachineOwner
    ---------
      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 17:33.
Find Us