Random BSOD win32k.sys 0x3b

Hello!

Bought a new computer and installed Win7 64. I do not get on a BSOD a week and it seems to be completely random when it happens. So far, I tested with memtest86, Furmark and chkdsk without error.

You can find the dump files 3 here:

https://www.dropbox.com/sh/7vt2ruxojpqn3hc/DKvxcxqbSG

I've updated the drivers video (Beta, nothing more recent), chipset drivers and installet SP1 without result.

Let me know if you need more information.

Much appreciated!

Hello

All attached files of the DMP are bug check SYSTEM_SERVICE_EXCEPTION (3B) .

This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.

This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

Bugcheck 3B, {c0000005, fffff96000144283, fffff8800b1a0020, 0}

5: kd > fffff96000144283 ln
(fffff960'001441e0)   win32k! HmgLockEx + 0xa3 |  (fffff960'0014432 c) win32k! RGNOBJ::vSet

The exception is produced in win32k! HmgLockEx.

---------------------------

1. AsIO.sys is listed and loaded which is Asus PC Probe / AI Suite. Please uninstall all software of Asus/bloatware as soon as POSSIBLE.

2. make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

3 if you're still crashing after all the above, please run Memtest for no. LESS than ~ 8 going on (several hours):

Memtest86 +:

Download Memtest86 + here:

http://www.memtest.org/

Which should I download?

You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).

Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.

The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.

Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.

Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.

This information, if it is available for the program, can be displayed via a menu option.

Other questions, they can most likely be answered by reading this excellent guide here:

http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

Kind regards

Patrick

Tags: Windows

Similar Questions

  • Win 7 64 random BSOD (nvlddmkm.sys, ataport.sys, dxgmms1.sys)

    Looking for help to detect which continues, started getting random BSOD for the last weeks of both systems has been stable for months at 100%.  Nothing has changed hardware wise over the last 9 months, software wise, I updated my video card drivers.  I've since gone back to the old drivers video and am still getting the BSOD.  Any help would be appreciated, thanks.

    Mini dump files

    GR

    Verified and associated avc3.sys driver driver filter Active Virus Control of BitDefender STROKE.  I remove it and use MSE in its place

    http://www.Microsoft.com/security_essentials/

  • Win32k.sys BSOD on launch of the first

    Until yesterday, Premiere Pro (CS6 and CC) worked very well. Whenever I try to launch the first now, it freezes at the end of the start screen and hangs my computer with system BSOD win32k.sys "page_fault_in_nonpaged_area" error None of my other Adobe products have had this same problem. After Effects, Photoshop, Lightroom - all loads very well. No updates have been tested, either. I tried the boot safe mode with networking and the same accident occurs. Anyone have any ideas?

    Hi Bhonik,

    Please try to rename the link dynamics and links Manager preferences Dynamics media server from 7.0 to old7.0. You can go to C:\Users\username\AppData\Roaming\Adobe

    and check these folders (make sure that you have display hidden folders). Once done, restart the machine and try to relaunch the products.

    Kind regards

    Vinay

  • How can I stop getting the win32k.sys error blue screen?

    This computer in the Shop 3 times ($$$) and still not fixed.

    . I've updated drivers, corrected the registry errors, changed the CMOS battery, had card mother replacement and addition of RAM maximum.

    Thank you
    David

    Hi, David,.

    Check the solutions proposed here

    W7 Bluescreen: system_service_exception

    http://social.technet.Microsoft.com/forums/en/w7itprogeneral/thread/ad2b7744-4118-4e36-9d79-9ba25e73318e

    http://www.howtofixbluescreenofdeath.com/Win32k-sys-blue-screen/

    http://www.SevenForums.com/crashes-debugging/39979-BSOD-Win32k-sys.html

  • BSOD iusb3xhc.sys

    Greetings! I have problem with my pc im getting random BSOD iusb3xhc.sys. I think it all started when I updated some drivers using extra driver. I got about 3 or 4 BSOD randomly this sort relating in particular to iusb3xhc.sys everything. I run sfc/scannow, and she reported that it fixed a problem .i run it again 3 times and no problems have been detected and I thought that everything was going well so far.
    I have a win 7 ultimate 64-bit service pack 1
    Core i3 of intel 4160
    RAM Kingston kvr 4 x 2 8 GB
    motherboard Asus b85m g
    660 GTX video card
    160 GB of disk velociraptor hard disk OS and 500 GB samsung spinpoint f3 as storage device
    Corsair vs650 650watts PSU.

    Here's the last minidump file:
    http://1drv.Ms/1JdcgRN

    Hello

    Apologize for the delayed response. It seems that this problem started after the installation of the Booster driver in the computer. These applications are known to cause damages instead of being useful to the computer. Did you uninstall the software from the computer? If this isn't the case, I suggest you uninstall the same and check if still have problems you.

    See the following article to troubleshoot BSOD:

    http://Windows.Microsoft.com/en-in/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

    Please make sure that your computer is virus-free by running a full scan using the Microsoft Safety Scanner. No doubt these files were created by viruses.

    Note: The files infected by viruses will be deleted and so there is a chance of data loss.

    Please be sure to download and install the latest drivers for your card display and Chipset graphics and motherboard from the manufacturer's website. Also check the updates of the firmware or the BIOS and install it as well.

    Come back for additional help.

  • Win32k.sys BSOD Intermittent problem

    I got a problem for several months with my computer all of a sudden stop and will the BSOD. The problem seems to occur when something on the InterNet, such as; From IE8/Google Chrome, access to a new tab, using the link that begins the new tab, change the pages and even beginner Email (Outlook Express). My system, in its current form, has run flawlessly since 2009. The complaint of BS is still the same: PAGE_FAULT_IN_NONPAGED_AREA, then that indicates a problem with win32k.sys. This question IS NOT preceded by a power interruption. I have a genuine XP installation with Service Pack 2 CD (because it is upgraded to SP3).

    I tried to find the fault using MemTest 86 (boot from CD when you run the test) and my RAM memory test. No defects found in 10 run tests.
    I had once an indication that there may be a flaw in Z: drive.  Drive Z: is a physically separated, HD 20 GB which stores much of the things of the InterNet as cookies, graphics, etc., and all files downloaded from the InterNet are stored on this drive (to avoid infecting my system drive). I ran CHECKDISK tool with Scan for and attempt recovery of bad sectors checked options and Auto-Fix file system errors. Connected the CHKDSK boot by following the instructions. No problems found.
    I also use CCleaner v4.09 to remove most of the detritus left by the InterNet (especially on drive Z :) and also check the register of questions.
    I have also four Minidump.DMP zipped files (using 7-Zip [file .7z]), but do not have the installation on this page to send the files damaged by arches. I file before, but not SkyNet or whatever is the sharing of files also mentioned elsewhere.

    System Specs:
    Make & model: Auto built in 2008
    Motherboard: ASRock 4Core1600-D800
    Processor: Intel Celeron CPU 430 @ 1.8 GHz, pin 775
    RAM: 3.0 GB of installed Ram (2 sticks [?])
    Video: ATI Radeon HD 2600 Pro (256 MB RAM DDR2)
    DVD installed: HL-DT-ST DVDRAM GH24NS90 R / W DVD
    System:
    WINDOWS XP HOME v2002 SP3 + w/SP2
    Antivirus: Trend Micro Titanium
    News of the blue screen:
    PAGE_FAULT_IN_NONPAGED_AREA
    STOP: 0X0000008E (0XC0000005, 0XBF905FAE, 0XA8BA29F8, 0X00000000)
    WIN32K. SYS - ADDRESS BF9005AFE BASE AT BF800000, time STAMP: 521ea476
    Has occurred @ 10:10, 04/12/13
    #2
    PAGE_FAULT_IN_NONPAGED_AREA
    STOP: 0 X 00000050 (0XE15F001C, 0X00000001, 0X00000000, 0XBF84B3D0)
    WIN32K. SYS - ADDRESS BF84B3D0 BASE AT BF800000, time STAMP: 52706e3f
    Was held on 15/12/13

    Proteus

    Worked well but had to respond to survey questions to continue.

    It was final but related to memory.  I doubt it's the memory itself, so I'd start by Driver Verifier.

    These accidents were related to the corruption of memory (probably caused by a driver).

    Please run these tests to check your memory and find which driver is causing the problem.


    If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

    1-Memtest. (You can read about running memtest here)

    2-Driver Verifier (for full instructions, see our wiki here)

    If you encounter problems or get stuck at any point, feel free to ask questions

    If you are unable to Windows because it crashes too early, try safe mode.

    If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.
    Co-written by JMH3143

  • Random BSOD and it seems to point to Netwsw02.sys

    Original title: Netwsw02.sys BSOD

    Hey guys,.

    One of my laptops in my area gives random BSOD. I had a look at the minidumps and it seems to point to Netwsw02.sys

    Looking around online, it was suggessted to update the drivers, etc. I went and checked all drivers and updates available, but this user is always get the BSOD. Whenever it looks like the same Netwsw02.sys is marked up in the minidumps.

    After having had a look at the W2k3 I see nothing out of habit there either.

    I'm new to this community - how can I reach the minidumps for this post?

    Its a SP1 Win7 64 bit

    HP 820 G2

    We have the same standard image on all our laptops of the same model throughout the Organization and other laptops are fine.

    Thanks in advance!

    Keesh

    Happy to help

    Associated with the Netwsw00.sys Intel® Wireless WiFi Link Driver of Intel Corporation

    Remove the driver current completely and install the latest driver available.  For instructions on how to do read everything to update the drivers of my partner JMH3143 http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149 here

  • Need help with BSOD PAGE_FAULT_IN_NONPAGED_AREA win32k.sys

    Hello

    How it started:

    I turned on my com and the screen was obscured for a few minutes, I force shut it down by pressing the start on my laptop and tried to back button - turn on the laptop, and it came on the screen

    Which was posted on the bsod:

    Win32k.sys

    PAGE_FAULT_IN_NONPAGED_AREA

    Technical information:

    STOP: 0 X 00000050 (0XFFFFF901C06729B4, 0 X 0000000000000000, 0XFFFF9600006CCA3, 0 X 0000000000000005)

    win32K.sys - address FFFFF9600006CCA3 base at FFFFF96000000000, Datestamp 53c5df64

    It's probably something that I installed, however I have not installed any new devices to my com, what I did was clean by removing unwanted programs (Non-windows) and clean my com through defragmentation and free disk space.

    I can't seem to find a solution on the forum who can solve my problem, I restarted my com and tried to start in safe mode, safe mode with network, safe mode with command prompt all brings back me to the BSOD. Most assistance in the forum would require me to start working on Windows, but I'm unable to access the windows because regardless of the command I run the com will return to the BSOD. Then I tried pressing F8 startup and select "System, restoration" and by running the backup, the computor invites you to me, ' the selected backup could not be found. System Restore is looking for a restore point that is located on your backup. Choose a different restore point. "I tried to run the backup of all and the same mistake has been invited.

    Finally, I did a system recovery Image so I can't use any device to restore the computor to previous state, while it was working fine.

    Any help is appreciated, thanks for reading.

    Hello

    Thanks for the reply.

    For you to get the dump files the computer should start first and then only you can provide us with the dump files.

    I suggest you follow the steps in the link below.

    http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7#section_2

    Note: Please ignore the steps under System Restore and reinstall Windows 7.

  • Win32k.sys caused BSOD IRQL, looking for likely causes

    While I was recording game for a game with Fraps, I got BSODed with him saying that an IRQL_NOT_LESS_OR_EQUAL error has been generated by win32k.sys.  I have debugged the minidump file and am looking for a reason why it happened.  I don't see anything obvious to said in the report that is generated if:

    Loading dump file [C:\Windows\Minidump\Mini071811-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol search path is: SRV * c:\symbols* http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (4 procs) free x 86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    By: 6002.18327.x86fre.vistasp2_gdr.101014 - 0432
    Computer name:
    Core = 0 x 82036000 PsLoadedModuleList = 0x8214dc70
    The debugging session: my Jul 18 22:01:47.823 2011 - 07:00 (UTC).
    System Uptime: 5 days 2:05:24.971
    Loading the kernel symbols
    ...............................................................
    ................................................................
    .........................................
    Loading user symbols
    Loading unloaded module list
    ..................
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck A, {9f5fffe4, 2, 1, 820cbc5b}

    Probably caused by: win32k.sys (win32k! Win32AllocPool + 13)

    Follow-up: MachineOwner
    ---------

    0: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access an address pageable (or completely invalid) to a
    application interrupt level (IRQL) that is too high.  It is usually
    caused by drivers using a wrong address.
    If a kernel debugger is available, download the stack trace.
    Arguments:
    Arg1: 9f5fffe4, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, bit field:
    bit 0: value 0 = read operation, 1 = write operation
    bit 3: value 0 = not an enforcement operation, 1 = performance operation (only on chips that support this level of State)
    Arg4: 820cbc5b, address memory

    Debugging information:
    ------------------

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8216d 868
    Cannot read MiSystemVaType memory at 8214d 420
    9f5fffe4

    CURRENT_IRQL: 2

    FAULTING_IP:
    NT! MiUnlinkFreeOrZeroedPage + 87
    820cbc5b 890c 10 mov dword ptr [eax + edx], ecx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0XA

    Nom_processus: pcsx2 - r4600.exe

    TRAP_FRAME: cac1b9fc-(.trap 0xffffffffcac1b9fc)
    ErrCode = 00000002
    EAX = ebx = 00000023 000010a 8 ecx = 00004600 edx = 00000000 esi = 00000000 edi = f68fc0a8
    EIP = 820eb23a esp = cac1ba70 ebp = cac1bab8 iopl = 0 nv in pe of na EI pl nz nc
    CS = 0008 ss = 0010 ds = 0023're = 0023 fs = 0030 gs = 0000 efl = 00010206
    NT! ExpAllocateBigPool + 0 x 231:
    820eb23a 895ffc mov dword ptr [edi-4], ebx ds:0023:f68fc0a4 is?
    Reset the default scope

    LAST_CONTROL_TRANSFER: from 820cbc5b to 82083fd9

    STACK_TEXT:
    cac1b7a0 820cbc5b badb0d00 88c8d8b8 83600000 nt! KiTrap0E + 0x2e1
    cac1b824 820cbeaf 00049351 85e44478 400001d 5 nt! MiUnlinkFreeOrZeroedPage + 0 x 87
    cac1b864 820ae467 000001d 5 86399030 c07b47e0 nt! MiRemoveAnyPage + 0x16c
    cac1b8ac 820adce4 00000001 f68fc0a4 c07b47e0 nt! MiResolveDemandZeroFault + 0x2e2
    cac1b968 820cf331 f68fc0a4 00000000 00000000 nt! MiDispatchFault + 0xadb
    cac1b9e4 82083dd4 00000001 f68fc0a4 00000000 nt! MmAccessFault + 0x10c6
    cac1b9e4 820eb23a 00000001 f68fc0a4 00000000 nt! KiTrap0E + 0xdc
    57 000000 has 8 00000021 000010 82123c cac1bab8 has 8 nt! ExpAllocateBigPool + 0 x 231
    00000021 000010a 0 35316847 nt a21664c9 cac1bb18! ExAllocatePoolWithTag + 0 x 116
    cac1bb2c a214a4aa 000010a 0 35316847 and 00000000 win32k! Win32AllocPool + 0x13
    cac1bb40 a216a2ee 000010 has 0 cac1bbe4 35316847 win32k! PALLOCMEM + 0X18
    cac1bb5c a214a88d 000010a 0 00000001 and 00000005 win32k! AllocateObject + 0 x 97
    cac1bb94 a21533c1 00000000 00000000 00000080 win32k! SURFMEM::bCreateDIB + 0x21d
    cac1bc48 a2127c98 01010052 00000000 00000000 win32k! GreCreateDIBitmapReal + 0x320
    cac1bce4 a2127f35 085a805c 00000000 00000000 win32k! _InternalGetIconInfo + 0xbe
    cac1bd44 82080c7a 00010003 085a805c 00000000 win32k! NtUserGetIconInfo + 0xf1
    cac1bd44 77d75ca4 00010003 085a805c 00000000 nt! KiFastCallEntry + 0x12a
    WARNING: Frame IP not in any known module. Sequence of images may be wrong.
    00000000 00000000 00000000 00000000 0x77d75ca4 085a803c

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    Win32k! Win32AllocPool + 13
    5 d a21664c9 pop ebp

    SYMBOL_STACK_INDEX: 9

    SYMBOL_NAME: win32k! Win32AllocPool + 13

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    Nom_image: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4d6f96aa

    FAILURE_BUCKET_ID: 0xA_win32k! Win32AllocPool + 13

    BUCKET_ID: 0xA_win32k! Win32AllocPool + 13

    Follow-up: MachineOwner
    ---------

    So far, this was the only time where I had it coming, but I have not tried from new record yet.  Actively running programs are FireFox, Pcsx2 and Fraps.  However, I ran these before without this issue arise.  I'm inclined to think that this is a time to screw that maybe something has been registered correctly or incorrectly read memory.

    Hello

    References to Vista also apply to Windows 7.

    This is my generic how updates of appropriate driver:

    This utility, it is easy see which versions are loaded:

    -Free - DriverView utility displays the list of all device drivers currently loaded on your system.
    For each driver in the list, additional useful information is displayed: load address of the driver,
    Description, version, product name, company that created the driver and more.
    http://www.NirSoft.NET/utils/DriverView.html

    For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
    Control Panel - device - Graphics Manager - note the brand and complete model
    your video card - double - tab of the driver - write version information. Now, click on update
    Driver (this can do nothing as MS is far behind the certification of drivers) - then right-click.
    Uninstall - REBOOT it will refresh the driver stack.

    Repeat this for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party
    with their own software and drivers and all other main drivers that you have.

    Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
    Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
    BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

    Download - SAVE - go to where you put them - right click - RUN AD ADMIN - REBOOT after
    each installation.

    Always check in the Device Manager - drivers tab to be sure the version you actually install
    presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
    in particular that) so to install a driver - reboot - check that it is installed and repeat as
    necessary.

    Repeat to the manufacturers - BTW in the DO NOT RUN THEIR SCANNER device - check
    manually by model.

    Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
    http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

    Installation and update of drivers to 7 (update drivers manually using the methods above is preferred
    to make sure that the latest drivers from the manufacturer of system and device manufacturers are located)
    http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.html

    ==========================================

    Tests of memory intercept all errors such as memory do not match (possible even for sticks
    seemingly identical) and when the faster memory is placed in system behind the slower memory.
    So it is best to Exchange also glue in and out to check for those, even if all the tests of memory do not respond
    a problem.

    To test the RAM here control - run 4 + hours or so.<-- best="">
    www.memtest.org

    For the Windows Memory Diagnostic tool.

    Start - type in the search-> memory box - find top - click - right Memory Diagnostics tool
    RUN AS ADMIN follow the instructions

    Windows Vista: How to scan / test your RAM or memory with Windows Vista Memory Diagnostic
    Tool
    http://www.shivaranjan.com/2007/11/01/Windows-Vista-how-to-scan-test-your-RAM-or-memory-with-Windows-Vista-memory-diagnostic-tool/

    How to run the diagnostic tool memory in Windows 7
    http://www.SevenForums.com/tutorials/715-memory-diagnostics-tool.html

    I hope this helps.

    Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

  • Win32k.sys

    Hello, today my mobile I got a bsod saying something with win32k.sys. When I try to start the laptop I get this error message after the windows logo. My laptop is a dv6 palvion 7006ed

    A few quick questions:

    What operating system do you use?

    Have you checked the the warranty status of your laptop? If it is under warranty, HP will likely have work you through several of these steps. Once they fail, they will send you recovery media, or you will ship the laptop for them and they will be reimage the hard drive.

    There are a few things you can try... From my experience, a Blue Screen of Death is usually indicative of a problem in the Windows operating system. They can be difficult to resolve, that usually require a reinstallation of the operating system to fix completely. If you can start Windows, download your saved data if you have not already. We should be able to solve this problem, but if you have to reload the OS, it will reformat the disk and erase all data on the hard drive.

    The system boots to Windows at all? When you get the BSOD? If it happens while you are working in windows, maybe we can fix it without losing everything. If it happens during startup, it is a little more difficult...

    Have you recently plugged all the new devices on the laptop? Sometimes, if a device is not completely compatible with Windows, it will cause a BSOD. Try disconnecting any new device and see if that helps.

    Try a hard reset of the laptop. Shut down the computer and unplug the unit, remove the battery. Press and hold the power button for at least 30 seconds plug it back and try to turn on/off. What you do here are draining any residual power that has been stored in the motherboard.

    If you cannot start Windows normally, try to start in "Safe Mode"? When the computer starts, press F8 several times until the advanced boot options go up and select boot mode safe.

    If you can get into Windows, you can try to restore the system to a previous point where it worked properly. It does not very often BSODs, but it is worth the chance.

    If you have an option to launch "Startup Repair" when you start your computer, let it work there.

    If you have the original supplied with your laptop disks, or you have created system recovery discs, you can try to put that. When it starts, it takes an option to try to fix the system.

    Honestly, if none of these work, my suggestion is that we do a complete reinstallation of the operating system. You will need the recovery disc, either made from your system when you got it, discs that were shipped with your system, or you should be able to recovery media order of HP.

    Hope this helps. Unfortunately the blue screens of death are called who for any reason... I would like to know if you need more explanation on what it, or to help with any of these steps.

  • STOP: 0x0000008E (0xC0000005, 0xBF9568C8, 0xA6864C00, 0x00000000) win32k.sys - address BF9568C8 base at BF800000, Date stamp 4ff2f633

    Hi, I get a blue screen frequently with the below error message.
    "Technical information:
    A problem has been detected and windows has shut down to prevent damage to your computer.

    STOP: 0X0000008E (0XC0000005, 0XBF9568C8, 0XA6864C00, 0X00000000)
    Win32k.sys - address BF9568C8 base at BF800000, Date stamp 4ff2f633

    Beginning physical memory dump.
    Complete physical memory dump.
    For more assistance, contact your system administrator or technical support.  "
    I am using Packard bell Easynote MX45.
    XP Home edition Version 2002
    SP3
    Inter (R) CPU [email protected] GHz.
    3 GB Ram
    could someone help me fix it please.

    N

    You are better able to tell us if the problem is resolved.  Continue to run Malwarebytes about once a week.  If the BSOD ceased and MBAM does not show any other infection, you're probably good.

  • Blue screen... STOP: 0x0000008E (0xC0000005, 0xBF8B6C11, 0xA9538368, 0x00000000) win32k.sys - address BF8B6C11 base address BF800000 DateStamp 4C7d06ce

    I have a Dimension 3000 bought in 2005, upgraded to 2 GB of RAM.

    I recently implemented almost from scratch, because Opera program and profile would be repeatedly corrupted, making me lose the email. (This reappeared even after reinstall opera clean, do not use old messages or other profile files). Therefore, I restored a backup of the C: partition Ghost (there are others for my data and downloads) I did shortly after the purchase, after which I had installed only Ghost and two games (I uninstalled the games). I installed SP3 and ran Microsoft Update. I was trying to reinstall other programs that I use now. It's Rhapsody; one of my kids 'synchronize' a player MP3 Sansa Fuze with Rhapsody.

    A few days ago when closing Internet Explorer, I got a message that should be closed and I could send a report to Microsoft. It is also used to happen before, from time to time.

    Then, more recently, when I closed Rhapsody, I got a blue screen with a message that there was a problem. He said I could try to change some settings in the BIOS. I remember what happens before I restored the ghost of 2005 BU. I looked in the BIOS and not able to find the parameters referred to in (something like memory cache). I wish it were possible to print these messages on a blue screen. I didn't copy the entire message, but I write these references:

    STOP: 0X0000008E (0XC0000005, 0XBF8B6C11, 0XA9538368, 0X00000000)

    Win32k.sys - address BF8B6C11 base address BF800000 DateStamp 4C7d06ce

    This means almost nothing to me. I hope that someone on the forum knows what this means and can suggest what could be the problem.

    So far, I have not had more wrong with Opera, so there may be two distinct problems. OTOH, I reinstalled only Opera on 10/12/10; I can still have problems with it.

    Hello

    Here is more information on the bug 0x8E control: http://support.microsoft.com/kb/945658/

    The 0x8E KERNEL_MODE_EXCEPTION_NOT_HANDLED can be caused by a faulty service/driver, damaged hard drive or defective display card not enough space, or memory, Hardware/software incompatibility and third-party remote control software. So to get started:

    1. test your memory. Run Memtest you can download from http://www.memtest.org/#downiso. Download the ZIP file, extract the ISO and write on CD. Once written to CD, boot your PC with the CD and run Memtest. Allow the test to run by at least 3 passes or until it gives errors. If you have more than 1 memory module, run the test on each module separately. Try running Memtest from a cold - start unplug your PC for an hour to cool down, then immediately run memtest again when you next turn on the. This way memtest will run when the memory is cool and after the 3rd pass when the memory is hottest.

    2. update your display driver. Reference Dell seems to have highlighted 3 different models of Dimension 3000 and so there is 3 different Intel display drivers. See if you can find an updated driver on the Intel Web site. If you use a graphics add-on card try to find an updated driver from the manufacturer's website. If you have any trouble finding a driver let us know what brand and model of graphics card you have.

    3. update the Rhapsody software. (I think it's the software you using http://www.rhapsody.com/-software ?). If it's Rhapsody software I think it seems to integrate into your Web browser and it's perhaps why Opera and now IE are mistakes? You can uninstall Rhapsody for a while just to see if it is the reason for your BSOD.

    4. when the 0x8E BSOD is caused by win32k.sys, yours, is it then possible, it is caused by control software remote third. It can include programs such as VNC, PCAnywhere, etc. of Teamviewer, RAdmin.  If you use one of these programs, uninstall it and see if the PC stops mistakes.

    5 run a scan on your hard drive. You can check your hard disk for errors by going toStart ->Run -> type chkdsk c: /r -> clickOk . When asked if you want to force a sayNodisassembly. When asked to plan the audit at the next startup, Yes. Reboot your PC to allow running chkdsk.

    Alternatively, you can run a diagnostic on your hard drive. This by downloading the diagnostic program from your hard disk manufacturer. A list of manufacturers and their diagnostic tools can be found here: http://www.tacktech.com/display.cfm?ttid=287. Once more, download the ZIP file, extract the ISO and write to CD. A time written on CD, boot your PC with the CD and run the test Advanced/extended.

    Also make sure you have enough hard disk space. It is always recommended, if possible, to have at least 15% of your free hard disk capacity.

    6. Finally, take a look in your event viewer when the BSOD for possible errors. You want to look especially in the system and Application logs (and maybe Internet Explorer connects). You can run Event Viewer by going toStart ->Run -> type eventvwr.msc -> pressOk -> event viewer screen opens. If there are errors listed in one of the newspapers type them in your next post if you are not right.

    Reading your post I see 3 specific issues, that you might want to focus:

    -The memory you added (run Memtest) and hard drive (run Chkdsk)

    -The Rhapsody program - try to update or uninstall.

    -The software was initially corrupted until you make the first image after the purchase. So you just ghost the problem on.

    I hope this helps. Good luck.

  • My Windows 7 keeps freezing or crashing randomly (BSOD)

    I am on Windows 7 Ultimate and my laptop Compaq Presario CQ61 guard randomly freezing or crashing. It got so bad now that yesterday, I was only able to apply some of the tools such as Fix It in Mode safe, now I can start my laptop and it works but freezes usually about 15 minutes.

    This is a report generated by «WhoCrashed»

    All pilots seem to be uptodate.

    (Local) information system

    computer name: xxx - PC
    Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    Windows dir: C:\Windows
    Hardware: Compaq Presario CQ61 Notebook PC, Hewlett-Packard, 3069
    CPU: GenuineIntel Pentium (r) Dual-Core processor T4400 @ 2.20 GHz Intel586, level: 6
    2 logical processors, active mask: 3
    RAM: 3119435776 total

    Crash Dump Analysis

    Crash dump directory: C:\Windows\Minidump

    Dumps are enabled on your computer.

    Tuesday, April 21, 2015 3:45:55 PM GMT crashed your computer
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: win32k.sys (win32k! EngTextOut + 0 x 26)
    Bugcheck code: 0x7A (0xFFFFFFFFC0000185, 0x460938C0, 0xFFFFFFFFC07F2E10, 0xFFFFFFFFFE5C2004)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: Multi-User Win32 Driver
    Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
    The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

    Saturday, September 13, 2014 8:36:36 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\091314 -.dmp
    This was probably caused by the following module: athr.sys (athr + 0x428A5)
    Bugcheck code: 0xD1 (30, 0 x 2, 0 x 0 x 0, 0xFFFFFFFF938618A5)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\
    Friday, September 12, 2014 9:08:40 AM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\091214-
    Wednesday, June 25, 2014 8:17:18 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\062514-
    Monday, June 23, 2014 8:55:18 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\062314-
    Thursday, June 5, 2014 19:8:15 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\060514-
    Sunday, May 11, 2014 8:42:17 PM GMT crashed your computer
    crash dump file: C:\Windows\Minidump\051114 -.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt + 0 x 120996)
    Bugcheck code: 0x19 (0x3, 0xFFFFFFFF88A94620, 0xFFFFFFFF88A94620, 0x3A51)
    Error: BAD_POOL_HEADER
    path: C:\Windows\system32\ntkrnlpa.
    Wednesday, April 9, 2014 14:48:52 this computer crashed
    crash dump file: C:\Windows\Minidump\040914-

    Conclusion
    8 dumps were found and analysed. 3 third-party drivers have been identified to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

    Igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
    ATHR.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
    dlkmd.sys (DisplayLink WDDM KMD, DisplayLink Corp.)

    If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

    Read the GENERAL WARNINGS for the failures of the system troubleshooting section for more information.

    Note that it is not always possible to say with certainty if a reported driver is responsible for her crash your system or that the cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

    PJ

    Still on the same pilot (HIDCLASS. (SYS).  You have still 2 malware apps (Isafe & AVG) assets.  I remove them both and using MSE instead

    http://www.Microsoft.com/security_essentials/

  • BSOD, ntfs.sys and ntsokrnl.exe

    Hello, all.

    I have a user who has had multiple bluescreens than to the end. Initially, it started with the ntfs.sys driver crashing, but quickly turned to the subsequent accidents ntoskrnl. Started about a month apart, now much more frequent. I ran Dell startup diags, who spent all on board. I then updated / replaced every driver/chipset in the system and the BIOS. His current running Windows 7 Enterprise 64 bits in an environment of business and another user is to have what would be similar BSOD, but more specifically the ntfs.sys file. This is the discharge for the accidents. Any direction on where to take this would be greatly appreciated. Thank you!

    Thursday, March 5, 2015 18:55:01 this computer crashed
    crash dump file: C:\WINDOWS\Minidump\030515-11466-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
    Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Thursday, March 5, 2015 18:55:01 this computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
    Bugcheck code: 0x9F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
    This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Tuesday, March 3, 2015 11:52:00 PM GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\030315-11216-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
    Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4040, 0xFFFFF80000B9C3D0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Friday, February 20, 2015 7:57:23 PM GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\022015-11902-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8008B34060, 0xFFFFF80000B9C3D8, 0xFFFFFA8004BFDBD0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
    This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Wednesday, February 18, 2015 12:03:26 AM GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\021715-8236-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
    Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039C8040, 0xFFFFF80000B9C3D0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Tuesday, February 17, 2015 11:48:29 PM GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\021715-10374-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
    Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF80000B9C3D0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    Tuesday, January 13, 2015 18:26:12 GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\011315-20451-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x78A8A)
    Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4660, 0xFFFFF8000478D3D0)
    Error: CUSTOM_ERROR
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

    On Monday, December 8, 2014 6:39:14 PM GMT crashed your computer
    crash dump file: C:\WINDOWS\Minidump\120814-15459-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 4211)
    Verification of error code: 0 x 24 (0xFFFFF880089ECCE8, 0xFFFFF880089EC540, 0x1904FB, 0xFFFFF880016D21D9)
    Error: NTFS_FILE_SYSTEM
    file path: C:\WINDOWS\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: NT file system driver
    Bug control description: This indicates there is a problem in the NTFS file system.
    The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

    The accident that produced this result is more than a month old, but I think that it always reflects exactly what the origins of the system to blue screen.

    1000009F error checking, {4, 258, fffffa80039b4660, fffff8000478d3d0}

    Failed to load image \SystemRoot\system32\DRIVERS\USA19Hx64.sys, 0n2 error Win32
    WARNING: unable to verify timestamp for USA19Hx64.sys
    ERROR: Module load completed but symbols can be loaded for USA19Hx64.sys
    WARNING: Unable to verify timestamp for win32k.sys
    ERROR: Module load completed but symbols can be loaded for win32k.sys
    Probably caused by: memory_corruption

    Follow-up: memory_corruption

    Loaded symbol image file: USA19Hx64.sys
    Image path: \SystemRoot\system32\DRIVERS\USA19Hx64.sys
    Image name: USA19Hx64.sys
    Timestamp: Thu Oct 30 15:52:45 2007 (47278B8D)

    USA19Hx64.sys, is a part of driver for Keyspan USB Serial Adapter ver: 3.7. Please update the driver, or uninstall the hardware/cable? If you can not.

    Keyspan® products.
    http://www.tripplite.com/LP/Keyspan/

    [Peripheral problem]

    Device PNP_Device_ID Error_Code
    Cisco Systems VPN Adapter for 64-bit Windows ROOT\NET\0000 this device is disabled.

  • Random BSOD at startup, sometimes perhaps 2 to 4 times a week

    Hello world
    First of all thanks for trying to help.  I was make a random BSOD from time to time at startup.  I have the minidump file that is downloaded and have an html element.  Before that all the tech news goes, I have a few things more talk, my video drivers have been updated since the BSOD first started to appear.  No hardware changes.  At one point I had to reinstall windows because of a complete failure, but since then have only this random BSOD.  Who started about 3 weeks to a month after the relocation.  I don't remember changing all programs, install any programs, or anything of the kind just before or a few days before the show began.

    https://SkyDrive.live.com/embed?CID=0733068D2B88BF3D&RESID=733068D2B88BF3D%21170&AuthKey=AJEH51CFK5T4kUs

    I hope that you are not seen any problems by looking at the file.  It's the actual error I receive on the loading of windows.

    BCCode: 1000007e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF88013DD3DB1
    BCP3: FFFFF880033693D8
    BCP4: FFFFF88003368C30
    OS version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    In addition, my dxdiag 64 results;

    ------------------
    Information System
    ------------------
    Time of this report: 01 22, 2014, 16:24:02
    Computer name: DERRICK-PC
    Operating system: Windows 7 Home Premium 64 - bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828) - 1532
    Language: English (regional setting: English)
    Manufacturer: Gigabyte Technology Co., Ltd..
    System model: GA-970-a - UD3
    BIOS: Award BIOS v6.00PG Modular
    Processor: AMD FX (tm) - 8350 eight cores processor (8 CPUs), ~4.0GHz
    Memory: RAM 8192MB
    Available OS memory: 8174MB RAM
    Page file: MB used 1938, 14406-MB of available space
    Windows Dir: C:\Windows
    DirectX version: DirectX 11
    DX setup parameters: not found
    DPI setting: Using System DPI
    System DPI setting: 96 DPI (100%)
    DWM DPI Scaling: disabled
    DxDiag Version: 6.01.7601.17514 64 bit Unicode

    ------------
    DxDiag Notes
    ------------
    Display 1 tab: The file aticfx64.dll, aticfx64.dll, aticfx64.dll, aticfx32, aticfx32, aticfx32, atiumd64.dll, atidxx64.dll, atidxx64.dll, atiumdag, atidxx32, atidxx32, atiumdva, atiumd6a.cap, atitmm64.dll is not signed digitally, it means that it has not been tested by Microsoft Windows Hardware Quality Labs (WHQL).  You may be able to obtain a WHQL logo driver from the hardware manufacturer.
    Sound tab 1: No problems found.
    2 Audio tab: No problems found.
    3 Audio tab: No problems found.
    Input tab: no problems found.

    --------------------
    DirectX Debug levels
    --------------------
    Direct3D: 0/4 (detail)
    DirectDraw: 0/4 (detail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay: 0/9 (detail)
    DirectSound: 0/5 (retail)
    DirectShow: 0/6 (detail)

    ---------------
    Display devices
    ---------------
    Card name: AMD Radeon HD 7700 Series
    Manufacturer: Advanced Micro Devices, Inc.
    Track type: processor AMD Radeon Graphics (0x683D)
    DAC type: DAC (400 MHz) internal
    The device key: Enum\PCI\VEN_1002 & DEV_683D & SUBSYS_20141787 & REV_00
    Memory display: 740 MB
    Dedicated memory: 1006 MB
    Shared memory: 3830 MB
    Current mode: 1680 x 1050 (32 bit) (60 Hz)
    Name of the monitor: Acer monitor LCD P201W
    Monitor model: Acer P201W
    Monitor ID: ACR0007
    Native mode: 1680 x 1050 (p) (59,883 Hz)
    Output type: DVI
    Driver name: aticfx64.dll, aticfx64.dll, aticfx64.dll, aticfx32, aticfx32, aticfx32, atiumd64.dll, atidxx64.dll, atidxx64.dll, atiumdag, atidxx32, atidxx32, atiumdva, atiumd6a.cap, atitmm64.dll
    The driver file version: 8.17.0010.1242 (English)
    Driver version: 13.200.11.0
    DDI version: 11
    : Model WDDM 1.1 driver
    Driver attributes: Final retail
    Format/driver Date: 05/09/2013-02:01:18, 1287152 bytes
    WHQL Logo would be: No.
    WHQL Date stamp: no
    The instrument identifier: {D7B71EE2-2B7D-11CF-ED70-1E00BEC2C535}
    Vendor ID: 0 x 1002
    Device ID: 0x683D
    SubSys ID: 0 x 20141787
    Revision ID: 0x0000
    Strong name of the driver: oem17.inf:ATI. Mfg.NTamd64.6.1:ati2mtag_R575A:13.200.11.0:pci\ven_1002&dev_683d
    The driver rating: 00E62001
    Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
    Deinterlace caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: caps Frames(Prev/Fwd/Back) = (0,0,1) (In/Out) Format (YUY2, YUY2) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: caps Frames(Prev/Fwd/Back) = (0,0,0) (In/Out) Format (YUY2, YUY2) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: caps Frames(Prev/Fwd/Back) = (0,0,0) Format (In/Out) = (YUY2, YUY2) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: caps Frames(Prev/Fwd/Back) = (0,0,1) (In/Out) Format (UYVY, UYVY) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: caps Frames(Prev/Fwd/Back) = (0,0,0) (In/Out) Format (UYVY, UYVY) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: caps Frames(Prev/Fwd/Back) = (0,0,0) Format (In/Out) = (UYVY, UYVY) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) (YV12, 0 x 32315659) = Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: caps Frames(Prev/Fwd/Back) = (0,0,2) (In/Out) Format (NV12, 0x3231564e) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: caps Frames(Prev/Fwd/Back) = (0,0,2) (In/Out) Format (NV12, 0x3231564e) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: caps Frames(Prev/Fwd/Back) = (0,0,1) (In/Out) Format (NV12, 0x3231564e) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: caps Frames(Prev/Fwd/Back) = (0,0,0) (In/Out) Format (NV12, 0x3231564e) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: caps Frames(Prev/Fwd/Back) = (0,0,0) (In/Out) Format (NV12, 0x3231564e) = VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (IMC1, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (IMC2, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (IMC3, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (IMC4, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (S340, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format (In/Out) = (S342, UNKNOWN) Frames(Prev/Fwd/Back) = (0,0,0) Caps
    D3d9 Overlay: Unsupported
    DXVA-HD: not supported
    DDraw status: enabled
    D3D status: enabled
    AGP status: enabled

    -------------
    Sound Devices
    -------------
    Description: Speakers (Realtek High Definition Audio)
    Default audio playback: Yes
    Default voice playback: no
    Hardware ID: HDAUDIO\FUNC_01 & VEN_10EC & DEV_0889 & SUBSYS_1458A002 & REV_1000
    Manufacturer ID: 1
    Product ID: 100
    Type: WDM
    Driver name: RTKVHD64.sys
    Driver version: 6.00.0001.6482 (English)
    Driver attributes: Final retail
    Would be WHQL logo: Yes
    Date and size: 2011-10-18 05:53:14, 2957544 bytes
    Other files:
    Driver provider: Realtek Semiconductor Corp.
    HW Accel level: basic
    Cap flags: 0xF1F
    Min/Max sample rate: 100, 200000
    Mix beef static/Strm HW: 1, 0
    Static/Strm HW 3D steers: 0, 0
    HW memory: 0
    Management of the voice: No.
    Listen/Src/EAX (TM) 2.0: No, no
    Listen/Src/I3DL2 (TM): No, no
    Sensaura (TM) ZoomFX (tm): No.

    Description: Realtek Digital Output (Optical) (Realtek High Definition Audio)
    Default audio playback: No.
    Default voice playback: no
    Hardware ID: HDAUDIO\FUNC_01 & VEN_10EC & DEV_0889 & SUBSYS_1458A002 & REV_1000
    Manufacturer ID: 1
    Product ID: 100
    Type: WDM
    Driver name: RTKVHD64.sys
    Driver version: 6.00.0001.6482 (English)
    Driver attributes: Final retail
    Would be WHQL logo: Yes
    Date and size: 2011-10-18 05:53:14, 2957544 bytes
    Other files:
    Driver provider: Realtek Semiconductor Corp.
    HW Accel level: basic
    Cap flags: 0xF1F
    Min/Max sample rate: 100, 200000
    Mix beef static/Strm HW: 1, 0
    Static/Strm HW 3D steers: 0, 0
    HW memory: 0
    Management of the voice: No.
    Listen/Src/EAX (TM) 2.0: No, no
    Listen/Src/I3DL2 (TM): No, no
    Sensaura (TM) ZoomFX (tm): No.

    Description: Realtek Digital Output (Realtek High Definition Audio)
    Default audio playback: No.
    Default voice playback: Yes
    Hardware ID: HDAUDIO\FUNC_01 & VEN_10EC & DEV_0889 & SUBSYS_1458A002 & REV_1000
    Manufacturer ID: 1
    Product ID: 100
    Type: WDM
    Driver name: RTKVHD64.sys
    Driver version: 6.00.0001.6482 (English)
    Driver attributes: Final retail
    Would be WHQL logo: Yes
    Date and size: 2011-10-18 05:53:14, 2957544 bytes
    Other files:
    Driver provider: Realtek Semiconductor Corp.
    HW Accel level: basic
    Cap flags: 0xF1F
    Min/Max sample rate: 100, 200000
    Mix beef static/Strm HW: 1, 0
    Static/Strm HW 3D steers: 0, 0
    HW memory: 0
    Management of the voice: No.
    Listen/Src/EAX (TM) 2.0: No, no
    Listen/Src/I3DL2 (TM): No, no
    Sensaura (TM) ZoomFX (tm): No.

    ---------------------
    Sound Capture devices
    ---------------------
    -------------------
    DirectInput devices
    -------------------
    Device name: mouse
    Joint: 1
    Controller ID: n/a
    Vendor/product ID: n/a
    FF driver: n/a

    Device name: keyboard
    Joint: 1
    Controller ID: n/a
    Vendor/product ID: n/a
    FF driver: n/a

    Device name: the HID-compliant consumer control device
    Joint: 1
    Controller ID: 0 x 0
    Suppliers of products/ID: 0xFEEB, 0xDEEF
    FF driver: n/a

    Device name: USB keyboard
    Joint: 1
    Controller ID: 0 x 0
    Suppliers of products/ID: 0x1A2C, 0x0C21
    FF driver: n/a

    Device name: USB keyboard
    Joint: 1
    Controller ID: 0 x 0
    Suppliers of products/ID: 0x1A2C, 0x0C21
    FF driver: n/a

    Poll w / Interrupt: No.

    -----------
    USB devices
    -----------
    + USB root hub
    | Suppliers of products/ID: 0 x 1002, 0 x 4397
    | Matching Device ID: usb\root_hub
    | Service: usbhub
    | Driver: usbhub.sys, 26/11/2013 19:41:37, 343040 bytes
    | Driver: usbd.sys, 26/11/2013 19:41:03, 7808 bytes

    ----------------
    Gameport devices
    ----------------

    ------------
    PS/2 devices
    ------------
    + Keyboard HID device
    | Suppliers of products/ID: 0x1A2C, 0x0C21
    | Matching Device ID: hid_device_system_keyboard
    | Service: kbdhid
    | Driver: kbdhid.sys, 20/11/2010 21:23:47, 33280 bytes
    | Driver: kbdclass.sys, 13/07/2009 19:48:04, 50768 bytes
    |
    + Server terminal keyboard driver
    | Matching Device ID: root\rdp_kbd
    | High filters: kbdclass
    | Service: TermDD
    | Driver: i8042prt.sys, 13/07/2009 17:19:57, 105472 bytes
    | Driver: kbdclass.sys, 13/07/2009 19:48:04, 50768 bytes
    |
    + HID-compliant mouse
    | Suppliers of products/ID: 0x093A, 0 x 2521
    | Matching Device ID: hid_device_system_mouse
    | Service: me
    | Driver: mouhid.sys, 13/07/2009 18:00:20, 31232 bytes
    | Driver: mouclass.sys, 13/07/2009 19:48:27, 49216 bytes
    |
    + HID-compliant mouse
    | Suppliers of products/ID: 0x1A2C, 0x0C21
    | Matching Device ID: hid_device_system_mouse
    | Service: me
    | Driver: mouhid.sys, 13/07/2009 18:00:20, 31232 bytes
    | Driver: mouclass.sys, 13/07/2009 19:48:27, 49216 bytes
    |
    + Terminal Server mouse driver
    | Matching Device ID: root\rdp_mou
    | High filters: mouclass
    | Service: TermDD
    | Driver: termdd.sys, 20/11/2010 21:23:47, 63360 bytes
    | Driver: sermouse.sys, 13/07/2009 18:00:20, 26624 bytes
    | Driver: mouclass.sys, 13/07/2009 19:48:27, 49216 bytes

    ------------------------
    Disk & CD-ROM/DVD-ROM readers
    ------------------------
    Drive: C:
    Free space: 109,0 GB
    Total space: 476.8 GB
    File system: NTFS
    Model: WDC WD5000AAKX-00ERMA0 ATA Device

    Drive: D:
    Model: TSSTcorp CDDVDW SH-224BB ATA Device
    Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 147456 bytes

    --------------
    System devices
    --------------
    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1603 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C3
    Pilot: s/o

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_5A1D & SUBSYS_5A141002 & REV_00\3 & 2B8E0B4B & 0 & 50
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: Standard double channel PCI IDE Controller
    Device ID: PCI\VEN_1002 & DEV_439C & SUBSYS_50021458 & REV_40\3 & 2B8E0B4B & 0 & A1
    Pilot: C:\Windows\system32\DRIVERS\pciide.sys, 6.01.7600.16385 (in English), 2009-07-13 19:45:45, 12352 bytes
    Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.01.7600.16385 (in English), 2009-07-13 19:45:46, 48720 bytes
    Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.01.7600.16385 (in English), 2009-07-13 19:52:21, 24128 bytes
    Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.01.7601.18231 (English), 04/08/2013-20:25:45, 155584 bytes

    Name: Standard double channel PCI IDE Controller
    Device ID: PCI\VEN_1002 & DEV_4390 & SUBSYS_B0021458 & REV_40\3 & 2B8E0B4B & 0 & 88
    Pilot: C:\Windows\system32\DRIVERS\pciide.sys, 6.01.7600.16385 (in English), 2009-07-13 19:45:45, 12352 bytes
    Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.01.7600.16385 (in English), 2009-07-13 19:45:46, 48720 bytes
    Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.01.7600.16385 (in English), 2009-07-13 19:52:21, 24128 bytes
    Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.01.7601.18231 (English), 04/08/2013-20:25:45, 155584 bytes

    Name: Turd USB 3.0 Extensible Host Controller
    Device ID: PCI\VEN_1B6F & DEV_7023 & SUBSYS_50071458 & REV_01\4 & 8CB6D41 & 0 & 0020
    Driver: C:\Windows\SYSTEM32\DRIVERS\EtronXHCI.sys, 0.00.0000.0104 (English), 28/07/2011-21:40, 79104 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1602 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C2
    Pilot: s/o

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_5A1C & SUBSYS_5A141002 & REV_00\3 & 2B8E0B4B & 0 & 48
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: OpenHCD Standard USB host controller
    Device ID: PCI\VEN_1002 & DEV_4399 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & A5
    Pilot: C:\Windows\system32\drivers\usbohci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:09, 25600 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: ATI i/o Communications Processor SMBus Controller
    Device ID: PCI\VEN_1002 & DEV_4385 & SUBSYS_00000000 & REV_42\3 & 2B8E0B4B & 0 & A0
    Pilot: s/o

    Name: Turd USB 3.0 Extensible Host Controller
    Device ID: PCI\VEN_1B6F & DEV_7023 & SUBSYS_50071458 & REV_01\4 & 2CF03ACF & 0 & 0050
    Driver: C:\Windows\SYSTEM32\DRIVERS\EtronXHCI.sys, 0.00.0000.0104 (English), 28/07/2011-21:40, 79104 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1601 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C1
    Pilot: s/o

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_5A19 & SUBSYS_5A141002 & REV_00\3 & 2B8E0B4B & 0 & 28
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: OpenHCD Standard USB host controller
    Device ID: PCI\VEN_1002 & DEV_4397 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & B0
    Pilot: C:\Windows\system32\drivers\usbohci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:09, 25600 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: ATI i/o Communications Processor PCI Bus controller
    Device ID: PCI\VEN_1002 & DEV_4384 & SUBSYS_00000000 & REV_40\3 & 2B8E0B4B & 0 & A4
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: Qualcomm Atheros AR5BWB222 Wireless Network adapt
    Device ID: PCI\VEN_168C & DEV_0034 & SUBSYS_662111AD & REV_01\4 & 125C753F & 0 & 0028
    Driver: C:\Windows\system32\DRIVERS\athrx.sys, 10.00.0000.0067 (English), 14/06/2012 00:23:12, 3678720 bytes
    Driver: C:\Windows\system32\drivers\vwifibus.sys, 6.01.7600.16385 (in English), 2009-07-13 18:07:21, 24576 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1600 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C0
    Pilot: s/o

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_5A18 & SUBSYS_5A141002 & REV_00\3 & 2B8E0B4B & 0 & 20
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: OpenHCD Standard USB host controller
    Device ID: PCI\VEN_1002 & DEV_4397 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & 98
    Pilot: C:\Windows\system32\drivers\usbohci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:09, 25600 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: High Definition Audio Controller
    Device ID: PCI\VEN_1002 & DEV_4383 & SUBSYS_A0021458 & REV_40\3 & 2B8E0B4B & 0 & A2
    Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 122368 bytes

    Name: VIA 1394 compatible OHCI Host Controller
    Device ID: PCI\VEN_1106 & DEV_3044 & SUBSYS_10001458 & REV_C0\4 & E7415D2 & 0 & A 70, 4
    Driver: C:\Windows\system32\DRIVERS\1394ohci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 229888 bytes

    Name: High Definition Audio Controller
    Device ID: PCI\VEN_1002 & DEV_AAB0 & SUBSYS_AAB01787 & REV_00\4 & 31B538E3 & 0 & 0110
    Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 122368 bytes

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_5A16 & SUBSYS_5A141002 & REV_00\3 & 2B8E0B4B & 0 & 10
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: OpenHCD Standard USB host controller
    Device ID: PCI\VEN_1002 & DEV_4397 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & 90
    Pilot: C:\Windows\system32\drivers\usbohci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:09, 25600 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: Realtek PCIe GBE Family Controller
    Device ID: PCI\VEN_10EC & DEV_8168 & SUBSYS_E0001458 & REV_06\4 & 36103136 & 0 & 0048
    Pilot: s/o

    Name: High Definition Audio Controller
    Device ID: PCI\VEN_1002 & DEV_AAB0 & SUBSYS_AAB01787 & REV_00\4 & 2BD43E08 & 0 & 01 A 8
    Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 122368 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1002 & DEV_5A14 & SUBSYS_5A141002 & REV_02\3 & 2B8E0B4B & 0 & 00
    Pilot: s/o

    Name: Standard enhanced PCI to USB Host Controller
    Device ID: PCI\VEN_1002 & DEV_4396 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & B2
    Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 53248 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1605 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C5
    Pilot: s/o

    Name: AMD Radeon HD 7700 Series
    Device ID: PCI\VEN_1002 & DEV_683D & SUBSYS_20141787 & REV_00\4 & 31B538E3 & 0 & 0010
    Driver: C:\Windows\system32\DRIVERS\atikmdag.sys, 8.01.0001.1345 (English), 05/09/2013-01:59:10, 12653568 bytes
    Driver: C:\Windows\system32\DRIVERS\ati2erec.dll, 1.00.0000.0024 (English), 05/09/2013-00:29:40, 43520 bytes
    Driver: C:\Windows\system32\DRIVERS\atikmpag.sys, 8.14.0001.6347 (English), 05/09/2013-00:33:34, 617984 bytes
    Driver: C:\Windows\system32\atiumd64.dll, 9.14.0010.0991 (English), 05/09/2013-02:00:52, 7625784 bytes
    Driver: C:\Windows\system32\atiumd6a.dll, 8.14.0010.0422 (English), 05/09/2013-02:00:54, 7128240 bytes
    Driver: C:\Windows\system32\atitmm64.dll, 6.14.0011.0025 (English), 05/09/2013-01:01:50, 190976 bytes
    Driver: C:\Windows\system32\atiicdxx.dat, 10/04/2013 09:34:24, 662785 bytes
    Driver: C:\Windows\system32\amdpcom64.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 78432 bytes
    Driver: C:\Windows\system32\atimpc64.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 78432 bytes
    Driver: C:\Windows\system32\atiadlxx.dll, 6.14.0010.1129 (English), 05/09/2013-00:34:34, 1097728 bytes
    Driver: C:\Windows\system32\atiumd6a.cap, 05/09/2013 00:47:16, 3399312 bytes
    Driver: C:\Windows\system32\atimuixx.dll, 6.14.0010.1002 (English), 05/09/2013-01:04:22, 26112 bytes
    Driver: C:\Windows\system32\atiapfxx.exe, 6.14.0010.1001 (English), 05/09/2013-01:24:32, 368640 bytes
    Driver: C:\Windows\system32\ativvsva.dat, 05/09/2013 00:44:28, 157144 bytes
    Driver: C:\Windows\system32\ativvsvl.dat, 05/09/2013 00:44:28, 204952 bytes
    Driver: C:\Windows\system32\ativvaxy_cik.dat, 18/07/2013 09:38:38, 233396 bytes
    Driver: C:\Windows\system32\ativvaxy_cik_nd.dat, 18/07/2013 09:47:16, 231856 bytes
    Driver: C:\Windows\system32\ativce02.dat, 15/07/2013 10:29:22, 82944 bytes
    Driver: C:\Windows\system32\atiesrxx.exe, 6.14.0011.1161 (English), 05/09/2013-01:03:22, 239616 bytes
    Driver: C:\Windows\system32\atieclxx.exe, 6.14.0011.1161 (English), 05/09/2013-01:04:14, 574976 bytes
    Driver: C:\Windows\system32\atidemgy.dll, 4.05.4996.3736 (English), 05/09/2013-01:04:32, 442368 bytes
    Driver: C:\Windows\system32\atio6axx.dll, 6.14.0010.12441 (English), 05/09/2013-01:25:16, 25611264 bytes
    Driver: C:\Windows\system32\aticalrt64.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:22, 62464 bytes
    Driver: C:\Windows\system32\aticalcl64.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:12, 55808 bytes
    Driver: C:\Windows\system32\aticaldd64.dll, 6.14.0010.1848 (English), 05/09/2013-01:23:54, 15716352 bytes
    Driver: C:\Windows\system32\atipblag.dat, 12/09/2011 16:06:16, 3917 bytes
    Driver: C:\Windows\system32\atiu9p64.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:20, 115512 bytes
    Driver: C:\Windows\system32\atiuxp64.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:22, 143304 bytes
    Driver: C:\Windows\system32\atig6pxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:04, 75264 bytes
    Driver: C:\Windows\system32\atig6txx.dll, 8.14.0001.6347 (English), 05/09/2013-00:33:54, 100352 bytes
    Driver: C:\Windows\system32\atibtmon.exe, 2.00.0000.0000 (English), 10/04/2013 09:34:24, 118784 bytes
    Driver: C:\Windows\system32\atiapfxx.blb, 05/09/2013 01:24:58, 552152 bytes
    Driver: C:\Windows\system32\atidxx64.dll, 8.17.0010.0514 (English), 05/09/2013-02:01:12, 9067808 bytes
    Driver: C:\Windows\SysWOW64\atiumdag.dll, 9.14.0010.0991 (English), 05/09/2013-02:01, 6549928 bytes
    Driver: C:\Windows\SysWOW64\atiumdva.dll, 8.14.0010.0422 (English), 05/09/2013-02:01:04, 6502024 bytes
    Driver: C:\Windows\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 71704 bytes
    Driver: C:\Windows\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 71704 bytes
    Driver: C:\Windows\SysWOW64\atiadlxy.dll, 6.14.0010.1129 (English), 05/09/2013-00:34:20, 828416 bytes
    Driver: C:\Windows\SysWOW64\atiumdva.cap, 05/09/2013 00:36:32, 3433360 bytes
    Driver: C:\Windows\SysWOW64\ativvsva.dat, 05/09/2013 00:44:28, 157144 bytes
    Driver: C:\Windows\SysWOW64\ativvsvl.dat, 05/09/2013 00:44:28, 204952 bytes
    Driver: C:\Windows\SysWOW64\atioglxx.dll, 6.14.0010.12441 (English), 05/09/2013-01:06:48, 21624320 bytes
    Driver: C:\Windows\SysWOW64\atidxx32.dll, 8.17.0010.0514 (English), 05/09/2013-02:01:10, 7919328 bytes
    Driver: C:\Windows\SysWOW64\aticalrt.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:20, 52224 bytes
    Driver: C:\Windows\SysWOW64\aticalcl.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:10, 49152 bytes
    Driver: C:\Windows\SysWOW64\aticaldd.dll, 6.14.0010.1848 (English), 05/09/2013-01:20:50, 14302208 bytes
    Driver: C:\Windows\SysWOW64\atipblag.dat, 12/09/2011 16:06:16, 3917 bytes
    Driver: C:\Windows\SysWOW64\atiu9pag.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:20, 98496 bytes
    Driver: C:\Windows\SysWOW64\atiuxpag.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:22, 126336 bytes
    Driver: C:\Windows\SysWOW64\atigktxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:33:44, 96768 bytes
    Driver: C:\Windows\SysWOW64\atiglpxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:00, 69632 bytes
    Driver: C:\Windows\SysWOW64\atiapfxx.blb, 05/09/2013 01:24:58, 552152 bytes
    Driver: C:\Windows\atiogl.xml, 19/06/2013 12:32, 47378 bytes
    Driver: C:\Windows\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 10/04/2013 09:34:24, 51200 bytes
    Driver: C:\Windows\system32\ATIODE.exe, 1.00.0000.0001 (English), 10/04/2013 09:34:24, 332800 bytes
    Driver: C:\Windows\system32\atisamu64.dll, 7.01.0000.0001 (English), 05/09/2013-00:27:40, 89088 bytes
    Driver: C:\Windows\system32\amdhcp64.dll, 1.00.0000.0001 (English), 05/09/2013-02:01:30, 157736 bytes
    Driver: C:\Windows\system32\amdave64.dll, 5.05.0005.0004 (English), 05/09/2013-00:28:00, 95744 bytes
    Driver: C:\Windows\SysWOW64\amdave32.dll, 5.05.0005.0004 (English), 05/09/2013-00:27:54, 90112 bytes
    Driver: C:\Windows\SysWOW64\atisamu32.dll, 7.01.0000.0001 (English), 05/09/2013-00:27:36, 80896 bytes
    Driver: C:\Windows\SysWOW64\amdhcp32.dll, 1.00.0000.0001 (English), 05/09/2013-02:01:30, 142304 bytes
    Driver: C:\Windows\system32\atiglpxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:00, 69632 bytes
    Driver: C:\Windows\system32\aticfx64.dll, 8.17.0010.1242 (English), 05/09/2013-02:01:18, 1287152 bytes
    Driver: C:\Windows\SysWOW64\aticfx32.dll, 8.17.0010.1242 (English), 05/09/2013-02:01:16, 1071328 bytes
    Driver: C:\Windows\system32\OpenCL.dll, 1.02.0011.0000 (English), 05/09/2013-01:41:02, 63488 bytes
    Driver: C:\Windows\system32\amdocl64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:04, 28445184 bytes
    Driver: C:\Windows\system32\amdocl_as64.exe, 05/09/2013 01:45:44, 1187342 bytes
    Driver: C:\Windows\system32\amdocl_ld64.exe, 05/09/2013 01:45:44, 1061902 bytes
    Driver: C:\Windows\system32\OpenVideo64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:40, 98816 bytes
    Driver: C:\Windows\system32\OVDecode64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:26, 86528 bytes
    Driver: C:\Windows\system32\clinfo.exe, 05/09/2013 01:45:56, 229888 bytes
    Driver: C:\Windows\SysWOW64\OpenCL.dll, 1.02.0011.0000 (English), 05/09/2013-01:40:58, 57344 bytes
    Driver: C:\Windows\SysWOW64\amdocl.dll, 10.00.1307.0001 (English), 05/09/2013-01:42:54, 23989248 bytes
    Driver: C:\Windows\SysWOW64\amdocl_as32.exe, 05/09/2013 01:45:42, 995342 bytes
    Driver: C:\Windows\SysWOW64\amdocl_ld32.exe, 05/09/2013 01:45:42, 798734 bytes
    Driver: C:\Windows\SysWOW64\OpenVideo.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:32, 83456 bytes
    Driver: C:\Windows\SysWOW64\OVDecode.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:22, 73216 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.ssz, 8.14.0001.6019 (English), 21/05/2013-17:38:38, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.sez, 8.14.0001.6019 (English), 21/05/2013-17:38:50, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.sbz, 8.14.0001.6019 (English), 21/05/2013-17:38:50, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.isz, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.iez, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.ibz, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.csz, 03/06/2013 23:16:38, 8095 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.cez, 03/06/2013 23:17:08, 9851 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.cbz, 03/06/2013 23:17:08, 9851 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDh264Enc32.dll, 1.00.0000.0001 (English), 05/09/2013-01:26:26, 235520 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDh264Enc64.dll, 1.00.0000.0001 (English), 05/09/2013-01:26:50, 278016 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDhwDecoder_32.dll, 1.00.0000.0001 (English), 05/09/2013-01:32:40, 195584 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDhwDecoder_64.dll, 1.00.0000.0001 (English), 05/09/2013-01:33:16, 232448 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTDecoder_32.dll, 1.00.15369.0331 (English), 05/09/2013-01:31:54, 98304 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTDecoder_64.dll, 1.00.15369.0331 (English), 05/09/2013-01:32:06, 121344 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTVideoDecoder_32.dll, 05/09/2013-02:00:50, 109832 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTVideoDecoder_64.dll, 05/09/2013 03:00:50, 132528 bytes
    Driver: C:\Windows\system32\coinst_13.20.11.dll, 1.00.0005.0009 (English), 05/09/2013-01:38:20, 129536 bytes

    Name: Bridge PCI to PCI standard PCI
    Device ID: PCI\VEN_1002 & DEV_43A0 & SUBSYS_00001002 & REV_00\3 & 2B8E0B4B & 0 & A8
    Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010-21:23:47, 184704 bytes

    Name: Standard enhanced PCI to USB Host Controller
    Device ID: PCI\VEN_1002 & DEV_4396 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & 9a
    Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 53248 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    Name: The standard host PCI bridge CPU
    Device ID: PCI\VEN_1022 & DEV_1604 & SUBSYS_00000000 & REV_00\3 & 2B8E0B4B & 0 & C4
    Pilot: s/o

    Name: AMD Radeon HD 7700 Series
    Device ID: PCI\VEN_1002 & DEV_683D & SUBSYS_20141787 & REV_00\4 & 2BD43E08 & 0 & 00A 8
    Driver: C:\Windows\system32\DRIVERS\atikmdag.sys, 8.01.0001.1345 (English), 05/09/2013-01:59:10, 12653568 bytes
    Driver: C:\Windows\system32\DRIVERS\ati2erec.dll, 1.00.0000.0024 (English), 05/09/2013-00:29:40, 43520 bytes
    Driver: C:\Windows\system32\DRIVERS\atikmpag.sys, 8.14.0001.6347 (English), 05/09/2013-00:33:34, 617984 bytes
    Driver: C:\Windows\system32\atiumd64.dll, 9.14.0010.0991 (English), 05/09/2013-02:00:52, 7625784 bytes
    Driver: C:\Windows\system32\atiumd6a.dll, 8.14.0010.0422 (English), 05/09/2013-02:00:54, 7128240 bytes
    Driver: C:\Windows\system32\atitmm64.dll, 6.14.0011.0025 (English), 05/09/2013-01:01:50, 190976 bytes
    Driver: C:\Windows\system32\atiicdxx.dat, 10/04/2013 09:34:24, 662785 bytes
    Driver: C:\Windows\system32\amdpcom64.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 78432 bytes
    Driver: C:\Windows\system32\atimpc64.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 78432 bytes
    Driver: C:\Windows\system32\atiadlxx.dll, 6.14.0010.1129 (English), 05/09/2013-00:34:34, 1097728 bytes
    Driver: C:\Windows\system32\atiumd6a.cap, 05/09/2013 00:47:16, 3399312 bytes
    Driver: C:\Windows\system32\atimuixx.dll, 6.14.0010.1002 (English), 05/09/2013-01:04:22, 26112 bytes
    Driver: C:\Windows\system32\atiapfxx.exe, 6.14.0010.1001 (English), 05/09/2013-01:24:32, 368640 bytes
    Driver: C:\Windows\system32\ativvsva.dat, 05/09/2013 00:44:28, 157144 bytes
    Driver: C:\Windows\system32\ativvsvl.dat, 05/09/2013 00:44:28, 204952 bytes
    Driver: C:\Windows\system32\ativvaxy_cik.dat, 18/07/2013 09:38:38, 233396 bytes
    Driver: C:\Windows\system32\ativvaxy_cik_nd.dat, 18/07/2013 09:47:16, 231856 bytes
    Driver: C:\Windows\system32\ativce02.dat, 15/07/2013 10:29:22, 82944 bytes
    Driver: C:\Windows\system32\atiesrxx.exe, 6.14.0011.1161 (English), 05/09/2013-01:03:22, 239616 bytes
    Driver: C:\Windows\system32\atieclxx.exe, 6.14.0011.1161 (English), 05/09/2013-01:04:14, 574976 bytes
    Driver: C:\Windows\system32\atidemgy.dll, 4.05.4996.3736 (English), 05/09/2013-01:04:32, 442368 bytes
    Driver: C:\Windows\system32\atio6axx.dll, 6.14.0010.12441 (English), 05/09/2013-01:25:16, 25611264 bytes
    Driver: C:\Windows\system32\aticalrt64.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:22, 62464 bytes
    Driver: C:\Windows\system32\aticalcl64.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:12, 55808 bytes
    Driver: C:\Windows\system32\aticaldd64.dll, 6.14.0010.1848 (English), 05/09/2013-01:23:54, 15716352 bytes
    Driver: C:\Windows\system32\atipblag.dat, 12/09/2011 16:06:16, 3917 bytes
    Driver: C:\Windows\system32\atiu9p64.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:20, 115512 bytes
    Driver: C:\Windows\system32\atiuxp64.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:22, 143304 bytes
    Driver: C:\Windows\system32\atig6pxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:04, 75264 bytes
    Driver: C:\Windows\system32\atig6txx.dll, 8.14.0001.6347 (English), 05/09/2013-00:33:54, 100352 bytes
    Driver: C:\Windows\system32\atibtmon.exe, 2.00.0000.0000 (English), 10/04/2013 09:34:24, 118784 bytes
    Driver: C:\Windows\system32\atiapfxx.blb, 05/09/2013 01:24:58, 552152 bytes
    Driver: C:\Windows\system32\atidxx64.dll, 8.17.0010.0514 (English), 05/09/2013-02:01:12, 9067808 bytes
    Driver: C:\Windows\SysWOW64\atiumdag.dll, 9.14.0010.0991 (English), 05/09/2013-02:01, 6549928 bytes
    Driver: C:\Windows\SysWOW64\atiumdva.dll, 8.14.0010.0422 (English), 05/09/2013-02:01:04, 6502024 bytes
    Driver: C:\Windows\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 71704 bytes
    Driver: C:\Windows\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 05/09/2013-02:01:28, 71704 bytes
    Driver: C:\Windows\SysWOW64\atiadlxy.dll, 6.14.0010.1129 (English), 05/09/2013-00:34:20, 828416 bytes
    Driver: C:\Windows\SysWOW64\atiumdva.cap, 05/09/2013 00:36:32, 3433360 bytes
    Driver: C:\Windows\SysWOW64\ativvsva.dat, 05/09/2013 00:44:28, 157144 bytes
    Driver: C:\Windows\SysWOW64\ativvsvl.dat, 05/09/2013 00:44:28, 204952 bytes
    Driver: C:\Windows\SysWOW64\atioglxx.dll, 6.14.0010.12441 (English), 05/09/2013-01:06:48, 21624320 bytes
    Driver: C:\Windows\SysWOW64\atidxx32.dll, 8.17.0010.0514 (English), 05/09/2013-02:01:10, 7919328 bytes
    Driver: C:\Windows\SysWOW64\aticalrt.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:20, 52224 bytes
    Driver: C:\Windows\SysWOW64\aticalcl.dll, 6.14.0010.1848 (English), 05/09/2013-01:24:10, 49152 bytes
    Driver: C:\Windows\SysWOW64\aticaldd.dll, 6.14.0010.1848 (English), 05/09/2013-01:20:50, 14302208 bytes
    Driver: C:\Windows\SysWOW64\atipblag.dat, 12/09/2011 16:06:16, 3917 bytes
    Driver: C:\Windows\SysWOW64\atiu9pag.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:20, 98496 bytes
    Driver: C:\Windows\SysWOW64\atiuxpag.dll, 8.14.0001.6347 (English), 05/09/2013-02:01:22, 126336 bytes
    Driver: C:\Windows\SysWOW64\atigktxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:33:44, 96768 bytes
    Driver: C:\Windows\SysWOW64\atiglpxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:00, 69632 bytes
    Driver: C:\Windows\SysWOW64\atiapfxx.blb, 05/09/2013 01:24:58, 552152 bytes
    Driver: C:\Windows\atiogl.xml, 19/06/2013 12:32, 47378 bytes
    Driver: C:\Windows\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 10/04/2013 09:34:24, 51200 bytes
    Driver: C:\Windows\system32\ATIODE.exe, 1.00.0000.0001 (English), 10/04/2013 09:34:24, 332800 bytes
    Driver: C:\Windows\system32\atisamu64.dll, 7.01.0000.0001 (English), 05/09/2013-00:27:40, 89088 bytes
    Driver: C:\Windows\system32\amdhcp64.dll, 1.00.0000.0001 (English), 05/09/2013-02:01:30, 157736 bytes
    Driver: C:\Windows\system32\amdave64.dll, 5.05.0005.0004 (English), 05/09/2013-00:28:00, 95744 bytes
    Driver: C:\Windows\SysWOW64\amdave32.dll, 5.05.0005.0004 (English), 05/09/2013-00:27:54, 90112 bytes
    Driver: C:\Windows\SysWOW64\atisamu32.dll, 7.01.0000.0001 (English), 05/09/2013-00:27:36, 80896 bytes
    Driver: C:\Windows\SysWOW64\amdhcp32.dll, 1.00.0000.0001 (English), 05/09/2013-02:01:30, 142304 bytes
    Driver: C:\Windows\system32\atiglpxx.dll, 8.14.0001.6347 (English), 05/09/2013-00:34:00, 69632 bytes
    Driver: C:\Windows\system32\aticfx64.dll, 8.17.0010.1242 (English), 05/09/2013-02:01:18, 1287152 bytes
    Driver: C:\Windows\SysWOW64\aticfx32.dll, 8.17.0010.1242 (English), 05/09/2013-02:01:16, 1071328 bytes
    Driver: C:\Windows\system32\OpenCL.dll, 1.02.0011.0000 (English), 05/09/2013-01:41:02, 63488 bytes
    Driver: C:\Windows\system32\amdocl64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:04, 28445184 bytes
    Driver: C:\Windows\system32\amdocl_as64.exe, 05/09/2013 01:45:44, 1187342 bytes
    Driver: C:\Windows\system32\amdocl_ld64.exe, 05/09/2013 01:45:44, 1061902 bytes
    Driver: C:\Windows\system32\OpenVideo64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:40, 98816 bytes
    Driver: C:\Windows\system32\OVDecode64.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:26, 86528 bytes
    Driver: C:\Windows\system32\clinfo.exe, 05/09/2013 01:45:56, 229888 bytes
    Driver: C:\Windows\SysWOW64\OpenCL.dll, 1.02.0011.0000 (English), 05/09/2013-01:40:58, 57344 bytes
    Driver: C:\Windows\SysWOW64\amdocl.dll, 10.00.1307.0001 (English), 05/09/2013-01:42:54, 23989248 bytes
    Driver: C:\Windows\SysWOW64\amdocl_as32.exe, 05/09/2013 01:45:42, 995342 bytes
    Driver: C:\Windows\SysWOW64\amdocl_ld32.exe, 05/09/2013 01:45:42, 798734 bytes
    Driver: C:\Windows\SysWOW64\OpenVideo.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:32, 83456 bytes
    Driver: C:\Windows\SysWOW64\OVDecode.dll, 10.00.1307.0001 (English), 05/09/2013-01:45:22, 73216 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.ssz, 8.14.0001.6019 (English), 21/05/2013-17:38:38, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.sez, 8.14.0001.6019 (English), 21/05/2013-17:38:50, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.sbz, 8.14.0001.6019 (English), 21/05/2013-17:38:50, 36096 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.isz, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.iez, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.ibz, 17/05/2013 13:55:44, 1980 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.csz, 03/06/2013 23:16:38, 8095 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.cez, 03/06/2013 23:17:08, 9851 bytes
    Driver: C:\AMD\amdkmpfd\amdkmpfd.cbz, 03/06/2013 23:17:08, 9851 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDh264Enc32.dll, 1.00.0000.0001 (English), 05/09/2013-01:26:26, 235520 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDh264Enc64.dll, 1.00.0000.0001 (English), 05/09/2013-01:26:50, 278016 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDhwDecoder_32.dll, 1.00.0000.0001 (English), 05/09/2013-01:32:40, 195584 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDhwDecoder_64.dll, 1.00.0000.0001 (English), 05/09/2013-01:33:16, 232448 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTDecoder_32.dll, 1.00.15369.0331 (English), 05/09/2013-01:31:54, 98304 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTDecoder_64.dll, 1.00.15369.0331 (English), 05/09/2013-01:32:06, 121344 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTVideoDecoder_32.dll, 05/09/2013-02:00:50, 109832 bytes
    Pilot: C:\Program Files\Common Files Technologies\Multimedia\AMDMFTVideoDecoder_64.dll, 05/09/2013 03:00:50, 132528 bytes
    Driver: C:\Windows\system32\coinst_13.20.11.dll, 1.00.0005.0009 (English), 05/09/2013-01:38:20, 129536 bytes

    Name: PCI standard ISA bridge
    Device ID: PCI\VEN_1002 & DEV_439D & SUBSYS_439D1002 & REV_40\3 & 2B8E0B4B & 0 & A3
    Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.01.7600.16385 (in English), 2009-07-13 19:48:27, 15424 bytes

    Name: Standard enhanced PCI to USB Host Controller
    Device ID: PCI\VEN_1002 & DEV_4396 & SUBSYS_50041458 & REV_00\3 & 2B8E0B4B & 0 & 92
    Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 53248 bytes
    Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:11, 325120 bytes
    Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.18328 (in English), 26/11/2013-19:41:37, 343040 bytes

    ------------------
    DirectShow filters
    ------------------

    DirectShow filters:
    WMAudio Decoder DMO, 0 x 00800800, 1, 1, WMADMOD. DLL, 6.01.7601.17514
    WMAPro over S/PDIF DMO, 0 x 00600800, 1, 1, WMADMOD. DLL, 6.01.7601.17514
    WMSpeech Decoder DMO, 0 x 00600800, 1, 1, WMSPDMOD. DLL, 6.01.7601.17514
    MP3 DMO, 0 x 00600800, 1, 1, mp3dmod.dll, 6.01.7600.16385 decoder
    Mpeg4s decoder DMO, 0 x 00800001, 1, 1, mp4sdecd.dll, 6.01.7600.16385
    Decoder WMV DMO, 0 x 00600800, 1 screen, 1, wmvsdecd.dll, 6.01.7601.17514
    Decoder DMO WMVideo, 0 x 00800001, 1, 1, wmvdecod.dll, 6.01.7601.18221
    Mpeg43 decoder DMO, 0 x 00800001, 1, 1, mp43decd.dll, 6.01.7600.16385
    MPEG4 Decoder DMO, 0 x 00800001, 1, 1, mpg4decd.dll, 6.01.7600.16385
    DV Muxer, 0x00400000, 0, 0, qdv.dll, 6.06.7601.17514
    Converter, 0 x 00400001, 1, 1, quartz.dll, 6.06.7601.17713 color space
    Reader, 0x00400000, 0, 0, qasf.dll, WM ASF 12.00.7601.17514
    Filter, 0 x 00200000, 0, 1, wmpsrcwp.dll, 12.00.7601.17514 screenshot
    AVI Splitter, 0 x 00600000, 1, 1, quartz.dll, 6.06.7601.17713
    VGA 16 color Ditherer, 0 x 00400000, 1, 1, quartz.dll, 6.06.7601.17713
    SBE2MediaTypeProfile, 0 x 00200000, 0, 0, SBE.dll, 6.06.7601.17528
    Microsoft DTV - DVD video Decoder, 0x005fffff, 2, 4, msmpeg2vdec.dll, 12.00.9200.16426
    AC3 parser Filter, 0 x 00600000, 1, 1, mpg2splt.ax, 6.06.7601.17528
    StreamBufferSink, 0 x 00200000, 0, 0, sbe.dll, 6.06.7601.17528
    Microsoft TV legends Decoder, 0 x 00200001, 1, 0, MSTVCapn.dll, 6.01.7601.17715
    MJPEG Decompressor, 0 x 00600000, 1, 1, quartz.dll, 6.06.7601.17713
    CBVA DMO wrapper filter, 0 x 00200000, 1, 1, cbva.dll, 6.01.7601.17514
    MPEG-I Stream Splitter, 0 x 00600000, 1, 2, quartz.dll, 6.06.7601.17713
    Parser, 0 x 00400000, 1, 1, quartz.dll, 6.06.7601.17713 SAMI (CC)
    The IST Codec, 0 x 00600000, 1, 4, VBICodec.ax, 6.06.7601.17514
    Writer, 00200000 x 0, 1, 0, atimpenc64.dll, 13.20.0000.30905 file MPEG ATI
    AMD Decoder, 0 x 00200000, 1, 2, atimpenc64.dll, 13.20.0000.30905 video
    MPEG-2 Splitter, 0x005fffff, 1, 0, mpg2splt.ax, 6.06.7601.17528
    Filter, 0 x 00200000, 2, 5, cca.dll, 6.06.7601.17514 analysis of closed captioning
    SBE2FileScan, 0 x 00200000, 0, 0, SBE.dll, 6.06.7601.17528
    Microsoft MPEG-2 video encoding, 0 x 00200000, 1, 1, msmpeg2enc.dll, 6.01.7601.17514
    Renderer, 0 x 00800001, 1, 0, quartz.dll, 6.06.7601.17713 Script command internal
    MPEG Audio Decoder, 0 x 03680001, 1, 1, quartz.dll, 6.06.7601.17713
    DV Splitter, 0 x 00600000, 1, 2, qdv.dll, 6.06.7601.17514
    Video Mixing Renderer 9 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713
    Microsoft MPEG - 2 encode, 0 x 00200000, 2, 1, msmpeg2enc.dll, 6.01.7601.17514
    ATI MPEG Audio Encoder, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905
    Decoder, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905 AMD MJPEG
    ACM Wrapper, 0 x 00600000, 1, 1, quartz.dll, 6.06.7601.17713
    Video Renderer, 0 x 00800001, 1, 0, quartz.dll, 6.06.7601.17713
    Video stream MPEG - 2 Analyzer, 0 x 00200000, 0, 0, sbe.dll, 6.06.7601.17528
    Line 21 decoder, 0 00600000, 1, 1, x
    Port video Manager, 0 x 00600000, 2, 1, quartz.dll, 6.06.7601.17713
    Video Renderer, 0x00400000, 1, 0, quartz.dll, 6.06.7601.17713
    AMD Encoder, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905 video
    Multiplex, 0 x 00200000, 2, 1, atimpenc64.dll, 13.20.0000.30905 ATI MPEG
    Decoder, 0 x 00200000 VPS, 0, 0, WSTPager.ax, 6.06.7601.17514
    Writer, 0x00400000, 0, 0, qasf.dll, WM ASF 12.00.7601.17514
    Allocator, 0 x 00600000, 1, 1, vbisurf.ax, 6.01.7601.17514 Surface of VBI
    File writer, 00200000 x 0, 1, 0, qcap.dll, 6.06.7601.17514
    iTV Sink, 0 x 00600000, 1, 0, itvdata.dll, 6.06.7601.17514 data
    iTV to Capture data filter 0 x 00600000, 1, 1, itvdata.dll, 6.06.7601.17514
    AMD Scaler video Filter, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905
    DVD Navigator, 0 x 00200000, 0, 3, qdvd.dll, 6.06.7601.17835
    Microsoft TV subtitles Decoder, 0 x 00200001, 1, 0, MSTVCapn.dll, 6.01.7601.17715
    Mixer2, 0 x 00200000, 1, 1, overlay
    RDP DShow Redirection Filter, 0xffffffff, 1, 0, DShowRdpFilter.dll,
    Microsoft MPEG-2 Audio Encoder, 0 x 00200000, 1, 1, msmpeg2enc.dll, 6.01.7601.17514
    Pager, 0 x 00200000, 1, 1, WSTPager.ax, 6.06.7601.17514 WST
    MPEG2 demux, 0 x 00600000, 1, 1, mpg2splt.ax, 6.06.7601.17528
    Decoder, 0 x 00800000, 1, 1, qdv.dll, 6.06.7601.17514 DV video
    SampleGrabber, 0 x 00200000, 1, 1, qedit.dll, 6.06.7601.18175
    Renderer, 00200000 x 0, 1, 0, qedit.dll, 6.06.7601.18175 null
    Tables, 0x005fffff, 1, 0, mpeg2data.ax, 6.06.7601.17514 and MPEG - 2 Sections
    Microsoft AC3 Encoder, 0 x 00200000, 1, 1, msac3enc.dll, 6.01.7601.17514
    StreamBufferSource, 0 x 00200000, 0, 0, sbe.dll, 6.06.7601.17528
    Smart Tee, 0 x 00200000, 1, 2, qcap.dll, 6.06.7601.17514
    Overlay mixer, 0 x 00200000, 0, 0,
    AVI Decompressor, 0 x 00600000, 1, 1, quartz.dll, 6.06.7601.17713
    NetBridge, 00200000 x 0, 2, 0, netbridge.dll, 6.01.7601.17514
    Source, 0 x 00400000, 0, 2, quartz.dll, 6.06.7601.17713 AVI/WAV file
    Parser, 0 x 00400000, 1, 1, quartz.dll, 6.06.7601.17713 wave
    Parser, 0 x 00400000, 1, 1, quartz.dll, 6.06.7601.17713 noon
    Multi-fichier Parser, 0 x 00400000, 1, 1, quartz.dll, 6.06.7601.17713
    File stream renderer, 0x00400000, 1, 1, quartz.dll, 6.06.7601.17713
    Filter, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905 video rotation AMD
    Microsoft DTV - DVD Audio Decoder, 0x005fffff, 1, 1, msmpeg2adec.dll, 6.01.7140.0000
    StreamBufferSink2, 0 x 00200000, 0, 0, sbe.dll, 6.06.7601.17528
    AVI Mux, 00200000 x 0, 1, 0, qcap.dll, 6.06.7601.17514
    Line 21 decoder 2, 0 x 00600002, 1, 1, quartz.dll, 6.06.7601.17713
    File Source (Async.), 0 x 00400000, 0, 1, quartz.dll, 6.06.7601.17713
    File Source (URL), 0 x 00400000, 0, 1, quartz.dll, 6.06.7601.17713
    Media Center Extender encryption Filter, 0 x 00200000, 2, 2, Mcx2Filter.dll, 6.01.7601.17514
    Dest, 0 x 00200000, 0, 0, WavDest.dll AudioRecorder WAV,.
    Wave WavDest.dll AudioRecorder form, 0 x 00200000, 0, 0,.,
    SoundRecorder Null Renderer, 0 x 00200000, 0, 0, WavDest.dll,
    Infinite pin Tee Filter, 0 x 00200000, 1, 1, qcap.dll, 6.06.7601.17514
    Renderer, 00200000 x 0, 1, 0, evr.dll, 6.01.7601.17514 improved video
    BDA MPEG2 Transport Information Filter, 0 x 00200000, 2, 0, psisrndr.ax, 6.06.7601.17669
    Decoder, 0 x 40000001, 1, 1, quartz.dll, 6.06.7601.17713 MPEG video

    WDM Streaming Tee/Splitter devices:
    Converter, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514 tee/sink - to the-wells

    Video compressors:
    WMVideo8 encoder DMO, 0 x 00600800, 1, 1, wmvxencd.dll, 6.01.7600.16385
    WMVideo9 encoder DMO, 0 x 00600800, 1, 1, wmvencod.dll, 6.01.7600.16385
    Encoder 9 MSScreen DMO, 0 x 00600800, 1, 1, wmvsencd.dll, 6.01.7600.16385
    Encode, 0 x 00200000, 0, 0, qdv.dll, 6.06.7601.17514 DV video
    MJPEG Compressor, 0 x 00200000, 0, 0, quartz.dll, 6.06.7601.17713

    Audio compressors:
    WM Encoder DMO speech, 0 00600800, 1, 1, x WMSPDMOE. DLL, 6.01.7600.16385
    WMAudio encoder DMO, 0 x 00600800, 1, 1, WMADMOE. DLL, 6.01.7600.16385
    ATI MPEG Audio Encoder, 0 x 00200000, 1, 1, atimpenc64.dll, 13.20.0000.30905
    IMA ADPCM, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    PCM, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    Microsoft ADPCM, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    GSM 6.10, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    CCITT A - Law, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    CCITT u - Law, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713
    MPEG Layer-3, 0 x 00200000, 1, 1, quartz.dll, 6.06.7601.17713

    PBDA CP filters:
    PBDA DTFilter, 0 x 00600000, 1, 1, CPFilters.dll, 6.06.7601.17528
    ETFilter, 0 x 00200000 PBDA, 0, 0, CPFilters.dll, 6.06.7601.17528
    PTFilter, 0 x 00200000 PBDA, 0, 0, CPFilters.dll, 6.06.7601.17528

    Midi converters:
    Default MidiOut Device, 0 x 00800000, 1, 0, quartz.dll, 6.06.7601.17713
    Synth, 00200000 x 0, 1, 0, quartz.dll, 6.06.7601.17713 Microsoft GS Wavetable

    WDM Streaming Capture devices:
    Realtek HD Audio Line input, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514
    Realtek HD Audio Mic input, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514
    Realtek HD Audio stereo input, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514

    WDM Streaming making devices:
    Realtek HD Audio output, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514
    Realtek HDA SPDIF optical Out, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514
    Realtek HDA SPDIF Out, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514

    BDA network providers:
    Provider, 0 x 00200000, 0, 1, MSDvbNP.ax, 6.06.7601.17514 Microsoft ATSC network
    DVBC Microsoft Network Provider, 0 x 00200000, 0, 1, MSDvbNP.ax, 6.06.7601.17514
    Provider, 0 x 00200000, 0, 1, MSDvbNP.ax, network 6.06.7601.17514 Microsoft DVBS
    Provider, 0 x 00200000, 0, 1, MSDvbNP.ax, 6.06.7601.17514 network Microsoft t
    Microsoft Network Provider, 0 x 00200000, 0, 1, MSNP.ax, 6.06.7601.17514

    Multiple instances Codecs VBI Capable:
    The IST Codec, 0 x 00600000, 1, 4, VBICodec.ax, 6.06.7601.17514

    BDA Transport Information converters:
    BDA MPEG2 Transport Information Filter 0 x 00600000, 2, 0, psisrndr.ax, 6.06.7601.17669
    Tables, 0 x 00600000, 1, 0, mpeg2data.ax, 6.06.7601.17514 and MPEG - 2 Sections

    CP/CA BDA filters:
    Decrypt/Tag,0x00600000,1,1,EncDec.dll,6.06.7601.17708
    Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.7601.17708
    PTFilter, 0 x 00200000, 0, 0, EncDec.dll, 6.06.7601.17708
    XDS Codec, 0 x 00200000, 0, 0, EncDec.dll, 6.06.7601.17708

    WDM Streaming transformations of the Communication:
    Converter, 0 x 00200000, 1, 1, ksproxy.ax, 6.01.7601.17514 tee/sink - to the-wells

    Audio converters:
    Speakers (Realtek High Definiti, 00200000 x 0, 1, 0, quartz.dll, 6.06.7601.17713)
    DirectSound Device, 0 x 00800000, 1, 0, quartz.dll, default 6.06.7601.17713
    Default WaveOut Device, 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713
    DirectSound: Realtek Digital Output (Realtek High definition Audio), 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713
    DirectSound: Realtek Digital Output (Optical) (Realtek High definition Audio), 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713
    DirectSound: Speakers (Realtek High definition Audio), 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713
    Realtek Digital Output (Realtek, 00200000 x 0, 1, 0, quartz.dll, 6.06.7601.17713)
    Realtek Digital Output (optical), 0 x 00200000, 1, 0, quartz.dll, 6.06.7601.17713

    ---------------
    EVR power information
    ---------------
    Current value: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (quality)
    Quality indicators: 2576
    Activated:
    Limitation of the force
    That allow half deinterlace
    Allow the scaling
    Decode power usage: 100
    Balanced flags: 1424
    Activated:
    Limitation of the force
    Allow batch processing
    Force half deinterlace
    Force the scaling
    Decode power usage: 50
    PowerFlags: 1424
    Activated:
    Limitation of the force
    Allow batch processing
    Force half deinterlace
    Force the scaling
    Decode power usage: 0

    Hello

    The attached file of the DMP is to bug checking SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) .

    This indicates that a system thread threw an exception who did not catch the error handler.

    Bugcheck 1000007E, {ffffffffc0000005, fffff88013dd3db1, fffff880033693d8, fffff88003368c30}

    The verification of bug 1 parameter is 0xc0000005 indicating an access violation has occurred. Let's look closer the exception record address:

    6: kd > .exr 0xfffff880033693d8
    ExceptionAddress: fffff88013dd3db1 (EtronXHCI+ 0x0000000000009db1)
    ExceptionCode: c0000005 (access violation)

    It was caused by EtronXHCI.sys which is the turd USB 3.0 Extensible Host Controller Driver.

    We can also see that she called twice in the stack:

    6: kd > kv
    Child-SP RetAddr: Args to child: call Site
    "fffff880 ' 03369610 fffffa80' 087 b 0000: 00000000 ' 00000002 '08510 a 60 fffffa80' fffffa80 08510bb0 fffffa80 ' 08510bb0: EtronXHCI+ 0x9db1
    fffff880'03369618 00000000'00000002: fffffa80 ' 08510a 60 fffffa80 '08510bb0 fffffa80' 08510bb0 fffffa80 ' 08510e78: 0xfffffa80'087 b 0000
    fffff880 ' 03369620 fffffa80' 08510 a 60: fffffa80 ' 08510bb0 fffffa80 '08510bb0 fffffa80' 08510e78 fffffa80 ' 08510 a 60: 0 x 2
    fffff880 ' 03369628 fffffa80' 08510bb0: fffffa80 ' 08510bb0 fffffa80 '08510e78 fffffa80' 08510 a 60 fffff880 ' 13dcbdb6: 0xfffffa80'08510 has 60
    fffff880 ' 03369630 fffffa80' 08510bb0: fffffa80 ' 08510e78 fffffa80 '08510-60 fffff880' 13dcbdb6 fffffa80 ' 00001b6f: 0xfffffa80'08510bb0
    fffff880 ' 03369638 fffffa80' 08510e78: fffffa80'08510 has 60 fffff880 '13dcbdb6 fffffa80' 00001b6f 00000000'00007023: 0xfffffa80'08510bb0
    fffff880 ' 03369640 fffffa80' 08510 a 60: fffff880 '13dcbdb6 fffffa80' 00001b6f 00000000'00007023 00000000'0 c 033001: 0xfffffa80'08510e78
    fffff880 ' 03369648 fffff880' 13dcbdb6: fffffa80'00001b6f 00000000'00007023 00000000'0 c 033001 00000000 00000000': 0xfffffa80'08510 has 60
    fffff880 ' 03369650 fffffa80' 00001b6f: 00000000'00007023 00000000'0 c 033001 00000000 00000000' fffff880'030fb180: EtronXHCI+ 0x1db6
    "fffff880'03369658 00000000'00007023: 00000000 ' 0 c 033001 00000000 00000000' fffff880 ' 030fb180 00000000' 00000000: 0xfffffa80'00001b6f
    "fffff880'03369660 00000000' 033001 0 c: 00000000 ' 00000000 fffff880 ' 030fb180 00000000'00000000 00000000'00000000: 0 x 7023
    fffff880'03369668 00000000 00000000': fffff880'030fb180 00000000'00000000 00000000'00000000 00000000'00000000: 0xc033001

    -----------------

    If we run a lmvm on your:

    6: kd > lmvm EtronXHCI
    start end module name
    fffff880 '13dca000 fffff880' 13ddd500 EtronXHCI T (no symbol)
    Loaded symbol image file: EtronXHCI.sys
    Image path: \SystemRoot\System32\Drivers\EtronXHCI.sys
    Image name: EtronXHCI.sys
        Timestamp: My Jul 25 17:30:56 2011

    ^^ Dated to ~ 2011, and later according to the Gigabyte website is 09/01/2014. Update ASAP - http://www.gigabyte.us/products/product-page.aspx?pid=3907#dl

    Kind regards

    Patrick

Maybe you are looking for