BSOD On Restart


  1. Posts : 120
    Windows 7 Professional x64
       #1

    BSOD On Restart


    If I restart the computer for updates or installs, or if I use start...shutdown...restart, the computer will BSOD shortly after the Windows logo/loading screen. However if I restart after the that BSOD it starts fine. Sometimes it will BSOD after a power-down.


    Thanks in advance for any help. I suspect it is my video driver, or maybe an HDD going bad.

    - x86 (32-bit) Windows 7 Ultimate
    - This was a fresh install of Windows 7, not an upgrade
    - Full retail
    - Motherboard/CPU/RAM 2 years, Video card, HDDs, Power Supply 2 months
    - Re-installed Windows 7 in January 2010, original install about 1 month before the release of Windows 7. (Completely legal full retail, piracy is for punks.)

    All information from this thread attached.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    0x000000C2: BAD_POOL_CALLER
    (A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.
    BAD_POOL_CALLERUsual causes: Device driver, ?Memory

    Code:
     
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp5_Windows7_BSOD_jcgriff2[1].zip\Windows7_BSOD_jcgriff2\082610-24414-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 x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x83002000 PsLoadedModuleList = 0x8314a810
    Debug session time: Thu Aug 26 09:11:55.295 2010 (GMT-4)
    System Uptime: 0 days 0:00:12.370
    Loading Kernel Symbols
    ...............................................................
    ......
    Loading User Symbols
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000007, Attempt to free pool which was already freed
    Arg2: 00001097, (reserved)
    Arg3: 08060008, Memory contents of the pool block
    Arg4: 87a44360, Address of the block of pool being deallocated
    Debugging Details:
    ------------------
    *** WARNING: Unable to verify timestamp for shdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for shdrv.sys
    GetPointerFromAddress: unable to read from 8316a718
    Unable to read MiSystemVaType memory at 8314a160
    *** WARNING: Unable to verify timestamp for mcupdate.dll
    *** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll
    *** WARNING: Unable to verify timestamp for iaStorV.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
    *** WARNING: Unable to verify timestamp for iaStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for PxHelp20.sys
    *** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
    *** WARNING: Unable to verify timestamp for ksecpkg.sys
    *** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
    *** WARNING: Unable to verify timestamp for fvevol.sys
    *** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
    *** WARNING: Unable to verify timestamp for apix.sys
    *** ERROR: Module load completed but symbols could not be loaded for apix.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for ssmdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
    *** WARNING: Unable to verify timestamp for dump_iaStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
    POOL_ADDRESS: GetPointerFromAddress: unable to read from 8316a718
    Unable to read MiSystemVaType memory at 8314a160
     87a44360 
    BUGCHECK_STR:  0xc2_7
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 83122a76 to 831211b6
    STACK_TEXT:  
    8078691c 83122a76 87a44360 00000000 80786960 nt!ExFreePoolWithTag+0x1b1
    8078692c 914db4e8 87a44360 87a43000 c0000001 nt!ExFreePool+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80786960 914d2037 87a3be00 87a43000 87a3be00 shdrv+0xd4e8
    807869b8 831a5740 87a3be00 87a43000 00000000 shdrv+0x4037
    80786b9c 833b3853 00000001 00000000 80786bd4 nt!IopLoadDriver+0x7ed
    80786be8 833af87b 8080f798 8080a420 00000000 nt!IopInitializeSystemDrivers+0x163
    80786c6c 833b4e78 0080a420 85b05d10 85b059a0 nt!IoInitSystem+0x6de
    80786d48 8318d494 80786d90 832106d3 8080a420 nt!Phase1InitializationDiscard+0xced
    80786d50 832106d3 8080a420 adb75e6f 00000000 nt!Phase1Initialization+0xd
    80786d90 830c20f9 8318d487 8080a420 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
     
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    shdrv+d4e8
    914db4e8 ??              ???
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  shdrv+d4e8
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: shdrv
    IMAGE_NAME:  shdrv.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4af08d32
    FAILURE_BUCKET_ID:  0xc2_7_shdrv+d4e8
    BUCKET_ID:  0xc2_7_shdrv+d4e8
    Followup: MachineOwner
    ---------
    0: kd> lmtsmn
    start    end        module name
    8be97000 8bedf000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
    91404000 9145e000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
    8c1ce000 8c1d7000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
    8c59a000 8c5a7000   apix     apix.sys     Tue Nov 03 15:06:10 2009 (4AF08D32)
    92128000 9212f000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
    836c8000 836d0000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
    92102000 92121000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
    83712000 837bd000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
    8c575000 8c59a000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
    836d0000 83712000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    8c3a3000 8c400000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
    8c5a7000 8c5b4000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
    8c564000 8c575000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
    920f1000 92102000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
    92017000 920f1000   dump_iaStor dump_iaStor.sys Thu Jun 04 21:42:33 2009 (4A287809)
    8c1d7000 8c1e8000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    8bfa7000 8bfdb000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
    8c20e000 8c217000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
    8c532000 8c564000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
    8c783000 8c7b4000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
    83412000 83449000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
    8c52a000 8c532000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
    8c0f4000 8c1ce000   iaStor   iaStor.sys   Thu Jun 04 21:42:33 2009 (4A287809)
    8c019000 8c0f4000   iaStorV  iaStorV.sys  Wed Apr 08 12:54:58 2009 (49DCD6E2)
    80bb0000 80bb8000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
    8c390000 8c3a3000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
    8c4f5000 8c51a000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
    8363f000 836b7000   mcupdate mcupdate.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
    8bf91000 8bfa7000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
    92181000 9218c000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
    8bee8000 8bef0000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
    8c365000 8c390000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
    8c51a000 8c52a000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
    8c400000 8c4b7000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
    91497000 914a5000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
    9145e000 91490000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
    8c4b7000 8c4f5000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
    9218c000 9219a000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
    83002000 83412000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
    8c236000 8c365000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
    92121000 92128000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
    8bf25000 8bf36000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
    8bef0000 8bf1a000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
    8c200000 8c20e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    836b7000 836c8000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
    8c1e8000 8c1f1200   PxHelp20 PxHelp20.sys Wed Mar 12 21:57:44 2008 (47D88A18)
    92169000 92171000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    92171000 92179000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
    92179000 92181000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
    8c608000 8c635000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
    914ce000 914f0000   shdrv    shdrv.sys    Tue Nov 03 15:06:10 2009 (4AF08D32)
    8c600000 8c608000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
    914c8000 914cda00   ssmdrv   ssmdrv.sys   Tue May 05 06:05:18 2009 (4A000F5E)
    8c63a000 8c783000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
    921b1000 921bc000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
    9219a000 921b1000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
    914b8000 914c8000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
    8bf1a000 8bf25000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
    9212f000 9213b000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
    9213b000 9215c000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
    8c7b4000 8c7bc380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
    8bf36000 8bf46000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8bf46000 8bf91000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
    8c7bd000 8c7fc000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
    914a5000 914b8000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
    9215c000 92169000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
    8be18000 8be89000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
    8be89000 8be97000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    91490000 91497000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
    8bedf000 8bee8000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
    Outdated Drivers
    PxHelp20 PxHelp20.sys Wed Mar 12 21:57:44 2008
    iaStorV iaStorV.sys Wed Apr 08 12:54:58 2009
    ssmdrv ssmdrv.sys Tue May 05 06:05:18 2009
    amdxata amdxata.sys Tue May 19 13:57:35 2009 (4A12F30F)




    Suggested Cause: See Above

    Suggested Solution
    Do steps in order shown. After the first two you can test the computer to see if you are still getting BSODs. If you do, complete one more step at a time at retest.
    Shdrv.sys: Update this driver
    Service Hardening Driver - TSX_R2 - Authentium, Inc
    Shdrv.sys file description
    Productname: TSX_R2
    Description: Service Hardening
    Driver Company: Authentium, Inc
    Install a current version of shdrv.sys as shown above
    Download memtest86 and test RAM
    RAM - Test with Memtest86+
    Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.
    Enable the Driver Verifier
    https://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
    Scan with your Anti Virus
    SFC /scannow
    https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    How to Find Drivers
    search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
    To remove any left over driver remnants, especially from graphics cards, use driver sweeper http://www.guru3d.com/category/driversweeper/

    After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
    If any links do not work, if clicked, please copy and paste to browser address bar.
    Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.
    Last edited by richc46; 26 Aug 2010 at 16:20.
      My Computer


  3. Posts : 2,528
    Windows 10 Pro x64
       #3

    It is a double-free attempt on a kernel pool block, so that would indicate driver. Rich is already right on this one - it's shdrv:
    Code:
    0: kd> k
    ChildEBP RetAddr  
    8078691c 83122a76 nt!ExFreePoolWithTag+0x1b1
    8078692c 914db4e8 nt!ExFreePool+0xf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80786960 914d2037 shdrv+0xd4e8
    807869b8 831a5740 shdrv+0x4037
    80786b9c 833b3853 nt!IopLoadDriver+0x7ed
    80786be8 833af87b nt!IopInitializeSystemDrivers+0x163
    80786c6c 833b4e78 nt!IoInitSystem+0x6de
    80786d48 8318d494 nt!Phase1InitializationDiscard+0xced
    80786d50 832106d3 nt!Phase1Initialization+0xd
    80786d90 830c20f9 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 nt!KiThreadStartup+0x19
    
    // Pool tag is AsmD:
    0: kd> dc 0x87a44360
    87a44360  87a47308 00000001 00000004 00000000  .s..............
    87a44370  00000002 00000004 00000000 00000004  ................
    87a44380  00000004 005c0053 04110006 446d7341  ....S.\.....AsmD
    87a44390  00000080 00000000 00000000 00000001  ................
    87a443a0  00000000 00000000 00000006 00000000  ................
    87a443b0  00000000 87a448e0 00000000 00000000  .....H..........
    87a443c0  914d4870 914d4850 914e00c0 914e1030  pHM.PHM...N.0.N.
    87a443d0  914e0480 914e0740 914e0aa0 914e0150  ..N.@.N...N.P.N.
    
    0: kd> lmvm shdrv
    start    end        module name
    914ce000 914f0000   shdrv    T (no symbols)           
        Loaded symbol image file: shdrv.sys
        Image path: shdrv.sys
        Image name: shdrv.sys
        Timestamp:        Tue Nov 03 15:06:10 2009 (4AF08D32)
        CheckSum:         0002963F
        ImageSize:        00022000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Last edited by cluberti; 26 Aug 2010 at 15:56. Reason: Rich types faster than me :)
      My Computer


  4. Posts : 120
    Windows 7 Professional x64
    Thread Starter
       #4

    It appears that the SHDrv driver was installed as part of a beta test I did for a company. The software was removed as instructed through "Programs And Features", but the driver is still loading unnecessarily. How would I go about cleaning it up? I have tried to disable SHDrv using Autoruns (Sysinternals) but I get the following error even when in safe mode: Error changing item state: Access is denied.

    PxHelp20 Px Engine Device Driver for Windows 2000/XP (Verified) Sonic Solutions c:\windows\system32\drivers\pxhelp20.sys (https://www.safecentral.com/online_i...ion_index.html)
    SHDrv Service Hardening Driver (Verified) Authentium, Inc. c:\windows\system32\drivers\shdrv.sys
    iaStorV iaStorV.sys Updated (Intel Matrix Storage Manager)
    amdxata Storage Filter Driver (Verified) Microsoft Windows c:\windows\system32\drivers\amdxata.sys

    I have no idea where the AMDXDATA driver is from. I don't think I have any AMD devices on this computer, everything is Intel here. Cannot find any updates after searching Google.

    PxHelp is part of Sonic's recording engine and is installed with Winamp. I cannot find a standalone updater, but made sure I have the latest version of Winamp Pro which updates the Sonic runtime.

    I am betting on the SHDrv. Can't figure out how to disable that one. I don't want to completely remove it to be sure it isn't necessary...I would like to just disable it first.
      My Computer


  5. Posts : 17,796
    Windows 10, Home Clean Install
       #5

    Manually, change the name to shdrv.bup. Then boot.

    Unofficially, I think if you get rid of this driver you will be ok.

    Make a system restore point before doing anything
      My Computer


  6. Posts : 120
    Windows 7 Professional x64
    Thread Starter
       #6

    It would not allow me to change it even if I took ownership. The software I was testing was security software...sort of ran a VM on top of your actual system. Safecentral, the link is in my post above.

    I was able to edit the registry offline using Hiren's Boot CD and removed the entry after exporting it for backup, and the system seems to be running fine. I rebooted twice, no BSOD, I am hoping that was the culprit.

    Thank you VERY much for all the help, let's hope this solved it.
      My Computer


  7. Posts : 17,796
    Windows 10, Home Clean Install
       #7

    You seem rather capable when it comes to computers, good going.
    I am glad that I was instrumental in helping you solve your problem.
    We are here, 24 x 7, if you need anything.

    EDIT: Since you do have computer "smarts", dont forget some of the other suggestions that I made, even if the computer does not BSOD. Get rid of those old drivers, make the sfc scan, run the anti virus, etc.

    Thanks for the rep, too. Very nice of you.
      My Computer


  8. Posts : 120
    Windows 7 Professional x64
    Thread Starter
       #8

    So here is my next question: How do I mark this thread as 'Solved"?

    I did follow all of your suggestions except for enabling the driver verifier. I was a bit daunted by the description in that thread. SFC had no issues, memtest x86 returned no issues, I updated the Intel Matrix storage driver and reinstalled the latest version of Winamp to obtain the latest Sonic runtime. I removed the SHDrv driver completely from the registry and the \windows\system32\drivers directory. I would have used Driver Sweeper, but it does not seem to work for the Safecentral driver (SHDrv). All I got from Safecentral's support was "Uninstall through Programs and Features". I explained to them that I had done this and that the driver had been left behind causing a BSOD, but of course that has not happened to anyone else and the only way to remove it was through Programs and Features.

    Luckily I know how to read and was able to remove it manually, thanks to your help.

    Mark as solved please. :)
      My Computer


  9. Posts : 17,796
    Windows 10, Home Clean Install
       #9

    So that you can learn, too.
    Upper right, three icons. One looks like a triangle the other a snowflake.
    click on the triangle and then type solved in the box that will appear.

    Good luck to you and enjoy your computer.
      My Computer


 

  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 00:24.
Find Us