Page 21 of 30 FirstFirst ... 11 19 20 21 22 23 ... LastLast
Results 201 to 210 of 300
  1. #201
    Moderator Array
    Join Date
    Apr 2019
    Reputation
    66
    Posts
    1,706

    Hi Dodgexander,
    We are testing with similar GPU, but our tech team would like to know if the issue still occurs without GPU riser cable.
    Please share me the result if it is possible.
    Thank you.
    Last edited by STARRAIN@ROG; 08-03-2022 at 01:54 AM.

  2. #202
    New ROGer Array
    Join Date
    May 2022
    Reputation
    11
    Posts
    36

    Quote Originally Posted by STARRAIN@ROG View Post
    Hi Dodgexander,
    We are testing with similar GPU, but our tech team would like to know if the issue still occurs without GPU riser cable.
    Please share me the result if it is possible.
    Thank you.
    Ok today I dissembled my system and ran some tests. For the tests I used the linkup PCIe x4 riser cable that comes with my case and all with PCIe Native Power Management Enabled. I also used my RTX 2080 which is a PCIe x3 card and my Wifes RX 6750XT which is PCIe x4.

    First, I installed my RTX 2080 directly into the motherboard slot. Result was no WHEA errors.
    Second, I installed my Wifes RX 6750XT with the Linkup PCIe x4 riser cable. Result was lots of WHEA errors.

    Conclusion = The issue is definitely related to using a riser cable, and it does not make a difference whether a PCIe x3 or PCIe x4 riser cable is being used. From previous testing, it also does not matter using a different PCIe x3 riser cable.

    The only thing left I can think is to try a different manufacturer PCIe riser cable, but it's pointless because most riser cables are not double reverse and do not fit my case.

    I do not know what to do since my system was designed with small form factor in mind. I have an ITX motherboard and ITX case and I cannot install the graphics card directly. At least disabling PCIe Power management stops WHEA but it's not a solution as it degrades performance and uses more power.

  3. #203
    Moderator Array
    Join Date
    Apr 2019
    Reputation
    66
    Posts
    1,706

    Hi Dodgexander,
    Thank you for your reply.
    If there is any update form our tech team, I'll keep you updated.

  4. #204
    Moderator Array
    Join Date
    Apr 2019
    Reputation
    66
    Posts
    1,706

    Hi Dodgexander,
    Most likely the whea 17 errors are related to your riser cable. May I have the specific model name, photo and purchase link of your riser cable?
    Could you please refer to the following link to select all whea 17 events in your system to save log file and provide the file to us?
    https://drive.google.com/file/d/1dDT...ew?usp=sharing
    Thank you.

  5. #205
    New ROGer Array
    Join Date
    May 2022
    Reputation
    11
    Posts
    36

    Quote Originally Posted by STARRAIN@ROG View Post
    Hi Dodgexander,
    Most likely the whea 17 errors are related to your riser cable. May I have the specific model name, photo and purchase link of your riser cable?
    Could you please refer to the following link to select all whea 17 events in your system to save log file and provide the file to us?
    https://drive.google.com/file/d/1dDT...ew?usp=sharing
    Thank you.
    I have tried three riser cables from Linkup. The first is the PCIe x4 Riser cable that comes with the meshilicious. The second a non-meshilicious x4 Riser cable, 3rd is the PCIe x3 Riser cable that comes with the meshilicious.
    The meshilcious cables are the double reverse cables are sold specially with the SSUPD Meshilicious Case, included with the case when you buy. Here's the URL for the case:
    https://www.ssupd.co/products/meshlicious
    You can also purchase them separately here:

    The 2nd cable is just straight and from linkup directly.

    I have also been in touch with Linkup about the issue. This is their response:
    Looks like if you received a cable that the insertion loss on one or more of the channels ( total 16 ) exceeding the Gen 4 specifications. The total insertion loss is the summary on all components including CPU, CPU socket, motherboard PCB traces, PCIE slot, riser cable, GPU connector, GPU PCB traces, & GPU. The insertion loss is different from all components in all of their 16 channels. When Gen 4 system is designed, the riser isn't part of it. Therefore, one or more channels may have higher insertion loss to cause the issue. And the motherboard is the highest source of insertion loss. Unfortunately, this specific riser cable's worst channel happened to mate with the worst channel on the motherboard. Normally this can be resolved by exchanging another riser cable if the exceeded insertion loss isn't too much.

    Please exchange with SSUPD for a new Gen 4 riser cable. Your current one might have been a defective one. We are very sorry if this is the case. You should be able to get an exchange with SSUPD directly or through their dealer in your area/country.

    Alternatively, by changing a new motherboard will definitely resolve the issue.
    But I have already tried three riser cables, 2x Gen 4 and Gen 3. So, they are saying I need to try another? Somehow, I don't think this is going to fix the problem.

    The 2nd Linkup PCIe x4 riser cable in another machine is working fine with a Gigabyte X570 Elite board and a Radeon RX 6750XT. I decided to spend even more time testing, pulling apart systems and changing components for testing sake.

    Process of elimination is starting to only leave the Motherboard as the problem:

    Z690i + RTX 2080 + 1st Meshilicious Linkup PCIe x4 cable = WHEA spam
    Z690i + RTX 2080 + 2nd Linkup PCIe x4 cable (straight cable, from other system) = WHEA spam
    Z690i + RTX 2080 + 3rd Linkup PCIe x3 cable = WHEA spam
    Z690i + RTX 2080 no riser = No WHEA spam
    Z690i + RX6750 XT + 1st Meshilicious Linkup PCIe x4 cable = WHEA spam

    x570 + RTX 2080 + 1st Meshilicious Linkup PCIe x4 cable = No WHEA spam
    x570 + RTX 2080 + 2nd Linkup PCIe x4 cable (straight cable) = No WHEA spam
    x570 + RX6750 XT + 1st Meshilicious Linkup PCIe x4 cable = No WHEA spam.
    x570 + RX6750 XT + 2nd Meshilicious Linkup PCIe x4 cable = No WHEA spam.

    So, it seems like this is a specific issue with the Asus Z690i ROG motherboard when being used with a riser cable. Different cable, different GPU does not matter and the traces in the motherboard for the PCIe lanes are not strong enough to carry a signal also on to a riser cable.

    Only thing I have left is to try a different branded riser cable such as the aforementioned LianLi one, or to exchange motherboard. I'm leaning on just exchanging the motherboard because I've spent so much time on this now that I'm just not going to get back.

    Any suggestions? Log file is here: https://drive.google.com/file/d/1Rqd...ew?usp=sharing

  6. #206
    New ROGer Array
    Join Date
    May 2022
    Reputation
    11
    Posts
    36

    Today my screen blacked out and my system rebooted when playing World of Warcraft.
    I waited for it to do it's thing, it came back up so I could check event log.

    In the event log I saw three errors related to storage:
    Code:
    Log Name:      System
    Source:        disk
    Date:          8/7/2022 2:16:10 PM
    Event ID:      154
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Beastington
    Description:
    The IO operation at logical block address 0x195e6128 for Disk 0 (PDO name: \Device\00000050) failed due to a hardware error.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="49156">154</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2022-08-07T18:16:10.0090604Z" />
        <EventRecordID>4794821</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="9712" />
        <Channel>System</Channel>
        <Computer>Beastington</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk0\DR0</Data>
        <Data>0x195e6128</Data>
        <Data>0</Data>
        <Data>\Device\00000050</Data>
        <Binary>0F01180004004000000000009A0004C00000000000000000000000000000000000000000000000000002042AF00004000000000A000000004400000000002D2D</Binary>
      </EventData>
    </Event>
    
    Log Name:      System
    Source:        disk
    Date:          8/7/2022 2:15:59 PM
    Event ID:      154
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Beastington
    Description:
    The IO operation at logical block address 0xd489b8 for Disk 0 (PDO name: \Device\00000050) failed due to a hardware error.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="49156">154</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2022-08-07T18:15:59.6086588Z" />
        <EventRecordID>4794820</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="14332" />
        <Channel>System</Channel>
        <Computer>Beastington</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk0\DR0</Data>
        <Data>0xd489b8</Data>
        <Data>0</Data>
        <Data>\Device\00000050</Data>
        <Binary>0F01180004004000000000009A0004C00000000000000000000000000000000000000000000000000002042AF00004000000000A000000004400000000002D2D</Binary>
      </EventData>
    </Event>
    
    Log Name:      System
    Source:        disk
    Date:          8/7/2022 2:15:57 PM
    Event ID:      154
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Beastington
    Description:
    The IO operation at logical block address 0x1608d120 for Disk 0 (PDO name: \Device\00000050) failed due to a hardware error.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="49156">154</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2022-08-07T18:15:57.7531496Z" />
        <EventRecordID>4794819</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="26108" />
        <Channel>System</Channel>
        <Computer>Beastington</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk0\DR0</Data>
        <Data>0x1608d120</Data>
        <Data>0</Data>
        <Data>\Device\00000050</Data>
        <Binary>0F01180004004000000000009A0004C00000000000000000000000000000000000000000000000000002042AF00004000000000A000000004400000000002D2D</Binary>
      </EventData>
    </Event>
    This is with ASPM disabled in BIOS.

    So it seems like my system is also unstable with storage. Yet the storage I use is on the Compatibility list.

    When I put this system together I made sure everything was compatible to avoid these kinds of problems.

  7. #207
    Moderator Array
    Join Date
    Apr 2019
    Reputation
    66
    Posts
    1,706

    Hi Dodgexander,
    Is the X570 motherboard X570 AORUS ELITE (rev. 1.0)?
    Was it the first time screen blacked out and system rebooted when playing World of Warcraft?
    How long did you play World of Warcraft and its screen blacked out and system rebooted? Does it occur on the specific game settings or scenes?
    Does ASPM mean PCIE Native Power Management? Did you adjust other bios settings?
    For whea 17 with riser cable, have you tried set PCIE gen4 to gen3 in bios?
    Thank you.

  8. #208
    New ROGer Array
    Join Date
    May 2022
    Reputation
    11
    Posts
    36

    Quote Originally Posted by STARRAIN@ROG View Post
    Hi Dodgexander,
    Is the X570 motherboard X570 AORUS ELITE (rev. 1.0)?
    Yes.
    Quote Originally Posted by STARRAIN@ROG View Post
    Was it the first time screen blacked out and system rebooted when playing World of Warcraft?
    No, it's not the first time I see these storage errors either. It doesn't happen very often. Maybe 3 times since I've owned the board for 2 months.
    Quote Originally Posted by STARRAIN@ROG View Post
    How long did you play World of Warcraft and its screen blacked out and system rebooted?
    I just launched the game; it wasn't very long. I checked NVME SSD temp and it was 44c. I check drive for erros with smart software and chdisk, no errors. Good health.
    Quote Originally Posted by STARRAIN@ROG View Post
    Does it occur on the specific game settings or scenes?
    It doesn't happen often enough to know. I do not remember what happened last time it occured. Chances are last time it also happened when gaming with World of Warcraft.
    Quote Originally Posted by STARRAIN@ROG View Post
    Does ASPM mean PCIE Native Power Management?
    On the x570 board I own there is no PCIE Native Power Management option, only ASPM L01 and L00. I enabled both to test.
    Quote Originally Posted by STARRAIN@ROG View Post
    Did you adjust other bios settings?
    It's an existing system that I have had running stable for some time. It is overclocked but 100% stable. I took the same riser cable from that PC into my PC and suddenly there are problems with the Z690I. I took the riser cable from my PC into that PC and there's no problem.
    Quote Originally Posted by STARRAIN@ROG View Post
    For whea 17 with riser cable, have you tried set PCIE gen4 to gen3 in bios?
    Thank you.
    Yes, but it doesn't help. I tested with the RX 6750 XT and I still get the same problem (WHEA spam) which is a PCIe gen 4 GPU.

  9. #209
    Moderator Array
    Join Date
    Apr 2019
    Reputation
    66
    Posts
    1,706

    Hi Dodgexander,
    May I double confirm you got screen blacked out and system rebooted issues on the Z690I with bios all default settings except PCIE Native Power Management disabled?
    Or the issues occur when overclock?
    If the issues also occur when with bios all default settings except PCIE Native Power Management disabled, please see if it occur on the specific game settings or scenes in World of Warcraft.
    Thank you.

  10. #210
    New ROGer Array
    Join Date
    May 2022
    Reputation
    11
    Posts
    36

    Quote Originally Posted by STARRAIN@ROG View Post
    Hi Dodgexander,
    May I double confirm you got screen blacked out and system rebooted issues on the Z690I with bios all default settings except PCIE Native Power Management disabled?
    Or the issues occur when overclock?
    If the issues also occur when with bios all default settings except PCIE Native Power Management disabled, please see if it occur on the specific game settings or scenes in World of Warcraft.
    Thank you.
    All settings on my system are default apart from XMP memory and native power management disabled.
    This particular issue with the black screen, reboot and disk errors has happened 2-3 times in 2 months. It's not linked to a particular setting or moment in game and it's impossible to repeat deliberately.

    I can use the system again for a few weeks and then maybe get this error again.

    The system is not overclocked.

    The ram and SSD I am using is on your QVL.

    If no solution can be found I'll have to try and return the board to Amazon. It's a shame because I wanted to go with Asus and paid more than other ITX boards.

Page 21 of 30 FirstFirst ... 11 19 20 21 22 23 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •