Zenimax, are you getting our system generated crash reports?

Stash · August 2014

I was wondering if filling out the OS system generated crash report was worth the effort. Are you receiving our crash reports if they are not generated by the ZOS crash reporter? I am suffering from the PvP memory leak issue, and I am filling out and sending in crash reports whenever I am prompted to. Sometimes the crash reports are the Apple OS system generated crash reports, and sometimes its the ZOS error reporter. I know many of the PC client users are using the Windows crash reporter too. I would feel better about all the crashes if I knew that Zenimax was getting the crash reports I am sending in. A little reassurance here would go a long way.

Rhoric · August 2014

If it is a windows or apple crash report, those get sent to microsoft or apple. If it is the ZOS one it should be being sent to ZOS if that is how it works. I have never crashed so haven't seen the ZOS one.

Stash · August 2014

Rhoric wrote: »

If it is a windows or apple crash report, those get sent to microsoft or apple. If it is the ZOS one it should be being sent to ZOS if that is how it works. I have never crashed so haven't seen the ZOS one.

Do you play in PvP much? I never crash in PvE, but I crash every 30 minutes or so in PvP.

Rhoric · August 2014

I don't touch PvP. It doesn't interest me. Do you keep your launcher running in the background after you hit Play?

Stash · August 2014

Yeah I do. I have tried quitting the launcher while playing, but I haven't tried do so since the 3rd patch. I might try that again tomorrow. I have 8GB ram, so I don't think the launcher should be causing any memory trouble.

Rhoric · August 2014

I would try closing the launcher after hitting Play. Some people reported in the past that there was a leak in the launcher and that after closing it they didn't have anymore issues. I close it down myself as there is no need for it to run in the background.

Epona222 · August 2014

Definitely close the launcher once the game has launched! I usually do that whilst waiting for my character to load. (Zenimax, please introduce an option on the launcher to shut it down automatically once the game is running).

Even with the launcher closed though, I did experience a crash a couple of days ago (first one in ages), very high RAM usage after running for a while.

Seravi · August 2014

The launcher has a known memory leak so yeah close that after you are in game. There is a bad memory leak that has shown up after this months update. CS and I have had daily emails back and forth on it and they are aware of the issue and "hope" to have a fix by the next update, whenever that is. I know they do receive the in game crash reports generated by ESO as they have pulled those to verify some stuff I asked about.

c0rp · August 2014

Rhoric wrote: »

I would try closing the launcher after hitting Play. Some people reported in the past that there was a leak in the launcher and that after closing it they didn't have anymore issues. I close it down myself as there is no need for it to run in the background.

CLosing the launcher DOES NOT stop the cyrodiil crashes, I assure you of that.

Homm · August 2014

Cyrodill crashed are due to memory leak. Easy to prove - open task manager on 2nd screen and observe the ram. Crash is always around 3.75 GB ram used for me (started from ~1.5 and growing.. growing... growing... till bam).

Evergnar · August 2014

Homm wrote: »

Cyrodill crashed are due to memory leak. Easy to prove - open task manager on 2nd screen and observe the ram. Crash is always around 3.75 GB ram used for me (started from ~1.5 and growing.. growing... growing... till bam).

^This. Nothing we can do except wait for Zos to fix it.

Stash · August 2014

The mac client crashes due to a memory leak regardless of whether the launcher is open or not. I just reconfirmed this morning. I'm running Activity Monitor (shows cpu, network and memory usage) and I can watch the virtual memory field keep increasing until about 3.9GB or so and the client will crash. It only happens in cyrodil, not in PvE. I deleted the whole zenimax folder and I'm downloading a new installation to see if that helps at all.

I was hoping I'd get some notification if Zenimax was getting all the crash reports I was sending in.

zgrssd · August 2014

Zos get's the Zenimax error reports. They look like this:
http://img0.joyreactor.cc/pics/comment/The-Elder-Scrolls-фэндомы-TES-Online-Beta-test-946279.png

That one get's send to the devs.
If you see that one, Windows should not even be aware that ESO crashed (as the exception was caught and handeled by eso.exe itself as last act before ending itself gracefully).

Homm wrote: »

Cyrodill crashed are due to memory leak. Easy to prove - open task manager on 2nd screen and observe the ram. Crash is always around 3.75 GB ram used for me (started from ~1.5 and growing.. growing... growing... till bam).

Wich figure of memory? A lot of people look at the working set, wich is the least usefull figure of all. Even programmers often stumble over that.

Private bytes is the only thing that says anything of relevance:
http://www.itwriting.com/dotnetmem.php
But if it really happens around the same value it is propably a legitimate OOM/memory leak exception. And those always are damn hard to track down.

Paske · August 2014

Having more RAM does nothing.

I have 24 GB System RAM and Cyro crashes every 30 or so minutes.

This is the issue, ESO is a 32 bit game and can adress no more then 3,75 GB of RAM.
Once it fills this it crashes.

With memory leak in Cyro it doesn't take too long ( sadly )

So all of you with cca 8 GB of RAM, dont worry, its the same for rest of us.

Taleof2Cities · August 2014

Same here ... 8 GB of RAM but crashed three times in Cyrodiil yesterday. It appears ZOS is aware of it so it's just a waiting period at this point.

Ozriel · August 2014

and waiting and waiting and.......

xFusionx · August 2014

I hope they get these crash reports...I swear, ZOS has no idea how to push a patch without introducing new issues - It's called QA - ffs ZOS, you should try it sometime

Stash · August 2014

So I opened another ticket about the memory leak/instability in Cyrodil issue. I made a point of suggesting that they should make sure they are getting the crash reports generated by the Mac OS crash reporter. I find it funny that the ZOS crash reporter also crashes regularly.

Gillysan · August 2014

I'm not playing pvp lately, pve is still keeping me busy. Today is Saturday, 6 days after the big 133 patch of Monday, I have played quite a bit the last few days with no crashing. Suddenly today I'm crashing.

Crashed twice in a row, deleted the shader cache file in the documents folder and it looked like it was fixed.

Then I crashed three times in a row shortly after entering the game on different characters. So I'm guessing that deleting the shader cache file didn't help previously.

Running the repair tool for the second time but it's getting late, so I'll see how it goes tomorrow. I don't use the launcher except on path days, usually it's the shortcut I made for eso.exe.

Each time I got the ESO game crash window and filled it out. I couldn't see any info there that told me what may have gone wrong. Also, I don't see any log files that might give me a clue, only that the game terminated suddenly.

Dxdiag

System Information

Time of this report: 8/6/2014, 14:51:43
Machine name: IG7-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: MSI
System Model: MS-7522
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 CPUs), ~2.7GHz
Memory: 6144MB RAM
Available OS Memory: 6134MB RAM
Page File: 6708MB used, 5558MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

DxDiag Notes

Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.

DirectX Debug Levels

Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

Display Devices

Card name: AMD Radeon HD 5800 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: ATI display adapter (0x6898)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_6898&SUBSYS_032E1043&REV_00
Display Memory: 3826 MB
Dedicated Memory: 1015 MB
Shared Memory: 2811 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: SyncMaster
Monitor Id: SAM06E9
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
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
Driver File Version: 8.17.0010.1299 (English)
Driver Version: 14.200.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/22/2014 19:28:04, 1328352 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-2BD8-11CF-E076-2423BEC2C535}
Vendor ID: 0x1002
Device ID: 0x6898
SubSys ID: 0x032E1043
Revision ID: 0x0000
Driver Strong Name: oem70.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:14.200.0.0:pci\ven_1002&dev_6898
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=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: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Card name: AMD Radeon HD 5800 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: ATI display adapter (0x6898)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_6898&SUBSYS_032E1043&REV_00
Display Memory: 3826 MB
Dedicated Memory: 1015 MB
Shared Memory: 2811 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: BenQ G2420HDBL (Analog)
Monitor Model: G2420HDBL
Monitor Id: BNQ785E
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HD15
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
Driver File Version: 8.17.0010.1299 (English)
Driver Version: 14.200.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/22/2014 19:28:04, 1328352 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-2BD8-11CF-E076-2423BEC2C535}
Vendor ID: 0x1002
Device ID: 0x6898
SubSys ID: 0x032E1043
Revision ID: 0x0000
Driver Strong Name: oem70.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:14.200.0.0:pci\ven_1002&dev_6898
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=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: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Sound Devices

Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_14627522&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6873 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 3/29/2013 21:42:42, 3379272 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Speakers (3- Logitech H360 Headset)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: USB\VID_046D&PID_0A18&REV_0100&MI_00
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: USBAUDIO.sys
Driver Version: 6.01.7601.18208 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/12/2013 03:40:58, 109824 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Realtek Digital Output (Realtek High Definition Audio)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_14627522&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.6873 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 3/29/2013 21:42:42, 3379272 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: AMD HDMI Output (2- AMD High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: AtihdW76.sys
Driver Version: 7.12.0000.7719 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4/8/2014 07:20:34, 94720 bytes
Other Files:
Driver Provider: Advanced Micro Devices
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Sound Capture Devices

Description: Microphone (3- Logitech H360 Headset)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 6.01.7601.18208 (English)
Driver Attributes: Final Retail
Date and Size: 7/12/2013 03:40:58, 109824 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

DirectInput Devices

Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Logitech H360 Headset
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0x0A18
FF Driver: n/a

Device Name: Gaming Mouse G600
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC24A
FF Driver: n/a

Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a

Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a

Device Name: USB Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a

Device Name: Cordless Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a

Device Name: Cordless Receiver
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC52B
FF Driver: n/a

Device Name: Razer Anansi
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x010F
FF Driver: n/a

Device Name: Razer Anansi
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x010F
FF Driver: n/a

Poll w/ Interrupt: No

USB Devices

+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x3A37
| Matching Device ID: usb\root_hub
| Service: usbhub

Gameport Devices

PS/2 Devices