[SOLVED] Random crashes on new ASUS computer - WHEA detects UNCORRECTABLE_ERROR (124) in GenuineIntel.sys. FIX: no fix, I received a refund.

Sylveon

Member
Joined
Dec 23, 2022
Posts
24
  • A brief description of your problem (but you can also include the steps you tried): My new computer randomly freezes or crashes once or twice a day. I have tried everything under the sun to track down the cause - I googled very aggressively, asked two of my friends who know more about computers to help, followed tons of advice online like turning off fast boot etc. Uninstalling Avast seems to have fixed a freezing issue, and reinstalling my graphic drivers fixed the one reproducible version of this where Ctrl+Shift+Windows+B would instantly blue screen of death my computer. But it still crashed twice today. The crash is either: An instant, automatic black screen reboot (no blue screen), or a weird glitched screen that freezes and I have to hard reboot it by holding down the power key. This seems to happen mostly when I'm watching videos or the computer is idle, I was able to play resource heavy games like Victoria 3 and Elden Ring with no crash. Some of the crashes trigger a WHEA error dump, but only four of them have done so, and I've had a lot more than those four crashes. These are boot hardware errors in GenuineIntel.sys, but I don't know enough about computers to understand much more than that. I'm starting to worry I just got a defective computer, and I'm considering trying to get a replacement or invoke the warranty, but I'm not sure if it is truly a hardware issue, hoping someone here can diagnose it. Thanks in advance! Edit: Oh and I've also tried sfc /scannow, windows memory diagnostic, and intel processor diagnostic tool, but none found anything wrong, and ran all Windows Updates. If it matters, the WHEA logs seem to all be from after installing Windows version 22H2, not sure if that's because the service pack contributed to the problem or if it instead just improved Windows' ability to log it.
  • System Manufacturer? Asus
  • Laptop or Desktop? Laptop
  • Exact model number (if laptop, check label on bottom): N7600P is what the laptop has printed on it. MyAsus is telling me it's X7600PCB, though.
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Windows 11
  • x86 (32bit) or x64 (64bit)? 64
  • (Only for Vista, Windows 7) Service pack? N/A, not Vista or 7
  • What was original installed OS on system? Windows 11
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM version
  • Age of system? (hardware) Less than a month.
  • Age of OS installation? I believe 12/7.
  • Have you re-installed the OS? No
  • CPU: Intel Core i7 11th Gen
  • RAM (brand, EXACT model, what slots are you using?): 32GB, no clue how to find brand/model info
  • Video Card - NVIDIA GeForce RTX 3050 Laptop GPU
  • MotherBoard - (if NOT a laptop: Laptop
  • Power Supply - brand & wattage (if laptop, skip this one): Laptop
  • Is driver verifier enabled or disabled?: Disabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth): Default windows antivirus, Malwarebytes. I tried using Avast but it was freezing my computer, so uninstalled it.
  • Are you using proxy, vpn, ipfilters or similar software? I did install peerblock. Was not using it when any of the crashes occured, to my knowledge. Otherwise, no.
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software): No
  • Are you currently under/overclocking? Are there overclocking software installed on your system?: Not overclocking as far as I am aware. I did set my maximum CPU to 99% in power options as one of the many steps to try to fix the issue, if that matters. It didn't seem to help.

Speccy: http://speccy.piriform.com/results/Hqu8AbAzpxplacxI2T6N37B
SysnativeBSODCollection app results attached. I had to kill the process due to infinite "waiting for system info" like the instructions say, so I zipped it manually, hopefully it still works.

Also see below for the results of my WHEA error:

Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffff9c8b1577c020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1983

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2495

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 1

    Key  : Analysis.Init.CPU.mSec
    Value: 3811

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2190653

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 143

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x2f3d1880

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  WHEA-20221223-1450.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 7

BUGCHECK_P2: ffff9c8b1577c020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  smss.exe

STACK_TEXT:
ffffb00f`2f3d1830 fffff801`72bff487     : ffff9c8b`1577c000 00000000`00000000 ffff9c8b`1577c020 0000007f`ba6ff848 : nt!LkmdTelCreateReport+0x1d4
ffffb00f`2f3d1d70 fffff801`72bff37e     : ffff9c8b`1577c000 ffffb00f`2f3d2460 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
ffffb00f`2f3d1db0 fffff801`72a72e65     : 00000000`00000001 ffffb00f`2f3d2460 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
ffffb00f`2f3d1de0 fffff801`7298d4a2     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`77aa7cfc : nt!WheaCrashDumpInitializationComplete+0x59
ffffb00f`2f3d1e10 fffff801`7263d4e5     : ffff9c8b`2e114080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x9c2
ffffb00f`2f3d23e0 00007ffe`d4bb2514     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007f`ba6ff7e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`d4bb2514


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

Followup:     MachineOwner
---------
 

Attachments

Last edited:
Hi,

I only see one 0x50 crash dump and no records of any other crash in the logs.

Could you try to run the sysnative log collector again, if it hangs on the systeminfo again then just reboot and run the collector again.
 
Hi,

I only see one 0x50 crash dump and no records of any other crash in the logs.

Could you try to run the sysnative log collector again, if it hangs on the systeminfo again then just reboot and run the collector again.
Did as instructed, this time it ran successfully after a reboot, but I still don't see the WHEA dumps in there, so attaching the five of them I have as a second file. (crashed again today)
 

Attachments

Did as instructed, this time it ran successfully after a reboot, but I still don't see the WHEA dumps in there, so attaching the five of them I have as a second file. (crashed again today)
Oh and I should probably add, today's crash happened when I quit out of Elden Ring, but not reproducible, every other time I've quit out of Elden Ring the computer didn't crash.

This time the crash was of the "weird glitched screen" variety except it did crash instead of me manually having to reboot it.
 
Ah I see now; it's treated as a live kernel event where the problem doesn't cause the system to crash. The typical log data to be expected with a BSOD crash is a bit different with a live kernel event.

Anyways, the WHEA_ERROR_RECORD_HEADER_FLAGS where PreviousError has the value 0x1 (i.e. it is set) indicates the error is from a previous session. If you don't have a problem with it, I would like to try something here. We can't do a lot of hardware testing here without voiding any warranty, so I suggest we take a slightly different approach to determine whether this is truly hardware or a software problem which we can do by hunting for bad drivers. This will take more time because we are going to need the system to crash many times, which may expose either a hardware problem or the root cause. Once either is confirmed, you can either use the warranty to have the problem fixed or walk away with a stable laptop again. If this is not a problem for you, please follow the instructions in this link -> Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8. If you have any questions, please let me know before performing the instructions.
Code:
2: kd> dt _WHEA_ERROR_RECORD  ffffd206`b636c020
win32k!_WHEA_ERROR_RECORD
   +0x000 Header           : _WHEA_ERROR_RECORD_HEADER
   +0x080 SectionDescriptor : [1] _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
2: kd> dx -id 0,0,ffffd206cee49040 -r1 (*((win32k!_WHEA_ERROR_RECORD_HEADER *)0xffffd206b636c020))
(*((win32k!_WHEA_ERROR_RECORD_HEADER *)0xffffd206b636c020))                 [Type: _WHEA_ERROR_RECORD_HEADER]
    [+0x000] Signature        : 0x52455043 [Type: unsigned long]
    [+0x004] Revision         [Type: _WHEA_REVISION]
    [+0x006] SignatureEnd     : 0xffffffff [Type: unsigned long]
    [+0x00a] SectionCount     : 0x2 [Type: unsigned short]
    [+0x00c] Severity         : WheaErrSevFatal (1) [Type: _WHEA_ERROR_SEVERITY]
    [+0x010] ValidBits        [Type: _WHEA_ERROR_RECORD_HEADER_VALIDBITS]
    [+0x014] Length           : 0x6c60 [Type: unsigned long]
    [+0x018] Timestamp        [Type: _WHEA_TIMESTAMP]
    [+0x020] PlatformId       : {00000000-0000-0000-0000-000000000000} [Type: _GUID]
    [+0x030] PartitionId      : {00000000-0000-0000-0000-000000000000} [Type: _GUID]
    [+0x040] CreatorId        : {CF07C4BD-B789-4E18-B3C4-1F732CB57131} [Type: _GUID]
    [+0x050] NotifyType       : {3D61A466-AB40-409A-A698-F362D464B38F} [Type: _GUID]
    [+0x060] RecordId         : 0x1d9161cf3ce8a35 [Type: unsigned __int64]
    [+0x068] Flags            [Type: _WHEA_ERROR_RECORD_HEADER_FLAGS]
    [+0x06c] PersistenceInfo  [Type: _WHEA_PERSISTENCE_INFO]
    [+0x074] OsBuildNumber    : 0x0 [Type: unsigned long]
    [+0x078] Reserved2        [Type: unsigned char [8]]
    [+0x074] Reserved         [Type: unsigned char [12]]
2: kd> dx -r1 (*((win32k!_WHEA_ERROR_RECORD_HEADER_FLAGS *)0xffffd206b636c088))
(*((win32k!_WHEA_ERROR_RECORD_HEADER_FLAGS *)0xffffd206b636c088))                 [Type: _WHEA_ERROR_RECORD_HEADER_FLAGS]
    [+0x000 ( 0: 0)] Recovered        : 0x0 [Type: unsigned long]
    [+0x000 ( 1: 1)] PreviousError    : 0x1 [Type: unsigned long]
    [+0x000 ( 2: 2)] Simulated        : 0x0 [Type: unsigned long]
    [+0x000 ( 3: 3)] DeviceDriver     : 0x0 [Type: unsigned long]
    [+0x000 ( 4: 4)] CriticalEvent    : 0x0 [Type: unsigned long]
    [+0x000 ( 5: 5)] PersistPfn       : 0x0 [Type: unsigned long]
    [+0x000 ( 6: 6)] SectionsTruncated : 0x0 [Type: unsigned long]
    [+0x000 ( 7: 7)] RecoveryInProgress : 0x0 [Type: unsigned long]
    [+0x000 ( 8: 8)] Throttle         : 0x0 [Type: unsigned long]
    [+0x000 (31: 9)] Reserved         : 0x0 [Type: unsigned long]


2: kd> !dpx
Start memory scan  : 0xfffffc0be7db1830 ($csp)
End memory scan    : 0xfffffc0be7db3000 (Kernel Stack Base)

0xfffffc0be7db1958 : 0x000000007ffe0301 : SharedUserData+0x301
0xfffffc0be7db1978 : 0xfffff80113265fe8 : nt!LkmdTelCreateReport+0x1d4
0xfffffc0be7db1d58 : 0xfffff80112ecaacd : nt!SePrivilegeCheck+0x2d
0xfffffc0be7db1d60 : 0xfffff8011342a460 : nt!WheapLiveDumpRecordList
0xfffffc0be7db1d68 : 0xfffff801131ff487 : nt!WheapReportLiveDump+0x7b
0xfffffc0be7db1da8 : 0xfffff801131ff37e : nt!WheapReportDeferredLiveDumps+0x7a
0xfffffc0be7db1db8 : 0xfffffc0be7db2460 :  !du "file.sys"
0xfffffc0be7db1dd8 : 0xfffff80113072e65 : nt!WheaCrashDumpInitializationComplete+0x59
0xfffffc0be7db1de8 : 0xfffffc0be7db2460 :  !du "file.sys"
0xfffffc0be7db1e08 : 0xfffff80112f8d4a2 : nt!NtSetSystemInformation+0x9c2
0xfffffc0be7db1e28 : 0xfffff80118897cfc : Ntfs!NtfsExtendedCompleteRequestInternal+0x1cc
0xfffffc0be7db1e58 : 0xfffff80112b44bed : nt!ExAllocatePoolEx+0xd
0xfffffc0be7db1e68 : 0xfffff801188979f8 : Ntfs!NtfsInitializeIrpContextInternal+0x208
0xfffffc0be7db1eb8 : 0xfffff80118969168 : Ntfs!NtfsFsdClose+0x728
0xfffffc0be7db1ee8 : 0xfffffc0be7db2248 : 0xfffff80112acb433 : nt!ObfDereferenceObjectWithTag+0xc3
0xfffffc0be7db1fd8 : 0xfffff80112578e21 : FLTMGR!FltpPassThroughInternal+0xd1
0xfffffc0be7db2038 : 0xfffff80112ad0d99 : nt!RtlpHpFreeHeap+0x159
0xfffffc0be7db20b0 : 0xfffff80112800000 : "nt!PopCheckpointSystemSleepVariable <PERF> (nt+0x0)"
0xfffffc0be7db20d8 : 0xfffff8011329d1b0 : nt!ExFreePoolWithTag+0x1a0
0xfffffc0be7db2128 : 0xfffff80112acb975 : nt!IofCallDriver+0x55
0xfffffc0be7db2160 : 0xfffff8011346aac0 : nt!PspSystemQuotaBlock
0xfffffc0be7db2168 : 0xfffff80112ec57bb : nt!ObpFreeObject+0x1ab
0xfffffc0be7db21e8 : 0xfffff80112ec55b6 : nt!ObpRemoveObjectRoutine+0x86
0xfffffc0be7db2248 : 0xfffff80112acb433 : nt!ObfDereferenceObjectWithTag+0xc3
0xfffffc0be7db2288 : 0xfffff80112ec1ed7 : nt!ObpCloseHandle+0x2f7
0xfffffc0be7db22d8 : 0xfffff80112fa1293 : nt!NtReadFile+0xd3
0xfffffc0be7db23b8 : 0x000000007ffe03b0 : SharedUserData+0x3b0
0xfffffc0be7db23d8 : 0xfffff80112c3d4e5 : nt!KiSystemServiceCopyEnd+0x25
0xfffffc0be7db23e0 : 0xffffd70adc782080 :  Trap @ fffffc0be7db23e0
0xfffffc0be7db2438 : 0x5555555555555555 :  !da "UUUUUUUU"
0xfffffc0be7db2460 : 0x0065006c00690066 :  !du "file.sys"
 
F8 wasn't working so I set bcdedit /set {default} bootmenupolicy legacy before doing so, tested and that fixed F8. I created a restore point and verifier is now running. So just leave my computer running normally for the next 24 hours and post if it crashes? Anything I should do beyond that?
 
Last edited:
Use your computer like you normally would while driver verifier is running. Note that you may notice performance impact, how much depends on what you do.

If there hasn't been any crash in 24h, keep it running for another 24h. If there still hasn't been a crash after another 24h then let me know.
 
Use your computer like you normally would while driver verifier is running. Note that you may notice performance impact, how much depends on what you do.

If there hasn't been any crash in 24h, keep it running for another 24h. If there still hasn't been a crash after another 24h then let me know.
Well past the 24 hour mark, still no crash. Of course it doesn't crash when I need it it to... Can I safely turn off verifier at the 48 hour mark if it still hasn't crashed?

Only noticeable difference is my computer runs a bit more slowly and Elden Ring seems more prone to crash.

Hm. And I guess Asus's inbuilt screensaver doesn't seem to be triggering, when I left it on overnight and came back it hadn't triggered the screensaver, even though I checked and the setting was turned on (I assume because verifier is keeping the computer busy?).
 
Hi!

Speccy shows both Defender and mbam are enabled: is this correct?

Mcafee-security processes are present.
Did you try also some McAfee product?
Or was it preinstalled?

After the verifier procedure has been completed, I'd try to remove all of them.

Maybe a scan for Avast, McAfee and malwarebytes remnants with Revo uninstaller FREE could be a good idea...

Then just use Windows in-built firewall and antivirus, at least until the problem is present.
 
Use your computer like you normally would while driver verifier is running. Note that you may notice performance impact, how much depends on what you do.

If there hasn't been any crash in 24h, keep it running for another 24h. If there still hasn't been a crash after another 24h then let me know.
It still hadn't crashed after 48 hours so I ran the verifier /reset and rebooted.

I'm not sure why running Driver Verifier PREVENTED my computer from crashing when the whole point was for it to cause a crash??? Bizarre, let me know if that tells us anything though
I'll get started on Xilolee's steps next
 
Hi!

Speccy shows both Defender and mbam are enabled: is this correct?

Mcafee-security processes are present.
Did you try also some McAfee product?
Or was it preinstalled?

After the verifier procedure has been completed, I'd try to remove all of them.

Maybe a scan for Avast, McAfee and malwarebytes remnants with Revo uninstaller FREE could be a good idea...

Then just use Windows in-built firewall and antivirus, at least until the problem is present.
McAfee was preinstalled. And I thought I uninstalled it as one of the first things I did with my new computer? But apparently it didn't work.

I actually ran the McAfee Consumer Product Removal to uninstall it more properly before I started driver verify, since I found the fact that it was still in Speccy suspicious as well. My crash on Sunday happened after that, though, so not sure if it helped (but then it didn't crash for 48 hours with Driver Verifier, so maybe it did help???)

Trying to run Revo Uninstaller Free, how do I search for an app I don't have installed? It only lists applications that are installed, so I can't find McAfee or Avast, searching for them comes up empty, so I don't seem to have the option to remove their remnants. I could reinstall Avast/Mcafee and then run Revo to get rid of them again, if there's no other option, but you made it sound like I can scan for remnants somehow.

I see Avast also has a special removal tool? I might try that while I wait for a reply.

As for Malwarebytes, I only use it for the scanning features, and I only open it when I'm doing a scan. I don't think it was running during any of my crashes, either.

In theory, if the interface isn't lying to me, all the protection features should be disabled as I only have the free version. (edit: I tried including an image of the interface but it was broken? So I removed it, but it says I don't have premium protection) So I would think it wouldn't interfere with the antivirus. With all that said, do you still think it could be causing the crashes, and I should remove it?

Updated Speccy after running McAfee Consumer Product Removal tool: http://speccy.piriform.com/results/hoMacaNOX4Z3xt84jX5WM7d

Edit: Ran the Avast removal tool as well, new Speccy: http://speccy.piriform.com/results/S0EsY4U35j3txe7OKganb8b
 
Last edited:
It rarely happens that with driver verifier no crash occurs, but it does happen.
 
Driver Verifier doesn't cause the crash, what it does is subject the selected drivers to extra checks (the ones selected) whenever they are called. If the driver that's causing your crashes isn't loaded whilst Driver Verifier is running, then it won't be checked at all. It's important when running Driver Verifier to use all your features, apps, and devices as much as possible. You need to get the problem driver loaded so that Driver Verifier can trap it.
 
Not sure what you mean with driver verifier doesn't cause the crash, driver verifier can and does initiate a system crash when it notices something is wrong with what it is checking.
 
It rarely happens that with driver verifier no crash occurs, but it does happen.
So what does that mean for my computer? Is there anything else I can do to test if there's a driver issue before I move on with uninstalling Malwarebytes, or are we at a dead end if Driver Verifier prevents the error?

Also hopefully related, I discovered a lead while pouring over event logs that may be a clue to the black screen errors

"Display driver igfxn stopped responding and has successfully recovered."

This happens multiple times a day. Today my computer froze on a black screen, and I had to do a reboot by holding down the power key. When I looked in the log, sure enough, there was this error at the same time.

Then later that day it flickered twice, but successfully recovered, both times leaving the same log.

So I suspect what's happening is that this driver error sometimes freezes the computer so completely I have to hold down the power button, other times my computer recovers.

However, when I look over the logs, it did NOT trigger at all when I was running driver verifier. It triggered on 12/28, a few hours after turning off driver verifier, then before that the last trigger was 12/24. So I suspect this driver might be the issue? But for some reason Verifier prevented the error from occurring??

But when I open driver verifier to look at my complete list of drivers, I don't see a driver called igfxn, which I'm very confused about.

I'm not sure what to do with any of this information, but hopefully it's a clue.

If it's not a clue, let me know, and I'll proceed with the Malwarebytes uninstall plan.

Driver Verifier doesn't cause the crash, what it does is subject the selected drivers to extra checks (the ones selected) whenever they are called. If the driver that's causing your crashes isn't loaded whilst Driver Verifier is running, then it won't be checked at all. It's important when running Driver Verifier to use all your features, apps, and devices as much as possible. You need to get the problem driver loaded so that Driver Verifier can trap it.
I played Elden Ring for hours, left my computer idle overnight, streamed Youtube and Twitch for hours, did various miscellaneous internet things, did Discord calls, reset my display driver with the shortcut, and none of them triggered any crashes. When Driver Verifier has been off all of those things were things I was doing when the computer crashed.
 
Last edited:
So what does that mean for my computer? Is there anything else I can do to test if there's a driver issue before I move on with uninstalling Malwarebytes, or are we at a dead end if Driver Verifier prevents the error?

Also hopefully related, I discovered a lead while pouring over event logs that may be a clue to the black screen errors

"Display driver igfxn stopped responding and has successfully recovered."

This happens multiple times a day. Today my computer froze on a black screen, and I had to do a reboot by holding down the power key. When I looked in the log, sure enough, there was this error at the same time.

Then later that day it flickered twice, but successfully recovered, both times leaving the same log.

So I suspect what's happening is that this driver error sometimes freezes the computer so completely I have to hold down the power button, other times my computer recovers.

However, when I look over the logs, it did NOT trigger at all when I was running driver verifier. It triggered on 12/28, a few hours after turning off driver verifier, then before that the last trigger was 12/24. So I suspect this driver might be the issue? But for some reason Verifier prevented the error from occurring??

But when I open driver verifier to look at my complete list of drivers, I don't see a driver called igfxn, which I'm very confused about.

I'm not sure what to do with any of this information, but hopefully it's a clue.

If it's not a clue, let me know, and I'll proceed with the Malwarebytes uninstall plan.

Not sure if this is separate from or the same error as what's actually crashing my computer though, as I can't find any matches between WHEA and this warning, the warning seems to only occur in the log when my computer freezes irrecoverably, not when it actually crashes, making me even more confused
 
So I did find a reproducible way to force a BSOD
Device Manager->Intel Iris(R) Xe Graphics>Update Drivers
Then when I check the Driver Date after updating, it displays a date back in June for some inexplicable reason, despite the fact that that's older than my current updated driver.
After that, all I have to do is his hit Windows Key+Shift+Ctrl+B, instant BSOD, minidump attached

I can fix it by then rolling back the update, which inexplicably rolls it forward to the newer version I already have installed, resetting my computer, and on that new version it no longer crashes on that keyboard shortcut

Hm. I'm not sure what to make of this though. In theory, the bugged graphics driver should not be installed, but could it be causing the problem somehow anyway if there's something leftover? Since clearly Windows is trying to update to it when I used Device Manager update, so it must still be leftover on my computer somehow. If so is there a way to get rid of those leftovers? So bizarre on so many levels, not least the fact that windows thinks the old bugged graphic driver is newer

All this circumstantial evidence is really making me suspect my Intel graphics card or driver, but driver verifier came up empty, so.... Maybe my suspicions are wrong, hoping this data helps though
 

Attachments

Good catch!

I saw your speccy report shows a more recent version of your Intel graphics (Iris xe) drivers.

Did you install new drivers or was it Windows update?

If it was Windows update, you should block the automatic update for Intel graphics drivers.

Then you have three possible solutions:
1) go to device manager and choose the previous drivers version.
See if the problem persists; if yes, go to the next step.
2) go to Asus support webpage, for your laptop, and download the Intel graphics drivers.
Uninstall the current drivers version.
Install the just downloaded one.
See if the problem persists; if yes, go to the next step.
3) go to Intel website and download the newest drivers.
It should be: Intel® Graphics – Windows* DCH Drivers

Intel® Graphics – Windows* DCH Drivers

This download installs Intel® Graphics Driver 31.0.101.3790/31.0.101.2114 for Xe Dedicated, 6th-13th Gen Intel® Core™ Processor Graphics, and related Intel Atom®, Pentium®, and Celeron® processors. Driver version varies depending on the Intel Graphics in the system. View download options.
Version: 31.0.101.3790 and 31.0.101.2114
Date: 10/26/2022
 
Last edited:
Good catch!

I saw your speccy report shows a more recent version of your Intel graphics (Iris xe) drivers.

Did you install new drivers or was it Windows update?

If it was Windows update, you should block the automatic update for Intel graphics drivers.

Then you have three possible solutions:
1) go to device manager and choose the previous drivers version.
See if the problem persists; if yes, go to the next step.
2) go to Asus support webpage, for your laptop, and download the Intel graphics drivers.
Uninstall the current drivers version.
Install the just downloaded one.
See if the problem persists; if yes, go to the next step.
3) go to Intel website and download the newest drivers.
It should be: "Intel graphics - dch drivers".
So what I currently have is the Intel website one, which fixes the reproducible crash.

The update I did today is the manual update in Device Manager, which leads to the reproducible crash.

Hm. I'll try the Asus website one instead, and see if that leads to different results? That seems to be older than the intel one though, it came out in September
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top