Random BSOD - critical process on my vaio flip error

Hi all!

I got my flip (model: SVF13N25CDB) for about 6 months now and about 1 month ago I started having BSOD at random.  They either stat that it is because of 'mistake of critical process' or 'core data entry error ".  They may not the case for days and then suddenly happen 5 times in one day.

I did a restore of Windows and that you always get this question.  Thinking maybe it was a hardware problem, I made a diagnosis of harware vaio but all inspected.  Theses errors are not all the minidump files.  This could be the cause?

Zet, thank you for this clarification. I think it's a good way to isolate, but I suggest you try to reformat external Windows by following the steps on this link unless the rescue of files since you have already wiped out the files. I hope this helps. ~ Yuri

Tags: Sony Computers

Similar Questions

  • How to fix the BSOD: critics of the process died?

    Hello

    Recently, I've restored my Acer Aspire 771 G back to factory settings, as I had a lot of problems after that I upgraded to windows 8.1. Now my computer works fine, except for a problem... I frequently get the BSOD: critics of the process is dead. It occurs usually when I try to run a certain game on Steam (it only happens for a game), but also happened on other occasions.

    I tried almost everything to solve the problem: reinstall the operating system, update drivers, virus/malware research and clean the registry. None of them have solved the problem. I then ran the Burn-in-test; my computer has adopted all aspects, except the CPU temperature test. It is likely that the BSOD if caused by overheating of the processor? And how can I stop this BSOD occurring?

    My computer is as follows: Acer Aspire V3 771 G: intel core i7, NVIDIA Geforce GT 640 M, 16 GB RAM, windows 8 and I have 2 hardrives: a 120G SSD as well as a 1 TB of HARD drive. On another note, I only had this computer for about 8 months.

    CG

    These two were always related to a part of Quick heal that remains installed (bdssvc.exe) I would like to remove it completely (you may need to contact them for more information)

  • 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

  • Satellite U940 - Random BSOD after replacing HARD drive

    Good day ladies and gentlemen!

    I was wondering if I can win some lights here - as I google myself in a bunch of flange on the issue, I have!

    I am a famous computer technician (modest too) and more recently, a client of mine introduced me to a ultrabook Satellite U940 - lovingly with the SSD / HDD Raid 0 configuration running our beloved Windows 8.

    All things according to their entire course - Hitachi hard drive failed (as google tells me is to be expected).

    So, I replace the hard drive by a great little number Western Digital, cloned from Hitachi, sector by sector, and after a significant cajoling with bcdedit and bootrec amount, I could so he could begin our good liked Windows 8.

    However, since then, I have random BSOD, cold boots failed and all sorts of errors.

    I ran all the regular patches - SFC/scannow, chkdsk/r, Windows 8 repair facilities, etc., but it is still volatile jolly.

    Things seem not to be as they were with this Satellite little ol '-before any repair, the peripheral device manager showed two "RAID 0' in the category of hard drives, and since then it shows the individual SSD and the WD HARD drive."

    I've updated the driver for the Intel Rapid Storage at latest on the Toshiba site, but nothing helps - alas!
    The weird part is that if I do a reboot on this little beauty, she starts without any problems, but a start cold after a power off is a completely different question - dummy - spit crashing, dumping, in general!

    If there is a troubleshooting there champion who can destroy my help in this situation, I'd be very impressed and never have if they could provide assistance in this regard.

    Unfortunately Microsoft - are we are all end by using these products of ever-so-pretty Appl?

    Hello

    I read in some discussions here in this forum only after replacing the disk SSD or HARD drive, the RAID configuration is lost and must be rebuilt on a device Windows 8.

    But this can be done very easily, and this can be corrected by an authorized Toshiba because this procedure requires special tools and utilities.

    Unfortunately, it seems to me that you will need to contact the ASP in your country to get this problem resolved :(

  • a few keys on the keyboard does not not on my Sony VAIO flip SVF15N17CXB 15A

    Hello people,

    I have the following problem. Around a week ago my keyboard started acting strange. namely, the letter 'I' and 'E' started does not have to work. However, after a few typing continious finally typed the letters. then only the restrat might help. After a few days, it completely stopped working and a few other letters does not work as well now. These are: 'Q' & 'E', 't' & 'I' & 'G '. I'm typing this now with touchscreen keyboard, (fortunetely, it works perfectly).

    to make sure that this software is not related, attempted to use the keys in safe mode of Windows, BIOS, connected a USB OS but still no use, they do not work. even activated the sound tapped the keyboard, but the keys do not all sound.

    I tried to unplug the LED cable described as https://community.sony.com/t5/VAIO-Hardware-Networking/How-to-replace-Vaio-Flip-15-keyboard/td-p/507..., but didn't help either.

    The only reason that comes to my mind could cause, it's playing video games before that happens the keyboard events. I think that overheating caused it, is it still possible that warming could cause some embarrassment on the keyboard keys?

    Coulf you please advice any other thing that might fix my problem before I'll order a new keyboard on eBay?

    I'm on m holidays and this completely spoiled my mood. Please help, community of Sony.

    Ordered keyboard, succeeded him myself, using the replaced keyboard now to type this message.

    All good, all good.

    Closed.

  • Random BSOD - Toshiba Qosmio X 500 13R (Windows 7 Home Premium x 64) have min

    I had some problems with random BSOD on my laptop.
    The laptop itself is relatively new, bought in March of this year, very good model but refently that I started to have problems.

    One day I closed the laptop and reflections he entered mode 'sleep' but a few hours later, when I opened a BSOD looked at me in the face, the processor part was hot enough so I restarted immediately to lower the temperature, but I remember the BSOD had something "Kernel Power" written on it.

    It happened 3 - 4 times since then, the third time it happened that I enabled the logging minidump so now I also the log since the last time it happened, can someone take a look and tell me what is happening and how to fix it?

    I still have a warranty on this baby so I can get it fixed for free if it's a hardware problem, I still have some important work to do this week (already almost lost a crucial project file on it) so I want to try to fix it myself for now, until I get this project done.

    Thank you!!!

    LAPTOP MODEL:
    Toshiba Qosmio X 500 13R

    Data sheet:
    QOSMIO X 500 - 13R - RED
    Processor Intel® Core i7-740QM 1.73 GHz
    Windows 7 Home Premium 64-bit
    18.4 "Toshiba TruBrite Full HD 1 920 x 1080
    1000 GB hard drive (500 GB + 500 GB [7200 RPM])
    8 GB RAM (1 066 MHz) DDR3, max 8 GB
    NVIDIA® GeForce® GTS 460M (1.50 GB)
    LAN wireless b/g/N
    TV tuner
    Disc Blu - ray rewritable
    Camera / HD Webcam with microphone integrated

    Memory minidump file:
    http://www.mediafire.com/?94akhevoscc8197

    > I still have a warranty on this baby so I can get it fixed for free if it's a hardware problem, I still have some important work to do this week (already almost lost a crucial project file on it) so I want to try to fix it myself for now, until I get this project done.

    The BSOD can be caused by a hardware problem software.
    You can check if the new OS install would solve this if this software issue then a new operating system installation is the good workaround. Before you start an OS install, back up data ;)

    But of course the question could be linked to the material; for example the high temperature.
    You said that you have noticed a higher temperature everything to happen.
    So maybe the memory modules are affected by a higher temperature, and this leads to BSOD. Often blocked fans are reason for this. Check to see if dust and debris must be removed you can remove the dust using a jet of compressed air.

    But if this is not enough, I'd recommend checking the material under conditions of warranty

  • 3270nr HP Envy, random BSOD

    I bought it a few months ago the beginning of the year, it worked great, was able to leave it on for a few days with no problems at all, but this week he started getting random BSOD, I did a test of stress with the CPU, was 100% usage for 20 minutes or so, do not go beyond 80 degrees (Celsius) and has not either the BSOD at first I thought it was steam associated, but this morning I left it on just to charge my phone with nothing open and he got a BSOD I think, because it shows the same image sometimes watch after BSOD, saying: there is no OS installed, I did not format after purchase, or made changes on the hardware all I use is a USB mouse. The attachment is the image which shows sometimes after the BSOD, but other times he just asking if I want to start Windows normally, with the network, or safe mode. It works very well after that I have press and hold the power button to force it to stop and restart. At the hope of solving this problem here before trying to exchange it for another or something.

    Hello

    If the hard drive test failed there is a hard drive problem and must be replaced. If your laptop is still under warranty, then you can call the HP technical support to get it replaced.

    HP Notebook PC - test a hard drive by using the Built in Self Test c00439024

  • New stream 7 randomly BSOD

    I bought a jet 7 from the Microsoft Store and had a couple of days.  Shortly after, I noticed that I would get random BSOD.  Sometimes, after a BSOD, it would BSOD when starting up and automatic startup repair will start and run aground.  Then he would start normally.  I tried to refresh and reset.  I am still getting random BSOD.  What could be wrong?

    Yes the BSOD is very rare in windows 8 and is usually the cause of two things, due to lack of equipment and the driver incorrect installed.

    You will need to provide us with the information on the blue screen, but for us to answer further, HOWEVER... since I doubt that you have installed the drivers of thugs, I suspect a piece of hardware has not seen anything to the Tablet isn't replaceable, you should make arrangements for a return to the Bank of microsoft to refun or replacement.

  • Random BSoD occurrences, can not read the message because no option to put an end to restart in the event of system failure.

    My girlfriend has a HP dv4-1465dx experiencing hardware problems, the laptop will be blue screen randomly and then restart 1-3 seconds later. When you restart the laptop reads, "No boot device - insert boot disk and press any key." If the laptop is turned off and turn it on again, it works fine, until the next BSoD. The first time that this error the hard drive was seized up, unable to enter a bank hard disk enclosure repair attempts that forced me to buy a new one.

    I tried the bios of an option to disable the restart in the event of system failure so I could read the error message, but it only gave me discover that HP has less useful bios in the world and that no such possibility existed; Yes I have updated the bios. Start/hardware error logs contained no data also, what so ever.

    The hard drive is fine, I ran it in my office for several days. a BSoD happens within his laptop several times a day.

    I don't know what to do at this point is that I have nothing to work outside of, I hope someone has a useful idea. The laptop is no longer under warranty, but this is ridiculous, how fast this thing is falling apart (literally... screws are only randomly drop the case).

    Yes I really don't think that this is the case. As mentioned above is not my laptop so I'll probably wait until he decides to restart not at all before eventually taking an iron to be welded to it. Thanks for all the information, assume that nothing can be done at this stage.

  • Failure of critical process after the December 13 update

    After that my Windows XP Media Center computer has installed the automatic updates of Microsoft this past Tuesday, December 13, 2011, I started to receive the critical process failure message Code #3.  I was able to do a system restore before the update but it automatically reinstalled the update and now I am not able to go back to one of the stored point of update and I can't access the registered and put programs in place of future records in Media Center

    I had initially followed the steps but couldn't reinstall Rollup 2 as it kept not install. I seemed to be in Hotfix KB891593.   I was able to locate a thread on some other Windows message board which has led me to open the MCSetup log to see what was not. The log seems to indicate that the inability to install had something to do with Windows Media Player 10. I use Windows Media Player 11 but I found a fix for Windows Media Player 10 in the programs/updates to update installed in the Panel.  I uninstalled this patch and was then able to reinstall the Update Rollup 2, which fixed the problem of Media Center.  Thanks for the reply.

  • Random BSOD, all drivers, firmware and bios updates. Need help!

    Hello, before Thursday and the release of Windows 7 x 64 I was running XP pro x 64, I did a clean install of Win 7 Home premium x 64 and was faced with random BSOD every hour. I've updated all my drivers, bios, hardware, everything that I could think of, and he continued to perform. I gave up on Win7 x 64 thinking it was a driver problem, so now I'm back on XP pro x 64 and I have random BSOD frequently enough.

    This is a copy of the journal of the accident:
    Server
    UI LCID = 1033
    Flags = 1696080
    Brand = WINDOWS
    TitleName = Microsoft Windows
    DigPidRegPath = HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
    ErrorText = A log of this error was created.
    HeaderText = the system has recovered from a serious error.
    Stage2URL=/DW/bluetwo.asp? BCCode = & 00000000000000D = BCP1 8 & BCP2 = 000000000000000C & BCP3 = 0000000000000000 BCP4 = FFFFF8000104F54C & OSVer = 5_2_3790 & SP = 2_0 & product = 256_1
    DataFiles=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WER582b.dir00\Mini102709-01.dmp| C:\DOCUME~1\ADMINI~1\Locals~1\Temp\WER582b.dir00\sysdata. XML
    ErrorSubPath = blue
    DirectoryDelete=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WER582b.dir00
    I am running AMD Phenom II X 4 945 Deneb 3.0 ghz socket AM3 125W quad-core processor
    4 GB (2x2gb) g. skill 240 pin ddr3 1333 dual channel desktop memory sdram
    OCZ gamexstream 850w psu
    Samsung 320 g 7200 RPM sata 3.0 GB/s HD
    PNY nvidia geforce 9800gt
    Biostar TA790gx A3 + AM3 AMD 790GX HDMI ATX AMD mobo
    Any suggestions/ideas/opinions would be greatly appreciated!

    Lardacus,
    If you haven't tried items on this thread then get started with them.  XP troubleshooting

    So I recommend you to run Chkdsk/r

    And test your memory with the Memory Diagnostic.

    Given that this error occurred with two versions of Windows, I would check the material to ensure that it is not a problem with anything. Mike - Engineer Support Microsoft Answers
    Visit our Microsoft answers feedback Forum and let us know what you think.

  • Random BSOD and I do not know why.__Unable to load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32

    I don't know why this is happening, but I'm getting random BSOD now and then. I tried to point out my system to see if it generates a BSOD, but multitasking 3d and photoshop programs and what's not stress, then when I least expect, BANG! BSOD.
    The last of them, that I had now was in the middle of the night with almost no programs running. The system had worked for some time (one or two days), but nothing was he pointing out at the same time.

    What I think happened was: our microwave shorted out and caused a fuse to blow. But it was on another grid in our House (I hope I make myself clear, because I'm not used to talk about stuff like this in English!) so it should not affect my computer. But at the same time my microwave said "Thank you for everything!" my computer would BSOD. The thing is that my modem, my switch, my router and my NAS is connected to the electric network and my short circuted of switch. And my computer is connected to the switch cable.
    This effect possible that excess tension (or something) has short circuted my switch and 'jumped' power to the switch and on the cable and sending there is a shock to my computer? Or am I just paranoid? Laughing out loud

    I know that the controllers are pushed to the limit of the memory and therefor tolerate very little when it comes to electricity. I ran MemTest4.00 14 passes but I came with nothing. But memtest that tests memory, not the controllers, right? I am watching a fried motherboard?

    I did a windb, but I don't understand what he says. Could someone please translate this for me and give me your opinion?
    In addition, when you run windb, it's tell me am I wrong symbols. -What this means, and where can I get the symbols he wants? And what symbols?

    Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
    Copyright (c) Microsoft Corporation. All rights reserved.

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

    Symbol search path is: * invalid *.
    ****************************************************************************
    * Loading of the symbol may be unreliable without a symbol search path.           *
    * Use .symfix to get the debugger to choose a symbol path.                   *
    * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.
    * using the _NT_SYMBOL_PATH environment variable.                 *
    * with the help of the there when you start the debugger argument. *.
    * using the .sympath and .sympath + *.
    *********************************************************************
    Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (4 procs) free x 64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Computer name:
    Kernel base = 0xfffff800 '02c4c000 PsLoadedModuleList = 0xfffff800' 02e10dd0
    The debugging session: 23:43:16.368 Thursday, April 29, 2010 (UTC + 02:00)
    System Uptime: 3 days 5:21:50.657
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.

    * using the _NT_SYMBOL_PATH environment variable.                 *
    * with the help of the there when you start the debugger argument. *.
    * using the .sympath and .sympath + *.

    *********************************************************************
    Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Loading the kernel symbols
    ...............................................................
    ................................................................
    ................................................
    Loading user symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck A, {fffffa7fffffffea, 2, 0, fffff80002c5a95c}

    The kernel symbols are FALSE. Correct symbols to do the analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    Probably caused by: ntoskrnl.exe (nt + e95c)

    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: fffffa7fffffffea, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002c5a95c, address memory

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

    The kernel symbols are FALSE. Correct symbols to do the analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Your debugger is not using the appropriate symbols *.
    ***                                                                   ***
    In order for this command works correctly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '! findthebuild' command to search for the generation of target information.
    If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80002c4c000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4b7d238f

    READ_ADDRESS: could not get nt! MmSpecialPoolStart
    Unable to get nt! MmSpecialPoolEnd
    Unable to get nt! MmPoolCodeStart
    Unable to get nt! MmPoolCodeEnd
    fffffa7fffffffea

    CURRENT_IRQL: 0

    FAULTING_IP:
    NT + e95c
    fffff800'02c5a95c?              ???

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0XA

    LAST_CONTROL_TRANSFER: from fffff80002ca626e to fffff80002ca64d0

    STACK_TEXT:
    fffffa60 '01bde688 fffff800' 02ca626e: 00000000' 0000000 a fffffa7f ' ffffffea 00000000'00000002 00000000'00000000: nt + 0x5a4d0
    fffffa60 '01bde690 00000000' 0000000-a: fffffa7f 'ffffffea 00000000'00000002 00000000'00000000 fffff800' 02c5a95c: nt + 0x5a26e
    fffffa60 '01bde698 fffffa7f' ffffffea: 00000000'00000002 00000000'00000000 fffff800 '02c5a95c fffffa60' 04dbf8b0: 0xa
    fffffa60 '01bde6a0 00000000' 00000002: 00000000 00000000' fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000' 00000000: 0xfffffa7f'ffffffea
    fffffa60'01bde6a8 00000000' 00000000: fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000'00000000 00000000'00000000: 0 x 2

    STACK_COMMAND: .bugcheck; Ko

    FOLLOWUP_IP:
    NT + e95c
    fffff800'02c5a95c?              ???

    SYMBOL_NAME: nt + e95c

    FOLLOWUP_NAME: MachineOwner

    Nom_image: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

    I'm grateful for any help I can get in that case.

    My system is: AMD 9950BE CPU, motherboard ASUS Crosshair II Formula, 4 x 2 giga OCZ 1066 mhz memory, Vista Ultimate 64 bit, ASUS 295GTX GPU

    Postal salvation,

    I think you're in luck. It chances are you are one of those rare cases where the BSOD may not be hardware related. In addition, it is actually pretty rare to have so many errors after a sfc... Wow. I think that alone has helped reduce the risk of an another BSOD and was good insurance against other problems.

    Do you have a chance to check the hard drive? Now, I would like to check the hard drive to see if there may be potential damage to the hard drive as well to help explain this number of errors (return to the material again).

    Here's how to new:

    http://Windows.Microsoft.com/en-us/Windows-Vista/check-your-hard-disk-for-errors

    I think that advice on the anti-virus scanning are also actually still relevant today. I have a scan of one of the two groups below as soon as you can and let us know the result if you can.

    virus/malware programs:

    Symantec:

    Works in Safe Mode and free:

    _ http://security.symantec.com/sscv6/WelcomePage.asp

    Trend Micro

    _ http://housecall.trendmicro.com/

    Ad-ware/spyware:

    Ad-aware

    http://www.lavasoftusa.com/

    Spybot Search and Destroy

    http://www.safer-networking.org/

    * It is an excellent versatile tool as it will both spyware and malware and has also a small footprint.

    See you soon,.

    Steve <> Microsoft Partner

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

  • Random BSOD after upgrade to Windows 7 for Win Vista

    Hello

    I am getting random BSOD, system crashes etc... After that I updated to windows vista.

    It is not a custom built PC, but I checked the inside of the box

    Plug-

    Intel Core2Duo

    4 GB of Ram

    1 TB HARD DRIVE

    NVIDIA Gt 140

    (Big one) memory dump

    http://1drv.Ms/1pIf5US

    OM

    All first please change your control panel of the system to small (lernel) DMP.  It will save you a ton of time when you transfer files DMP.  You can read how in this wiki

    This accident was related to the corruption of memory, please run the Driver Verifier to find the underlying cause.

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

    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.

    Since then, it is more likely to be a pilot run everything first.
    1-Driver Verifier (for full instructions, see our wiki here)

    If the auditor does not have the issue we move to it.

    2-Memtest. (You can learn more about running memtest here)


    If you cannot start after you have enabled the auditor reboot in safe mode
    In Vista & win 7 (F8)

    Co-written by JMH3143

    .

Maybe you are looking for

  • NB200 - upgrade the RAM and install Windows 7?

    Hello to you guys. I'm back and received the news for you. I got my new Toshiba NB200-10Z. I would like to ask you: What are your comments on the upgrade of RAM? The difference is notable? It worth the cost?What RAM memory slot I'm supposed to get? A

  • Update wireless WPA on satellite A110-276

    I have the laptop above that has built-in wireless 'WEP '. We again lapop work which has integrated wireless WPA. Can I upgrade my satellite WPA Wireless so that they can both work out of the box of wireless router?

  • Have a PHotosmart C4795 wireless capable; printing problems

    I have a Verizon 4 G hotspot for the Internet and was able to print for a while, but now can't do wireless wireless. No problem to do with usb to the printer.

  • HP C309g: Printing problems

    Help! I can't print from my MacBook Pro, one of my printers (HP C309g & D110) wireless. I have run the wireless network test and everything is good on the report, but on the computer, it shows that it is unable to communicate with the selected device

  • How to get on the application performance?

    Hi guys. I am looking at the performance of applications such as CPU, memory utilization etc. In other words, I want to know how the application gets the performance itself. For the code, what classes use? Thanks in advance.