Aces High Bulletin Board

General Forums => Hardware and Software => Topic started by: falcon23 on May 25, 2010, 06:24:43 PM

Title: Computer wouldnt start
Post by: falcon23 on May 25, 2010, 06:24:43 PM
OK..comp wouldnt boot...It did a problem repair and this is the list it came up with.And now the computer is working,but here is what it gave me earlier when I tried to start it about 6 times...and on the 6th time,it gave me the repair screen 5 times before that..nothing

 Problem signature01-6.1.7600.16385
 Problem signature02-Same number as above
 Problem signature03-unknown
 Problem signature04-75
 Problem signature05-AutoFailover
 Problem signature06-1
 Problem signature07-No root cause


                And now to the DXDIAG


------------------
System Information
------------------
Time of this report: 5/25/2010, 18:22:47
       Machine name: THETANK
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: EP35-DS3L
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz (2 CPUs), ~3.6GHz
             Memory: 4096MB RAM
Available OS Memory: 4094MB RAM
          Page File: 1167MB used, 7019MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: 120 DPI (125 percent)
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 32bit 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: ASUS EAH4850 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_025E1043&REV_00
     Display Memory: 2296 MB
   Dedicated Memory: 505 MB
      Shared Memory: 1791 MB
       Current Mode: 1280 x 1024 (32 bit) (60Hz)
       Monitor Name: Generic Non-PnP Monitor
      Monitor Model: unknown
         Monitor Id:
        Native Mode: unknown
        Output Type: DVI
        Driver Name: atiu9p64 aticfx64 aticfx64 atiu9pag aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Driver File Version:  ()
     Driver Version: 8.690.0.0
        DDI Version: 10.1
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: , 0 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71EE2-D702-11CF-3864-5F22A1C2C535}
          Vendor ID: 0x1002
          Device ID: 0x9442
          SubSys ID: 0x025E1043
        Revision ID: 0x0000
 Driver Strong Name: oem7.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_RV7X:8.690.0.0:pci\ven_1002&dev_9442
     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_BOBVerticalSt retch
                     {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_BOBVerticalSt retch
                     {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_BOBVerticalSt retch
                     {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 (Creative SB X-Fi)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 6/4/2009 03:49:08, 684312 bytes
            Other Files:
        Driver Provider: Creative
         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: SPDIF Out (Creative SB X-Fi)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 6/4/2009 03:49:08, 684312 bytes
            Other Files:
        Driver Provider: Creative
         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:  (Creative SB X-Fi)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 03:49:08, 684312 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

            Description: Auxiliary (Creative SB X-Fi)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 03:49:08, 684312 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

            Description: Line-In (Creative SB X-Fi)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: ctaud2k.sys
         Driver Version: 6.00.0001.1373 (English)
      Driver Attributes: Final Retail
          Date and Size: 6/4/2009 03:49:08, 684312 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF


                       Thanks
Title: Re: Computer wouldnt start
Post by: Getback on May 25, 2010, 08:00:23 PM
Welp, I don't know. However, if it is up and running do a mem test.

Maybe do a <gulp> a complete restore. I noticed you changed to windows 7. Did you update the drivers? Do you need to update the bios?

Title: Re: Computer wouldnt start
Post by: Chalenge on May 26, 2010, 12:26:50 AM
Find a driver for your monitor also.
Title: Re: Computer wouldnt start
Post by: MrRiplEy[H] on May 26, 2010, 10:07:56 AM
Always disable any overclocks as the first thing if problems come. Sometimes the system will remain stable for months, then just start to die little by little forcing you to lower the clocks or up voltages.
Title: Re: Computer wouldnt start
Post by: humble on May 27, 2010, 12:40:01 PM
This is a windows 7 issue tied to use of OEM vs retail. It's detecting a different MB then the original installation (or thinks it is)...
Title: Re: Computer wouldnt start
Post by: falcon23 on May 27, 2010, 06:06:24 PM
OC's are gone..not sure what you mean humble..I bought the 3 pack upgrade family disc this was last christmas..
Title: Re: Computer wouldnt start
Post by: Chalenge on May 27, 2010, 06:20:46 PM
You have (I believe) a driver that is hanging upon loading. Probably you updated a video driver without cleaning previous drivers and there is an incompatibility. In any case you really need to get the monitor driver loaded and stop using that generic device driver.
Title: Re: Computer wouldnt start
Post by: gyrene81 on May 27, 2010, 06:33:56 PM
In any case you really need to get the monitor driver loaded and stop using that generic device driver.
Why, is there special instance when the base plugnplay monitor driver would cause a problem? Getting just a monitor driver without the extra b.s. software is not that easy, especially when dealing with companies like Acer, HannsG, Hyundai, etc...
Title: Re: Computer wouldnt start
Post by: falcon23 on May 27, 2010, 06:44:29 PM
The reason why i have yet to get the driver for the monitor,is because I noticed when I did that last time..my refresh was stuck at 60 instead of 75..
Title: Re: Computer wouldnt start
Post by: Chalenge on May 27, 2010, 07:00:27 PM
Why, is there special instance when the base plugnplay monitor driver would cause a problem? Getting just a monitor driver without the extra b.s. software is not that easy, especially when dealing with companies like Acer, HannsG, Hyundai, etc...

Using generic drivers with Windows 7 may be alright (I wouldnt do it) but there could very well be a problem trying to use them with AH since it is not identifying proper refresh rates and could cause real issues which we have seen in the Technical Support forum.
Title: Re: Computer wouldnt start
Post by: gyrene81 on May 27, 2010, 07:22:51 PM
Using generic drivers with Windows 7 may be alright (I wouldnt do it) but there could very well be a problem trying to use them with AH since it is not identifying proper refresh rates and could cause real issues which we have seen in the Technical Support forum.
I was under the impression that AH read the settings based on what the user set...similar to how dxdiag reads it.

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100216-1514)
Current Mode: 1440 x 900 (32 bit) (60Hz)
Monitor: Plug and Play Monitor

Color settings could be an issue but if refresh rate can be set in Windows and detected at all, it shouldn't cause an issue. But, ya never know, it could happen.
Title: Re: Computer wouldnt start
Post by: Reschke on May 27, 2010, 07:43:06 PM
I was under the impression that AH read the settings based on what the user set...similar to how dxdiag reads it.

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100216-1514)
Current Mode: 1440 x 900 (32 bit) (60Hz)
Monitor: Plug and Play Monitor

Color settings could be an issue but if refresh rate can be set in Windows and detected at all, it shouldn't cause an issue. But, ya never know, it could happen.

That would be a negative answer there ghostrider. Win7 has taught me that it does not like generic display drivers for monitors. I updated mine because one of the problems I was having with my system was the monitor was creating an issue with the video card drivers and forcing the higher refresh rate which caused other little problems. Trust me you can live with the 60Hz refresh and the 59-60fps in a game. Anyone that says they can tell a difference in anything higher than that is lying through their teeth.
Title: Re: Computer wouldnt start
Post by: BaldEagl on May 27, 2010, 10:44:57 PM
Just google "Problem signature01-6.1.7600.16385".  I did and there's a number of things that may have caused this.

It sounds like after the first repair it should have booted after displaying the error/repair screen for the second time.