Computer Hope

Hardware => Hardware => Topic started by: JustnCase on March 24, 2010, 10:09:54 AM

Title: A Challenging Crash?
Post by: JustnCase on March 24, 2010, 10:09:54 AM
Okay, I have been searching the web for an answer for months and havnt found anything tht works or anyone who can help. I bought a Gateway FX6000-01 Series Computer about a year ago now. When I 1st bought it I only used it for playing World of Warraft and checking emails. Then I bought the online game Aion I installed it just fine and played it for about 4 hours that night with no problems. The next day I turned on my computer and started the game and at the login screen it crashed and powersave mode showed up on my computer monitor I could hear the music for about 5 secs after it crashed and then kicked into a repeating sound "like a broken record". Well this isnt the only game I have found that does this, Oblivion does it too. I then wanted to see if my GPU was stressing so I downloaded a couple video card stress test, the last one was video card stability test. As soon as I hit the run button and the world moved for a fraction of a sec then my computer crashes. My wife took it into Geeksquad because I bought the Manufacture Warrenty on it and after they had it for 3 days they told her there wasnt anything wrong with my graphics card, so they sent it home. The problem seemed to be getting worst so I took it back to them, after a day they could see it crashing and told my wife I had traces of a virus on my computer and for $130 they would remove it. I told my wife just bring it home and I'll remove them I got home from work that night and looked at it. they left there scan on my computer and in there log the only thing off was 2 tracking cookies "no viruses" all my drivers were up to date since then I have wiped the computer and reinstalled the drivers and overtime I'm finding it crashes for no reason I was playing WoW for about 30 min left it there and went downstairs for a drink came back and it had crashed. It also now crashes 75% of the time when I try to watch videos on youtube in full screen it will work in the small screen but just after it gets to full screen same kida crash, and everytime I try to start Media Player Classic it crashes. Three times it has crashed trying to open the Explorer but it was a different crash, my screen went to vertical lines across my whole screen. After the warrenty expired I tried adding RAM to it I put in 2 DDR3 2GB PCI 1600c7 chips for a total upgrade of 4GB. I have tried everything I can think of 6 times or more. I think its a hardware issue maybe the Graphics card but if thats it I'm going to be pissed that it wasnt replaced when I had the warrenty. I dont want to buy another graphics card if that doesnt fix the problem I'm pretty good with computers but I dont know everything so I wont pretend to. So I'm looking here to see if anyone knows something else. Here My Specs on my computer


------------------
System Information
------------------
Time of this report: 3/23/2010, 08:36:51
       Machine name: JUSTIN-PC
   Operating System: Windows Vista™ Home Premium (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.091208-0542)
           Language: English (Regional Setting: English)
System Manufacturer: Gateway
       System Model: FX6800-01e
               BIOS: Default System BIOS
          Processor: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz (8 CPUs), ~2.7GHz
             Memory: 7158MB RAM
          Page File: 2643MB used, 11883MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
     DxDiag Version: 6.00.6001.18000 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: 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: ATI Radeon HD 4800 Series
     Manufacturer: ATI Technologies Inc.
        Chip type: ATI display adapter (0x9442)
         DAC type: Internal DAC(400MHz)
       Device Key: Enum\PCI\VEN_1002&DEV_9442&SUBSYS_E810174B&REV_00
   Display Memory: 4083 MB
 Dedicated Memory: 1015 MB
    Shared Memory: 3067 MB
     Current Mode: 1920 x 1080 (32 bit) (60Hz)
          Monitor: Generic PnP Monitor
      Driver Name: atiumd64.dll,atidxx64.dll,atiumdag,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
   Driver Version: 8.14.0010.0678 (English)
      DDI Version: 10.1
Driver Attributes: Final Retail
 Driver Date/Size: 7/2/2009 09:54:53, 4059648 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp:
Device Identifier: {D7B71EE2-D702-11CF-5D76-1AC8A1C2C535}
        Vendor ID: 0x1002
        Device ID: 0x9442
        SubSys ID: 0xE810174B
      Revision ID: 0x0000
      Revision ID: 0x0000
      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=
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled

-------------
Sound Devices
-------------
            Description: Speakers (High Definition Audio Device)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10250198&REV_1001
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: HdAudio.sys
         Driver Version: 6.00.6002.18005 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 4/10/2009 22:39:51, 275456 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: Digital Output Device (HDMI) (High Definition Audio Device)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10250198&REV_1001
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: HdAudio.sys
         Driver Version: 6.00.6002.18005 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 4/10/2009 22:39:51, 275456 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

---------------------
Sound Capture Devices
---------------------
            Description: Microphone (High Definition Audio Device)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: HdAudio.sys
         Driver Version: 6.00.6002.18005 (English)
      Driver Attributes: Final Retail
          Date and Size: 4/10/2009 22:39:51, 275456 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

            Description: Line In (High Definition Audio Device)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: HdAudio.sys
         Driver Version: 6.00.6002.18005 (English)
      Driver Attributes: Final Retail
          Date and Size: 4/10/2009 22:39:51, 275456 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: G15 Gaming Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC226
        FF Driver: n/a

      Device Name: G15 Gaming Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC226
        FF Driver: n/a

      Device Name: G15 GamePanel LCD
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC227
        FF Driver: n/a

      Device Name: Media Center Interface
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04EB, 0xE030
        FF Driver: n/a

      Device Name: Media Center Interface
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04EB, 0xE030
        FF Driver: n/a

      Device Name: Media Center Interface
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x04EB, 0xE030
        FF Driver: n/a

      Device Name: USB2.0-CRW
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x0BDA, 0x0152
        FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x3A36
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/10/2009 22:39:52, 273920 bytes
| Driver: usbd.sys, 1/20/2008 19:47:25, 7680 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC226
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 22:33:40, 22528 bytes
| Driver: kbdclass.sys, 1/20/2008 19:47:27, 42040 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC227
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 22:33:40, 22528 bytes
| Driver: kbdclass.sys, 1/20/2008 19:47:27, 42040 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC232
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 22:33:40, 22528 bytes
| Driver: kbdclass.sys, 1/20/2008 19:47:27, 42040 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x04EB, 0xE030
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 22:33:40, 22528 bytes
| Driver: kbdclass.sys, 1/20/2008 19:47:27, 42040 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 1/20/2008 19:47:27, 64000 bytes
| Driver: kbdclass.sys, 1/20/2008 19:47:27, 42040 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC043
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 1/20/2008 19:46:59, 19968 bytes
| Driver: mouclass.sys, 1/20/2008 19:46:59, 39992 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC231
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 1/20/2008 19:46:59, 19968 bytes
| Driver: mouclass.sys, 1/20/2008 19:46:59, 39992 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/11/2009 00:15:53, 62440 bytes
| Driver: sermouse.sys, 1/20/2008 19:46:59, 26624 bytes
| Driver: mouclass.sys, 1/20/2008 19:46:59, 39992 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 454.6 GB
Total Space: 705.4 GB
File System: NTFS
      Model: ST3750630AS

      Drive: D:
      Model: HL-DT-ST DVDRAM GH15F
     Driver: c:\windows\system32\drivers\cdrom.sys, 6.00.6002.18005 (English), 4/10/2009 22:34:39, 79872 bytes

--------------
System Devices
--------------
     Name: Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40
Device ID: PCI\VEN_8086&DEV_3A40&SUBSYS_01981025&REV_00\3&11583659&0&E0
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:31, 178664 bytes

     Name: High Definition Audio Controller
Device ID: PCI\VEN_8086&DEV_3A3E&SUBSYS_01981025&REV_00\3&11583659&0&D8
   Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:41, 948736 bytes

     Name: Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C
Device ID: PCI\VEN_8086&DEV_3A3C&SUBSYS_01981025&REV_00\3&11583659&0&D7
   Driver: C:\Windows\system32\drivers\usbehci.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:36, 49664 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes
   Driver: C:\Windows\system32\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 04:17:29, 10752 bytes
   Driver: C:\Windows\system32\hcrstco.dll, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 17920 bytes

     Name: Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A
Device ID: PCI\VEN_8086&DEV_3A3A&SUBSYS_01981025&REV_00\3&11583659&0&EF
   Driver: C:\Windows\system32\drivers\usbehci.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:36, 49664 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes
   Driver: C:\Windows\system32\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 04:17:29, 10752 bytes
   Driver: C:\Windows\system32\hcrstco.dll, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 17920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A39
Device ID: PCI\VEN_8086&DEV_3A39&SUBSYS_01981025&REV_00\3&11583659&0&D2
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A38
Device ID: PCI\VEN_8086&DEV_3A38&SUBSYS_01981025&REV_00\3&11583659&0&D1
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A37
Device ID: PCI\VEN_8086&DEV_3A37&SUBSYS_01981025&REV_00\3&11583659&0&D0
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A36
Device ID: PCI\VEN_8086&DEV_3A36&SUBSYS_01981025&REV_00\3&11583659&0&EA
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A35
Device ID: PCI\VEN_8086&DEV_3A35&SUBSYS_01981025&REV_00\3&11583659&0&E9
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family USB Universal Host Controller - 3A34
Device ID: PCI\VEN_8086&DEV_3A34&SUBSYS_01981025&REV_00\3&11583659&0&E8
   Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/20/2008 19:47:25, 29184 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:39, 259584 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:52, 273920 bytes

     Name: Intel(R) ICH10 Family SMBus Controller - 3A30
Device ID: PCI\VEN_8086&DEV_3A30&SUBSYS_01981025&REV_00\3&11583659&0&FB
   Driver: n/a

     Name: Intel(R) ICH10R SATA AHCI Controller
Device ID: PCI\VEN_8086&DEV_3A22&SUBSYS_01981025&REV_00\3&11583659&0&FA
   Driver: C:\Windows\system32\DRIVERS\iaStor.sys, 8.05.0000.1032 (English), 7/20/2008 18:44:54, 402456 bytes

     Name: Intel(R) ICH10R LPC Interface Controller - 3A16
Device ID: PCI\VEN_8086&DEV_3A16&SUBSYS_01981025&REV_00\3&11583659&0&F8
   Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.00.6001.18000 (English), 1/20/2008 19:46:51, 17976 bytes

     Name: Intel(R) 5520/5500/X58 I/O Hub Throttle Registers - 3438
Device ID: PCI\VEN_8086&DEV_3438&SUBSYS_00000000&REV_12\3&11583659&0&A3
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 I/O Hub System Management Registers - 342E
Device ID: PCI\VEN_8086&DEV_342E&SUBSYS_00000000&REV_12\3&11583659&0&A0
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller - 342D
Device ID: PCI\VEN_8086&DEV_342D&SUBSYS_00000000&REV_12\3&11583659&0&98
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 Routing and Protocol Layer Registers Port 0 - 3426
Device ID: PCI\VEN_8086&DEV_3426&SUBSYS_00000000&REV_12\3&11583659&0&81
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 Physical and Link Layer Registers Port 0 - 3425
Device ID: PCI\VEN_8086&DEV_3425&SUBSYS_00000000&REV_12\3&11583659&0&80
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 I/O Hub Control Status and RAS Registers - 3423
Device ID: PCI\VEN_8086&DEV_3423&SUBSYS_00000000&REV_12\3&11583659&0&A2
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers - 3422
Device ID: PCI\VEN_8086&DEV_3422&SUBSYS_00000000&REV_12\3&11583659&0&A1
   Driver: n/a

     Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 7 - 340E
Device ID: PCI\VEN_8086&DEV_340E&SUBSYS_01981025&REV_12\3&11583659&0&38
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:31, 178664 bytes

     Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 3 - 340A
Device ID: PCI\VEN_8086&DEV_340A&SUBSYS_01981025&REV_12\3&11583659&0&18
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:31, 178664 bytes

     Name: Intel(R) 5520/5500/X58 I/O Hub PCI Express Root Port 1 - 3408
Device ID: PCI\VEN_8086&DEV_3408&SUBSYS_01981025&REV_12\3&11583659&0&08
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:31, 178664 bytes

     Name: Intel(R) 5520/5500/X58 I/O Hub to ESI Port - 3405
Device ID: PCI\VEN_8086&DEV_3405&SUBSYS_01981025&REV_12\3&11583659&0&00
   Driver: n/a

     Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_01981025&REV_90\3&11583659&0&F0
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:31, 178664 bytes

     Name: Intel(R) 82567LF-2 Gigabit Network Connection
Device ID: PCI\VEN_8086&DEV_10CD&SUBSYS_01981025&REV_00\3&11583659&0&C8
   Driver: C:\Windows\system32\DRIVERS\e1y60x64.sys, 9.52.0009.0000 (English), 6/13/2008 01:41:54, 316544 bytes
   Driver: C:\Windows\system32\e1y60x64.din, 5/29/2008 05:15:48, 2723 bytes
   Driver: C:\Windows\system32\NicCo26.dll, 2.01.0000.0000 (English), 8/23/2007 17:58:16, 36472 bytes
   Driver: C:\Windows\system32\NicInstQ.dll, 9.10.0002.0000 (English), 6/4/2008 02:00:02, 57464 bytes
   Driver: C:\Windows\system32\e1000msg.dll, 9.08.0000.0000 (English), 12/13/2007 22:06:06, 121440 bytes

     Name: Standard AHCI 1.0 Serial ATA Controller
Device ID: PCI\VEN_197B&DEV_2363&SUBSYS_2363197B&REV_03\4&4054087&0&0008
   Driver: C:\Windows\system32\DRIVERS\msahci.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:21, 29656 bytes
   Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:24, 49640 bytes
   Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:00, 20952 bytes
   Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.00.6002.18005 (English), 4/11/2009 00:15:28, 123368 bytes

     Name: LSI PCI-SV92EX Soft Modem
Device ID: PCI\VEN_11C1&DEV_0630&SUBSYS_063011C1&REV_01\4&C74F31&0&00E0
   Driver: C:\Windows\system32\DRIVERS\agrsm64.sys, 2.02.0098.0000 (English), 8/13/2009 15:20:46, 1209856 bytes
   Driver: C:\Program Files\LSI SoftModem\agr64svc.exe, 1.00.0000.0010 (English), 3/27/2009 22:10:16, 16896 bytes
   Driver: C:\Windows\agrsmdel.exe, 2.07.0005.0000 (English), 6/9/2009 17:28:36, 64000 bytes
   Driver: C:\Windows\agrdel64.exe, 2.07.0005.0000 (English), 6/9/2009 17:34:50, 42496 bytes
   Driver: C:\Program Files\LSI SoftModem\agrsmdel.ico, 5/27/2009 20:17:46, 41812 bytes
   Driver: C:\Windows\system32\agrsco64.dll, 1.00.0000.0008 (English), 3/27/2009 22:12:46, 14848 bytes

     Name: VIA OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1106&DEV_3044&SUBSYS_01981025&REV_C0\4&1963F9A4&0&30F0
   Driver: C:\Windows\system32\DRIVERS\ohci1394.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:49, 72448 bytes
   Driver: C:\Windows\system32\DRIVERS\1394bus.sys, 6.00.6001.18000 (English), 1/20/2008 19:46:54, 65280 bytes

     Name: High Definition Audio Controller
Device ID: PCI\VEN_1002&DEV_AA30&SUBSYS_AA30174B&REV_00\4&1635B5A2&0&0118
   Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.00.6002.18005 (English), 4/10/2009 22:39:41, 948736 bytes

     Name: ATI Radeon HD 4800 Series
Device ID: PCI\VEN_1002&DEV_9442&SUBSYS_E810174B&REV_00\4&1635B5A2&0&0018
   Driver: C:\Windows\system32\DRIVERS\atikmdag.sys, 8.01.0001.0921 (English), 7/2/2009 10:51:28, 6036480 bytes
   Driver: C:\Windows\system32\DRIVERS\ati2erec.dll, 1.00.0000.0019 (English), 7/2/2009 09:18:06, 53248 bytes
   Driver: C:\Windows\system32\atiumd64.dll, 8.14.0010.0678 (English), 7/2/2009 09:54:53, 4059648 bytes
   Driver: C:\Windows\system32\atiumd6a.dll, 8.14.0010.0228 (English), 7/2/2009 09:49:49, 2622464 bytes
   Driver: C:\Windows\system32\atitmm64.dll, 6.14.0011.0022 (English), 7/2/2009 10:14:56, 120320 bytes
   Driver: C:\Windows\system32\atiicdxx.dat, 6/18/2009 12:29:04, 197654 bytes
   Driver: C:\Windows\system32\amdpcom64.dll, 8.14.0010.0023 (English), 7/2/2009 09:32:47, 52224 bytes
   Driver: C:\Windows\system32\atimpc64.dll, 8.14.0010.0023 (English), 7/2/2009 09:32:47, 52224 bytes
   Driver: C:\Windows\system32\atiadlxx.dll, 6.14.0010.1050 (English), 7/2/2009 09:32:17, 251904 bytes
   Driver: C:\Windows\system32\atiumd6a.cap, 7/2/2009 09:47:34, 219120 bytes
   Driver: C:\Windows\system32\atimuixx.dll, 6.14.0010.1001 (English), 7/2/2009 10:14:09, 12288 bytes
   Driver: C:\Windows\system32\atiesrxx.exe, 6.14.0011.1033 (English), 7/2/2009 10:16:05, 203264 bytes
   Driver: C:\Windows\system32\atieclxx.exe, 6.14.0011.1033 (English), 7/2/2009 10:16:39, 420352 bytes
   Driver: C:\Windows\system32\atipdl64.dll, 6.14.0010.2556 (English), 7/2/2009 10:14:37, 421376 bytes
   Driver: C:\Windows\system32\atiedu64.dll, 6.14.0010.2514 (English), 7/2/2009 10:14:03, 59392 bytes
   Driver: C:\Windows\system32\ATIDEMGX.dll, 2.00.3470.22105 (English), 7/2/2009 10:16:51, 442368 bytes
   Driver: C:\Windows\system32\atio6axx.dll, 6.14.0010.8787 (English), 7/2/2009 10:13:09, 15062016 bytes
   Driver: C:\Windows\system32\aticaldd64.dll, 6.14.0010.0344 (English), 7/2/2009 09:28:16, 4289536 bytes
   Driver: C:\Windows\system32\aticalrt64.dll, 6.14.0010.0344 (English), 7/2/2009 09:28:41, 48640 bytes
   Driver: C:\Windows\system32\aticalcl64.dll, 6.14.0010.0344 (English), 7/2/2009 09:28:29, 41984 bytes
   Driver: C:\Windows\system32\atibtmon.exe, 2.00.0000.0000 (English), 5/11/2009 14:35:29, 118784 bytes
   Driver: C:\Windows\system32\atidxx64.dll, 8.15.0010.0212 (English), 7/2/2009 10:05:28, 2921984 bytes
   Driver: C:\Windows\SysWOW64\atiumdag.dll, 8.14.0010.0678 (English), 7/2/2009 09:59:37, 3105280 bytes
   Driver: C:\Windows\SysWOW64\atiumdva.dll, 8.14.0010.0228 (English), 7/2/2009 09:44:32, 2868224 bytes
   Driver: C:\Windows\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 7/2/2009 09:32:41, 51712 bytes
   Driver: C:\Windows\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 7/2/2009 09:32:41, 51712 bytes
   Driver: C:\Windows\SysWOW64\atiadlxy.dll, 6.14.0010.1050 (English), 7/2/2009 09:32:10, 184320 bytes
   Driver: C:\Windows\SysWOW64\atiumdva.cap, 7/2/2009 09:44:10, 219120 bytes
   Driver: C:\Windows\SysWOW64\atipdlxx.dll, 6.14.0010.2556 (English), 7/2/2009 10:14:29, 356352 bytes
   Driver: C:\Windows\SysWOW64\Oemdspif.dll, 6.15.0006.0005 (English), 7/2/2009 10:14:15, 274432 bytes
   Driver: C:\Windows\SysWOW64\ati2edxx.dll, 6.14.0010.2514 (English), 7/2/2009 10:13:58, 43520 bytes
   Driver: C:\Windows\SysWOW64\atioglxx.dll, 6.14.0010.8787 (English), 7/2/2009 09:51:13, 11650560 bytes
   Driver: C:\Windows\SysWOW64\atidxx32.dll, 8.15.0010.0212 (English), 7/2/2009 10:10:41, 2469888 bytes
   Driver: C:\Windows\SysWOW64\aticaldd.dll, 6.14.0010.0344 (English), 7/2/2009 09:27:26, 3264512 bytes
   Driver: C:\Windows\SysWOW64\aticalrt.dll, 6.14.0010.0344 (English), 7/2/2009 09:28:39, 53248 bytes
   Driver: C:\Windows\SysWOW64\aticalcl.dll, 6.14.0010.0344 (English), 7/2/2009 09:28:27, 53248 bytes
   Driver: C:\Windows\atiogl.xml, 6/17/2009 00:53:12, 18333 bytes
   Driver: C:\Windows\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 2/3/2009 13:52:07, 51200 bytes
   Driver: C:\Windows\system32\ATIODE.exe, 1.00.0000.0001 (English), 2/18/2009 10:55:23, 332288 bytes

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,,
WMAPro over S/PDIF DMO,0x00600800,1,1,,
WMSpeech Decoder DMO,0x00600800,1,1,,
MP3 Decoder DMO,0x00600800,1,1,,
Mpeg4s Decoder DMO,0x00800001,1,1,,
WMV Screen decoder DMO,0x00600800,1,1,,
WMVideo Decoder DMO,0x00800001,1,1,,
Mpeg43 Decoder DMO,0x00800001,1,1,,
Mpeg4 Decoder DMO,0x00800001,1,1,,
Full Screen Renderer,0x00200000,1,0,,6.06.6002.18158
Multiple File Output,0x00200000,2,2,WMM2FILT.dll,
WMT Black Frame Generator,0x00200000,1,1,WMM2FILT.dll,
WMT Import Filter,0x00200000,0,1,WMM2FILT.dll,
DV Muxer,0x00400000,0,0,,6.06.6001.18000
Color Space Converter,0x00400001,1,1,,6.06.6002.18158
WMT Interlacer,0x00200000,1,1,WMM2FILT.dll,
WM ASF Reader,0x00400000,0,0,,11.00.6001.7000
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,11.00.6001.7000
AVI Splitter,0x00600000,1,1,,6.06.6002.18158
VGA 16 Color Ditherer,0x00400000,1,1,,6.06.6002.18158
Microsoft MPEG-2 Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,11.00.6001.7110
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.6002.18005
WMT Format Conversion,0x00200000,1,1,WMM2FILT.dll,
9x8Resize,0x00200000,1,1,WMM2FILT.dll,
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.6001.18000
WMT Virtual Source,0x00200000,0,1,WMM2FILT.dll,
Microsoft TV Caption Decoder,0x00200001,1,0,MSTVCapn.dll,6.00.6001.18000
MJPEG Decompressor,0x00600000,1,1,,6.06.6002.18158
CBVA DMO wrapper filter,0x00200000,1,1,cbva.dll,6.00.6002.18005
MPEG-I Stream Splitter,0x00600000,1,2,,6.06.6002.18158
SAMI (CC) Parser,0x00400000,1,1,,6.06.6002.18158
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6001.18000
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.6002.18005
WMT AudioAnalyzer,0x00200000,1,1,WMM2FILT.dll,
Microsoft MPEG-2 Video Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6002.18005
Stretch Video,0x00200000,1,1,WMM2FILT.dll,
Internal Script Command Renderer,0x00800001,1,0,,6.06.6002.18158
MPEG Audio Decoder,0x03680001,1,1,,6.06.6002.18158
DV Splitter,0x00600000,1,2,,6.06.6001.18000
Video Mixing Renderer 9,0x00200000,1,0,,6.06.6002.18158
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,11.00.6002.18005
Frame Eater,0x00200000,1,1,WMM2FILT.dll,
Allocator Fix,0x00200000,1,1,WMM2FILT.dll,
ACM Wrapper,0x00600000,1,1,,6.06.6002.18158
Video Renderer,0x00800001,1,0,,6.06.6002.18158
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.6001.18000
Capture ASF Writer,0x00200000,0,0,WMM2FILT.dll,
Line 21 Decoder,0x00600000,1,1,,
Video Port Manager,0x00600000,2,1,,6.06.6002.18158
Video Renderer,0x00400000,1,0,,6.06.6002.18158
Bitmap Generate,0x00200000,1,1,WMM2FILT.dll,
Proxy Sink,0x00200000,1,0,WMM2FILT.dll,
Proxy Source,0x00200000,0,1,WMM2FILT.dll,
WM ASF Writer,0x00400000,0,0,,11.00.6001.7000
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.00.6000.16386
WMT Sample Information Filter,0x00200000,1,1,WMM2FILT.dll,
File writer,0x00200000,1,0,,6.06.6001.18000
DVD Navigator,0x00200000,0,3,,6.06.6002.18005
WMT DV Extract,0x00200000,1,1,WMM2FILT.dll,
Overlay Mixer2,0x00200000,1,1,,
Microsoft MPEG-2 Audio Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6002.18005
WST Pager,0x00800000,1,1,WSTPager.ax,6.06.6001.18000
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.6002.18005
Record Queue,0x00200000,1,1,WMM2FILT.dll,
DV Video Decoder,0x00800000,1,1,,6.06.6001.18000
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.6002.18005
Null Renderer,0x00200000,1,0,qedit.dll,6.06.6002.18005
WMT Log Filter,0x00200000,1,1,WMM2FILT.dll,
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.6001.18000
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,11.00.6002.18005
WMT Virtual Renderer,0x00200000,1,0,WMM2FILT.dll,
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.6001.18000
Smart Tee,0x00200000,1,2,,6.06.6001.18000
Overlay Mixer,0x00200000,0,0,,
AVI Decompressor,0x00600000,1,1,,6.06.6002.18158
WMT MuxDeMux Filter,0x00200000,0,0,WMM2FILT.dll,
NetBridge,0x00200000,2,0,netbridge.dll,6.01.6001.18000
AVI/WAV File Source,0x00400000,0,2,,6.06.6002.18158
WMT Volume,0x00200000,1,1,WMM2FILT.dll,
Wave Parser,0x00400000,1,1,,6.06.6002.18158
MIDI Parser,0x00400000,1,1,,6.06.6002.18158
Multi-file Parser,0x00400000,1,1,,6.06.6002.18158
File stream renderer,0x00400000,1,1,,6.06.6002.18158
WMT VIH2 Fix,0x00200000,1,1,WMM2FILT.dll,
Microsoft MPEG-1/DD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,11.00.6001.7000
AVI Mux,0x00200000,1,0,,6.06.6001.18000
Line 21 Decoder 2,0x00600002,1,1,,6.06.6002.18158
File Source (Async.),0x00400000,0,1,,6.06.6002.18158
File Source (URL),0x00400000,0,1,,6.06.6002.18158
Media Center Extender Encryption Filter,0x00200000,2,2,Mcx2Filter.dll,6.01.6002.18005
AudioRecorder WAV Dest,0x00200000,0,0,,6.00.6000.16386
AudioRecorder Wave Form,0x00200000,0,0,,6.00.6000.16386
SoundRecorder Null Renderer,0x00200000,0,0,,6.00.6000.16386
Infinite Pin Tee Filter,0x00200000,1,1,,6.06.6001.18000
WMT Switch Filter,0x00200000,1,1,WMM2FILT.dll,
Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.00.6002.18005
Uncompressed Domain Shot Detection Filter,0x00200000,1,1,WMM2FILT.dll,
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.6002.18005
MPEG Video Decoder,0x40000001,1,1,,6.06.6002.18158

WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,,6.00.6001.18000

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,,
WMVideo9 Encoder DMO,0x00600800,1,1,,
MSScreen 9 encoder DMO,0x00600800,1,1,,
DV Video Encoder,0x00200000,0,0,,6.06.6001.18000
MJPEG Compressor,0x00200000,0,0,,6.06.6002.18158

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,,
WMAudio Encoder DMO,0x00600800,1,1,,
IMA ADPCM,0x00200000,1,1,,6.06.6002.18158
PCM,0x00200000,1,1,,6.06.6002.18158
Microsoft ADPCM,0x00200000,1,1,,6.06.6002.18158
GSM 6.10,0x00200000,1,1,,6.06.6002.18158
CCITT A-Law,0x00200000,1,1,,6.06.6002.18158
CCITT u-Law,0x00200000,1,1,,6.06.6002.18158
MPEG Layer-3,0x00200000,1,1,,6.06.6002.18158

Audio Capture Sources:
Microphone (High Definition Aud,0x00200000,0,0,,6.06.6001.18000
Line In (High Definition Audio ,0x00200000,0,0,,6.06.6001.18000

Midi Renderers:
Default MidiOut Device,0x00800000,1,0,,6.06.6002.18158
Microsoft GS Wavetable Synth,0x00200000,1,0,,6.06.6002.18158

WDM Streaming Capture Devices:
HD Audio Mixed capture,0x00200000,1,1,,6.00.6001.18000

WDM Streaming Rendering Devices:
Realtek HDA HDMI Out,0x00200000,1,1,,6.00.6001.18000
HD Audio HDMI out,0x00200000,1,1,,6.00.6001.18000
HD Audio Headphone/Speakers,0x00200000,1,1,,6.00.6001.18000

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.6002.18005

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6001.18000

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.6002.18005
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.6001.18000

BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,0,EncDec.dll,6.06.6002.18005
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.6002.18005
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.6002.18005

WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,,6.00.6001.18000

Audio Renderers:
Speakers (High Definition Audio,0x00200000,1,0,,6.06.6002.18158
Default DirectSound Device,0x00800000,1,0,,6.06.6002.18158
Default WaveOut Device,0x00200000,1,0,,6.06.6002.18158
Digital Output Device (HDMI) (H,0x00200000,1,0,,6.06.6002.18158
DirectSound: Digital Output Device (HDMI) (High Definition Audio Device),0x00200000,1,0,,6.06.6002.18158
DirectSound: Speakers (High Definition Audio Device),0x00200000,1,0,,6.06.6002.18158

Title: Re: A Challenging Crash?
Post by: Azzaboi on March 24, 2010, 10:35:49 AM
It might be an issue with damaged memory, this will only crash the computer when it reachs those memory addresses (might seem like random crashing) or do random things if corrupted. Test your memory and if detected remove the memory, replacing one at a time till you find the bad one.

To do this, you can use 'Windows Memory Diagnostic' from Microsoft. The diagnostic includes a comprehensive set of memory tests.  You can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard.
http://oca.microsoft.com/en/windiag.asp

To run Windows Memory Diagnostic, you must reboot your computer with the disk or CD-ROM on which you installed Windows Memory Diagnostic in the drive.  This might take a while to fully run (30 mins). It will also do two passes to ensure.

Upgrading memory can be a big issue. When installing/removing RAM ensure you touch the metal case or use an anti-static wrist band. Static can easily damage it. Make sure they are firmly pressed down and installed correctly, it's easy for an edge to be sitting up on one once clipped into place. Make sure the RAM is all the same type and compatible. It will default to the slowest ones speed, so it's wasted to have some fast ones and one or two different slower ones. The specs and timing are written on them and you can check in your motherboard manual the different RAM types supported.
Title: Re: A Challenging Crash?
Post by: JustnCase on March 24, 2010, 11:36:26 AM
Okay... So I tried to chnge out the RAM to see if it was the problem. I took out the original 3 1gb and only left in the 2 2gb DDR3 I just bought and its still crashing. I also tried 1 2gb with 1 1gb and 2 1gb RAM and chnged them around. I am very careful not to touch anything and I was using a staic strap to be safe when I 1st installed the 2 I just bought and just now. also the 2 I just bought looks to have a hard case over them to protect it too. I'm going to try to run the bootup cd that you were talking about and see if that tells me anything.
Title: Re: A Challenging Crash?
Post by: Computer_Commando on March 24, 2010, 02:01:07 PM
...
---------------
Display Devices
---------------
        Card name: ATI Radeon HD 4800 Series
     Manufacturer: ATI Technologies Inc.
        Chip type: ATI display adapter (0x9442)
         DAC type: Internal DAC(400MHz)
       Device Key: Enum\PCI\VEN_1002&DEV_9442&SUBSYS_E810174B&REV_00
   Display Memory: 4083 MB
 Dedicated Memory: 1015 MB
    Shared Memory: 3067 MB

 ...
I suspect this is where the problem lies:  1GB Dedicated Memory, 3GB Shared Memory.
You can't expect the performance of Shared memory to equal that of Dedicated graphics memory.
Try reducing the Shared Memory to 0MB and see what happens.
Title: Re: A Challenging Crash?
Post by: JustnCase on March 25, 2010, 09:24:09 AM
To do this, you can use 'Windows Memory Diagnostic' from Microsoft. The diagnostic includes a comprehensive set of memory tests.  You can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard.
http://oca.microsoft.com/en/windiag.asp

To run Windows Memory Diagnostic, you must reboot your computer with the disk or CD-ROM on which you installed Windows Memory Diagnostic in the drive.  This might take a while to fully run (30 mins). It will also do two passes to ensure.


I just finished running the Windows Memory scan. I did 4 passes on extended scan to make sure... everthing was good everything said success over and over.

I suspect this is where the problem lies:  1GB Dedicated Memory, 3GB Shared Memory.
You can't expect the performance of Shared memory to equal that of Dedicated graphics memory.
Try reducing the Shared Memory to 0MB and see what happens.

I'll try just about anything however I'm not sure how to go about reducing the shared memory to 0. I'm running Vista is there anyway you could tell me how to reduce it down to 0?.. Once again Thank you all for you input, this all just alows me to check one more thing off the board as whats wrong.
Title: Re: A Challenging Crash?
Post by: Azzaboi on March 25, 2010, 03:32:28 PM
If you need some other ideas to check, I would suggest...

Checking the Power Supply - a bad (or insufficient) power supply is the most common cause for random crashes, especially if you have a lot of cards, drives, or fans, or have a dual-processor motherboard. After upgrading my graphic card to one of the latest, it would draw so much power, killed off other components, the card required a minimum 550W, I had a 450W which I updated to 700W which resolved all issues.

Mixed formated hard drives, like a FAT32 and a NTFS hard drive, it is best to make them all NTFS format, if your 'swap file' virtual memory is on the other hard drive from the Operating System it can cause crashing if the format is different.

Incompatible Drivers, Vista is evil against driver compatiblity, Win7 would of at least informed you before installing unstable drivers. Make sure they are 100% compatible with Vista, for example the sound card drivers, etc.

If you have a USB hub, try eliminating it and see if that solves the problem, this could be due to IQ conficts with other devices. Check under the Control Panel / Device Manager.

A computer will crash if the processor overheats. Make sure your computer case has adequate ventilation and not hard up against a wall or on the floor, or clogged fans, etc.
Title: Re: A Challenging Crash?
Post by: BC_Programmer on March 25, 2010, 03:46:14 PM
Quote
I then wanted to see if my GPU was stressing so I downloaded a couple video card stress test, the last one was video card stability test. As soon as I hit the run button and the world moved for a fraction of a sec then my computer crashes.

Quote
Three times it has crashed trying to open the Explorer but it was a different crash, my screen went to vertical lines across my whole screen.


This points to either the graphics card or power supply.
Title: Re: A Challenging Crash?
Post by: JustnCase on March 25, 2010, 03:59:05 PM
Okay. I have had a little more than a few people say that maybe the Power Supply wasnt enough. I just assumed that since this computer was build by a company like Gateway and was selling it then they would have put the right power supply to match the rest of the hardware... Well my father told me what Assume spells so I'm going to try a new power supply. Have to wait till payday though. I'll post in a couple of weeks and let you all know the outcome. Thanks for the help.
Title: Re: A Challenging Crash?
Post by: BC_Programmer on March 25, 2010, 04:34:36 PM
Okay. I have had a little more than a few people say that maybe the Power Supply wasnt enough. I just assumed that since this computer was build by a company like Gateway and was selling it then they would have put the right power supply to match the rest of the hardware... Well my father told me what Assume spells so I'm going to try a new power supply. Have to wait till payday though. I'll post in a couple of weeks and let you all know the outcome. Thanks for the help.

For most manufactured PCs, the Power supply is usually barely adequate. After all, the CPU speed and RAM and hard disk sell, the PSU wattage doesn't, so they skimp on those.
Title: Re: A Challenging Crash?
Post by: Azzaboi on March 25, 2010, 05:36:23 PM
First before you fork out, check and see if you need to or it's possibly damaged?

i7 Core Motherboard will take it's fair share of power depending on fans, light tubes, how many hard drives, etc. The main power hungry component is however the graphics card.

ATI Radeon HD 4850 Power Requirements
450 Watt or greater power supply with 75 Watt 6-pin PCI Express® power connector recommended (550 Watt and two 6-pin connectors for ATI CrossFireX™ technology in dual mode)

ATI Radeon HD 4870 System Requirements
500 Watt or greater power supply with two 75W 6-pin PCI Express® power connectors recommended (600 Watt and four 6-pin connectors for ATI CrossFireX™ technology in dual mode)


There's a lot of specs to buying a good power supply, single vs double rail, connector outputs, voltage ranges, max output capacity, protection and regulatory, etc. Also fans noise, nothing more annoying than watching a movie with a loud purring of the fan. Cooler Master do ultra silent fans and are quite powerful and stable, but look around and get reviews if you do plan to have it replaced.
Title: Re: A Challenging Crash?
Post by: JustnCase on March 26, 2010, 09:33:42 AM
Thank you so much for the info. I have the ATI HD4850 and my power supply is a 450W I had a guy tell me "Thats the bare minimum for that Graphics card you should get a 650W". he didnt tell me any suggestions on what to get. I will be looking into some forums to find whats a good power supply. Thank you again.
Title: Re: A Challenging Crash?
Post by: Azzaboi on March 26, 2010, 10:57:07 AM
Hmm, well if you believe it is the fault and wish to upgrade here are some things to look for. First of all the dimensions of the power supply, will it fit or will you be stuck with buying a new case as well? The connectors given, will they power all devices and at a stable voltage. Voltage of the rail(s), with your CPU and graphic card it would be recommended to go 12v rail. Multiple +12 V Rails will however cost more and balance load (good if overclocking or multiple graphic cards, etc). Overcurrent protection on the powersupply, how will it react to overheating, powerspikes, etc.

(Just as an option example)
Maybe the 'Silent Pro M 700W Cooler Master Power Supply' would meant your computer specs plus allow for any upgrades in the future?

It's a good price (well checking in NZ pricespy) and has good reviews. Single rail 12v with up to 50A but won't have any problems powering even the most demanding SLI (multiple graphics card joined together). Two 6 + 2 pin PCI-e connectors. So it allows for some upgrading in the future, some newer graphic cards will take both.

The cables are connectible (can be added/removed) this allows clean setup and more air around components.

Max Output Capacity goes up to 850W (adjustable power is good, it's able to do way more than the given 700W but to stay stable and cool)
135mm Ultra Silent Fan
Input Voltage: 90-264V (Auto Range)
Input Current: 10A@115Vac, 6A@230Vac
Power Good Signal: 100-500ms
Efficiency: ~85%
Protection: OVP / UVP / OCP / OPP / OTP / SCP / OLP
Regulatory: NEMKO / TUV / CE / GOST / C-tick / FCC / UL
Dimensions: 150x150x86(mm)

Connectors:
M/B 20+4 Pin Connector x 1
CPU 4+4 Pin x 1
PCI-E 6+2 Pin x 2
4 Pin Peripheral x 5
SATA x 9
4 Pin Floppy x 1
Title: Re: A Challenging Crash?
Post by: Computer_Commando on March 26, 2010, 12:33:18 PM
...I'll try just about anything however I'm not sure how to go about reducing the shared memory to 0. I'm running Vista is there anyway you could tell me how to reduce it down to 0?...
Setting for Shared Memory is in the CMOS Setup (BIOS), probably under "Advanced Chipset Features", "VGA Share Memory Size".  Set to "Disable".
Title: Re: A Challenging Crash?
Post by: JustnCase on March 26, 2010, 01:23:34 PM
Setting for Shared Memory is in the CMOS Setup (BIOS), probably under "Advanced Chipset Features", "VGA Share Memory Size".  Set to "Disable".

I went into BIOS and I seen "Basic CMOS" and "Advanced Chipset Features" I looked under both of these... CMOS didn't say anything about "Advanced Chipset Features" or VGA. So I figured in this case "Advanced Chipset Features" at the begining is probably what you were refering too... "Advanced Chipset Features" had everything under it Enabled but didnt say shared or VGA. It had these listed.

Intel EIST          [Enabled]
Intel XD Bit        [Enabled]
Intel VT              [Enabled]
Intel VT-d           [Enabled]

which one of these should I disable to disable the shared memory, if its possible.
Title: Re: A Challenging Crash?
Post by: Salmon Trout on March 26, 2010, 01:39:44 PM
Mixed formated hard drives, like a FAT32 and a NTFS hard drive, it is best to make them all NTFS format, if your 'swap file' virtual memory is on the other hard drive from the Operating System it can cause crashing if the format is different.

This is nonsense.
Title: Re: A Challenging Crash?
Post by: Allan on March 26, 2010, 01:42:54 PM
This is nonsense.

Most of what is in his posts is generally nonsense, and he gets upset when others call him on it.
Title: Re: A Challenging Crash?
Post by: Computer_Commando on March 26, 2010, 02:38:02 PM
I went into BIOS and I seen "Basic CMOS" and "Advanced Chipset Features" I looked under both of these... CMOS didn't say anything about "Advanced Chipset Features" or VGA. So I figured in this case "Advanced Chipset Features" at the begining is probably what you were refering too... "Advanced Chipset Features" had everything under it Enabled but didnt say shared or VGA. It had these listed.

Intel EIST          [Enabled]
Intel XD Bit        [Enabled]
Intel VT              [Enabled]
Intel VT-d           [Enabled]

which one of these should I disable to disable the shared memory, if its possible.
Gateway "minimal BIOS" doesn't let you do much.  I see no mention of the BIOS in any of the documentation.  Online documentation is weak.  I would think a computer that powerful should be able to run anything without any issues.
I think you're going to have to contact them.
http://support.gateway.com/s/PC/FX/FX6800/FX6800nv.shtml

I do see a recent BIOS version, but I would hold off on that until you hear from Gateway.
http://support.gateway.com/support/drivers/search.asp?st=pn&param=FX6800
Title: Re: A Challenging Crash?
Post by: Azzaboi on March 26, 2010, 05:04:09 PM
Quote
Quote
This is nonsense.
Most of what is in his posts is generally nonsense, and he gets upset when others call him on it.

And you always just grin and smile hiding behind someone else Allan, having to have ya say. Like the time someone said thanks that was helpful, solved the problem to me and you say to ignore it, lol. What about the time when someone questioned you, you just say do what I said to him! pff

I don't get upset if people call me on it, I get upset with the morons like you that spend all your time looking for the smallest things and not even saying anything to fix it or help out solving the problem. Yet you call yourself an Admin?

Have you actually tried it? I didn't say there's an issue with mixed format, for example one FAT32 and a NTFS drive, but if you end up putting the swap file on the other hard drive than the operating system, it has a fit swapping it across the two which can even become unstable.

Anyway it was just another option and probably not clearly written.
Title: Re: A Challenging Crash?
Post by: Computer_Commando on March 26, 2010, 05:14:36 PM
Thank you so much for the info. I have the ATI HD4850 and my power supply is a 450W I had a guy tell me "Thats the bare minimum for that Graphics card you should get a 650W". he didnt tell me any suggestions on what to get. I will be looking into some forums to find whats a good power supply. Thank you again.
PSU wattage ratings are a joke and mean almost nothing.  Some manufacturers add all outputs together and claim that's the wattage.  Almost no PSU can produce max current at every voltage listed.  If you haven't added any power hungry devices to your Gateway, the standard PSU is sufficient.
Title: Re: A Challenging Crash?
Post by: Salmon Trout on March 26, 2010, 05:36:16 PM
if you end up putting the swap file on the other hard drive than the operating system, it has a fit swapping it across the two which can even become unstable.

This is even more stupid nonsense than you wrote before, idiotboi Azzaboi. I think it is time you poured yourself a nice tall cool glass of STFU.

Title: Re: A Challenging Crash?
Post by: patio on March 26, 2010, 07:09:53 PM
This is even more stupid nonsense than you wrote before, idiotboi Azzaboi. I think it is time you poured yourself a nice tall cool glass of STFU.


His advice has so far been questionable at best...
However given time that may change...
Title: Re: A Challenging Crash?
Post by: BC_Programmer on March 26, 2010, 07:19:07 PM
It hasn't been called a "Swap file" since windows 3.x. Maybe 9x, can't remember. in NT it's a pagefile. Pedantic, yes. I just want to be a part of the excitement.
 
Gotta love how quick some people turn to ad hominem attacks though. "remember the time X happened, and you looked so X, therefore you are X now as well". priceless.


PSU wattage ratings are a joke and mean almost nothing.  Some manufacturers add all outputs together and claim that's the wattage.  Almost no PSU can produce max current at every voltage listed.  If you haven't added any power hungry devices to your Gateway, the standard PSU is sufficient.

This is true, so it leaves the Graphics card, since we've tested the memory.

Title: Re: A Challenging Crash?
Post by: Azzaboi on March 26, 2010, 08:26:56 PM
 Mr Trout...

For stupid nonsense, it actually has happened in the past, ages ago, I believe it was on Windows XP... but what have you suggested? It was only one of many I suggested to solve the issue at hand. Yes I guess you could say it's a "remember the time X happened" like BC_Programmer said. Sorry I called it a swap file rather than pagefile. If it's happened before can't it possibly happen again, just trying to cover different areas. Also if you used NTFS over FAT32 you would have a better system and performance, but ok ignore that part if it's such a big woopee-doo for you!

This forum is nothing but a joke, trying to prove who's the biggest geek, rather than helping out people with their problems. Freaken microsoft lovers with no virus scanners, thinking they are secure, lol.
Title: Re: A Challenging Crash?
Post by: patio on March 26, 2010, 08:37:36 PM
Get over yourself...
If you make questionable comments or give suspect advice be prepared to get called out on it.
If you choose to just label us as fanboyz and not be able to admit your shortcomings then so be it...

This is not the 1st time we've seen it...
Title: Re: A Challenging Crash?
Post by: BC_Programmer on March 26, 2010, 09:08:46 PM
Quote
For stupid nonsense, it actually has happened in the past, ages ago, I believe it was on Windows XP
Alright then. No idea what you're talking about.



Quote
but what have you suggested?

Interesting.

What you suggested is analogous to somebody being mauled by a bear and you suggest they eat a lime wedge. Completely unrelated. mixing NTFS and FAT32 is a performance thing and will not cause the symptoms described by the OP.

The issue is almost certainly the graphics card, not their choice of bloody file system.

Quote
It was only one of many I suggested to solve the issue at hand.
In the game of darts, even a blind man eventually hits the bulls-eye if they throw enough darts. Or if they aren't actually blind and are actually a dart hussler.

Quote
Also if you used NTFS over FAT32 you would have a better system and performance

And they could probably get better long distance service if they had listened to Deloris instead of hanging up on them. But that has absolutely nothing to do with the OP's issue.

Quote
This forum is nothing but a joke, trying to prove who's the biggest geek

Seriously, you really should take the advice of the ol' Contrex, and stop. The best part here is that your first reply threw a bunch of darts at the board, one of then hit it (the graphics card) some people (such as myself) agreed with this and then suddenly your trying to discuss the semantics of different file systems and inventing scenarios where having two different format drives can cause issues.


Quote
rather than helping out people with their problems.
Oh yes, of course.

Problem: Computer crashes during GPU intensive operations like games and Video card stress tests.

It's so obvious the problem is that they are using two different file systems on their drives. How could we all be so blind.

Quote
Freaken microsoft lovers with no virus scanners, thinking they are secure, lol.


oh. yes. it all makes sense now. we don't agree with your wild claims that file systems that have gotten along for years in all sorts of different configurations causes Graphics cards issues and now we're suddenly part of some global conspiracy that tries to hide the truth that FAT32+NTFS = Video card related crashes. Not sure where Virus scanners comes in. Guess that has nothing to do with anything.


I didn't say there's an issue with mixed format, for example one FAT32 and a NTFS drive, but if you end up putting the swap file on the other hard drive than the operating system, it has a fit swapping it across the two which can even become unstable.
Yes. that's Exactly what you said.

Quote
Mixed formated hard drives, like a FAT32 and a NTFS hard drive, it is best to make them all NTFS format, if your 'swap file' virtual memory is on the other hard drive from the Operating System it can cause crashing if the format is different.



Whatever the case, you've just proved Allan so right with your two completely off-topic and meaningless posts.



Quote from: Allan
and he gets upset when others call him on it.

So... Bravo. You've got everybody's attention now. Anything else you like to say? perhaps you'd like to make more off-topic and random quips about how you disagree with how we choose to configure our own computers. because, I think the Original Poster is So totally getting helped by such complaints.
Title: Re: A Challenging Crash?
Post by: Allan on March 27, 2010, 08:36:18 AM
BC - this is a 14 year old little boy who desperately wants to sound like he knows what he's talking about and then gets offended when others who DO know what they are talking about won't let him get away with posting nonsense. And like most children, rather than saying "Sorry, I was mistaken" he either tries to defend his (indefensible) position or resorts to attacking those who correct him. So if he chooses to stay here I guess all we can do is continue to point out his erroneous comments to the posters who come here for help and may not know better, and ignore the rest of his childish rants.
Title: Re: A Challenging Crash?
Post by: BC_Programmer on March 27, 2010, 09:02:16 AM
BC - this is a 14 year old little boy who desperately wants to sound like he knows what he's talking about and then gets offended when others who DO know what they are talking about won't let him get away with posting nonsense. And like most children, rather than saying "Sorry, I was mistaken" he either tries to defend his (indefensible) position or resorts to attacking those who correct him. So if he chooses to stay here I guess all we can do is continue to point out his erroneous comments to the posters who come here for help and may not know better, and ignore the rest of his childish rants.

But it's just so much FUN! And then he spazzes out and gives me SOOOO much more material to work with! Doesn't help the OP though to continue shooting fish in a barrel though.

birthday is 7-27-1994, so he's really 16, despite what his profile says.


Title: Re: A Challenging Crash?
Post by: Allan on March 27, 2010, 09:03:58 AM
But it's just so much FUN! And then he spazzes out and gives me SOOOO much more material to work with!
In that case, enjoy ;D
Title: Re: A Challenging Crash?
Post by: Salmon Trout on March 27, 2010, 09:09:43 AM
If he is from NZ, he sure puts the 'w' into Kiwi... (That's a joke I guess you have to be a Brit or an Aussie to understand...)
Title: Re: A Challenging Crash?
Post by: Azzaboi on March 27, 2010, 12:44:26 PM
Quote
And like most children, rather than saying "Sorry, I was mistaken"

I did say sorry where I was wrong in my previous post: "Sorry I called it a swap file rather than pagefile."

I believe the rest is correct, however badly written, but I said also in my previous posts - ignore it if it's not of value or you don't believe it is.

No where does it say Im 14, says 15 in my profile and yes Im 16 now. So what? You age-ist?

For someone that doesn't know there stuff, I still get thanked by others who have said it worked for them. I do website design, some programming, hacking, tweaking, computer performance, computer troubleshooting, and am a supermod even since I was 13. I also have a photograph memory. Other talents include playing the electric guitar, skateboarding, surfing, karate, and dance. Have a part-time job along with school, applying for a tv series. Big woopee, I don't care for boosting, but since your writing a friggen novel about me.

What did you do at my age, pick your nose?

I don't get pissed off with people correcting me except for you Allan and your unnessary back talk along with it. Thats the only thing that got me started. And what's with the racist joke Trout Man?

ps. congratz on hi-jacking the topic, the person with the problem still has the problem, no help with that...
Title: Re: A Challenging Crash?
Post by: CBMatt on March 28, 2010, 07:28:34 AM
That's one of the funniest things I've read all week.  You're adorable.