BSOD crashing while running heavy downloading - new laptop setup

p64imp

New member
Local time
1:13 AM
Posts
11
Hi All,

Just got a Asus Zephyrus Duo 15 SE laptop and am working on pulling down some games. When i have several game download clients running, my laptop crashes almost right away.

I backed off and just have steam running now, but after several hours i find it still crashes. It tends to reboot ok, but the BSOD screen flashes so fast i can't see the error code.

Attached is my v2 crash dump zip.

I jumped in the event viewer but all i get is :
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

which is hardly helpful.

Can somebody review my v2 crash logs and let me know what may be happening here?

I am running:

Windows 11 Version 21H2 (OS build 22000.194)

Additional details:

Upon receiving the laptop, i upgraded the m.2 storage to two WD 850 2tb nvme drives. Initially i installed it in RAID0 config, but after several bsod's and issues booting (raid.sys errors) i pulled it out of raid and am now booting in ahci mode.

I also upgraded the ram module. It has a HMAB2GS6AMR6N-XN module soldered on-board and had a 16gb plug in module for a total of 32gb. I upgraded the 16gb module with a 32gb HyperX module (KHX3200C20S4/32GX). Though i did not check that this module is mobo supported, the manuf. states that you can upgrade to a max of 32gb additional memory for a 48gb max. I am not sure if my mobo supports this module, but have not found any site at all that can confirm.

My laptop MOBO/model is :

GX551QR-XB98​


Link to the purchase page of my laptop

I asked this question by mistake on the windows 10 board here and received one reply.

though i was requested to ask it over here.

I was asked:


Did the computer come with the BETA BIOS or was that installed recently?
(3503)

I did run some updates, but through the MyAsus app. I don't believe it had me install a beta bios update, nor would i think it would have through an official app.

Behavior i see when it crashes:
I am typically running several processes, then i get a flash of the black screen and it goes away before i can even see an error code.
At times when it attempts to reboot, the fans kick on max speed. One thing i noted once is when i hit bios during this the cpu registered 113 degrees Celcius which i am not sure is accurate, however after a fresh boot it registers 90c using coretemp, so maybe it is?

IDK if its related to heat, memory, bios, or ????

attached is my v2 dump. I am really hoping somebody can give me an idea what's going on here. I have until november 5th to return this if its un-solvable. I want to prove what the issue is before i hit that as apart from the crashing i LOVE this laptop and want it to work out.

Many thanks in advance.
 
Windows Build/Version
22000.194 version 21H2

Attachments

  • ASUSLAPTOP-(2021-10-08_22-26-56).zip
    283.5 KB · Views: 1

My Computer

System One

  • Operating System
    Windows 11

SlicEnDicE

Well-known member
Power User
VIP
Local time
11:13 AM
Posts
533
Location
Finland
Based on this information, your CPU temperatures are very high.
 

My Computers

System One System Two

  • Operating System
    Windows 11 Pro build 10.0.22478.1012 (Dev Channel)
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo A485
    CPU
    Ryzen 7 2700U Pro
    Motherboard
    Lenovo
    Memory
    32GB
    Graphics Card(s)
    iGPU Vega 10
    Sound Card
    Realtek
    Monitor(s) Displays
    14" FHD (built-in) + 14" Lenovo Thinkvision M14t (touch+pen) + 32" Asus PB328
    Screen Resolution
    FHD + FHD + 1440p
    Hard Drives
    Intel 660p m.2 nVME PCIe3.0 x2 512GB
    PSU
    65W
    Keyboard
    Thinkpad
    Mouse
    Logitech MX Master 2S
    Internet Speed
    400/100Mbit
    Browser
    Edge (Chromium)
    Antivirus
    Windows Defender
    Other Info
    SecureBoot: Enabled
    TPM2.0: Enabled
    AMD-V: Enabled
    VBS: Enabled
    HVCI: Enabled
  • Operating System
    Windows 10 Pro, Windows 11 Pro build 10.0.22000.282 (VHDX, OfflineInsiderEnrolled to RP) , Linux Mint 20
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom
    CPU
    i7-2600k @4.4GHz
    Motherboard
    Asus P8Z68-V PRO/GEN3
    Memory
    16GB 4x4GB 1600MHz CL9
    Graphics card(s)
    MSI GTX970 4GB
    Sound Card
    Soundblaster X-Fi
    Monitor(s) Displays
    32" 10-bit Asus PB328Q
    Screen Resolution
    WQHD 2560x1440
    PSU
    750W
    Case
    Fractal Design (something old)
    Cooling
    Noctua
    Mouse
    Logitech MX Master 2S
    Keyboard
    Logitech G710+
    Internet Speed
    400/100Mbit
    Browser
    Edge (Cromium)
    Antivirus
    Windows Defender

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
There was a BSOD but there no dump files to debug.

The BSOD bugcheck was 154.



If no hardware were added or modified on the new laptop then it's best to contact the manufacturer or vendor for Return Merchandise Authorization (RMA).



Run: Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.



Download and install one of these temperature monitoring software:

Speccy: Download Speccy | Find your computer specs, free!
HWMonitor: HWMONITOR | Softwares | CPUID
SpeedFan: Download SpeedFan - Access temperature sensor in your computer




If there are continued BSOD then check for stability / instability by

a) removing the mismatched RAM module and contact ASUS customer service for a list of supported RAM modules (already tested RAM for the motherboard).

b) removing any installed drives




Continue monitoring with reliability monitor:




Code:
Manufacturer : Hynix
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 16GB
Speed        : 3200
Serial       : 00000000
PartNumber   : HMAB2GS6AMR6N-XN


Code:
Manufacturer : Kingston
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 32GB
Speed        : 3200
Serial       : 8CAED5DD
PartNumber   : KHX3200C20S4/32GX




Code:
Event[1045]
  Log Name: System
  Source: volmgr
  Date: 2021-10-08T12:41:50.4860000Z
  Event ID: 161
  Task: N/A
  Level: N/A
  Opcode: N/A
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: ASUSLaptop
  Description:
Dump file creation failed due to error during dump creation. ?
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

p64imp

New member
Local time
1:13 AM
Posts
11
I havn't had an error since the evening i made this post which i think is a good sign.

Only issue i had was about 4 hours ago when rebooting, the system booted with a loud noise sounding like a gust of wind through the speakers, but once it hit the windows login screen it stopped. it lasted about 2 seconds, pause, then 5 seconds. (no it was not the fans, it was sound from the speakers clear, obvious, and quite loud at that.)

Quite odd, though after subsequent reboots it didnt happen again.

My main concern with odd behavior like that is, once it happens once, its likely to happen again, and more frequently as the pc ages...

I'm going to continue to monitor things as i have until 11/5 to return it if needed.

I greatly appreciate the replies though. Very thorough and detailed. I will be using these tools to monitor through the month. Hopefully the issues just go away.

i WAS hitting my pc quite hard downloading 3tb worth of game files as this is my new gaming laptop. That could have constituted the unusual behavior. It's not very good to push an ssd with such frequent disk access - heating can get the better of it. Its possible thats what was going on...

And an overheating issue ceasing write to the drive causing a BSOD could certainly be responsible for the failure to write a crash report...

in any event, i'm going to keep monitoring. Thanks again for the input!
 

My Computer

System One

  • Operating System
    Windows 11

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
When available please post tuneup results.

It will improve the likelihood that you notice BSOD by turning off automatic restart.

After any unexpected shutdown or restart > post a new V2
 

My Computer

System One

  • Operating System
    Windows 10

p64imp

New member
Local time
1:13 AM
Posts
11
Here is the results of my tuneup run. Please let me know what you see:

Started on Mon 10/11/2021 at 15:25:23.97

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Mon 10/11/2021 at 15:26:29.84

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.194

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on Mon 10/11/2021 at 15:27:18.76

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.194

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on Mon 10/11/2021 at 15:28:03.57

[ChkDsk /Scan]

The type of the file system is NTFS.
Volume label is OS.

Stage 1: Examining basic file system structure ...


609280 file records processed.

File verification completed.
Phase duration (File record verification): 2.49 seconds.


7288 large file records processed.

Phase duration (Orphan file record recovery): 2.60 milliseconds.


0 bad file records processed.

Phase duration (Bad file record checking): 0.03 milliseconds.

Stage 2: Examining file name linkage ...


3914 reparse records processed.



735416 index entries processed.

Index verification completed.
Phase duration (Index verification): 6.51 seconds.


3 unindexed files scanned.


Phase duration (Orphan reconnection): 1.20 seconds.
Found 3 missing entries (\Users\khenz\AppData\Local\Packages\Microsoft.ZuneVideo_8wekyb3d
8bbwe\AC\52264C4C-172F-41B9-91B8-7F0C3B1E9021_VEN_1002&DEV_1638&SUBSYS_11BC&REV_C7.lock
<0x6,0x89aa6>, ...) in index "$I30" of directory
"\Users\khenz\AppData\Local\Packages\Microsoft.ZuneVideo_8wekyb3d8bbwe\AC <0x3,0x71232>"
... repaired online.


0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 0.47 milliseconds.


3914 reparse records processed.

Phase duration (Reparse point and Object ID verification): 7.08 milliseconds.

Stage 3: Examining security descriptors ...
Found corrupt security descriptor entry at offset 0x3bb920 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
Found corrupt security descriptor entry at offset 0x3bba30 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
Found corrupt security descriptor entry at offset 0x3bbc80 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
Found corrupt security descriptor entry at offset 0x3bbd90 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
Found corrupt security descriptor entry at offset 0x380000 in \$Secure <0,0x9>:$SDS
... queued for offline repair.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 45.90 milliseconds.


63069 data files processed.

Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run "chkdsk /spotfix" to fix the issues.

1929227275 KB total disk space.
884426300 KB in 328781 files.
189328 KB in 63070 indexes.
0 KB in bad sectors.
741623 KB in use by the system.
65536 KB occupied by the log file.
1043870024 KB available on disk.

4096 bytes in each allocation unit.
482306818 total allocation units on disk.
260967506 allocation units available on disk.
Total duration: 10.28 seconds (10280 ms).

㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ †匠慴瑲摥漠潍〱ㄯ⼱〲ㄲ愠⁴㔱㈺㨸〲㤮‸਍ഠ䄊瑵副扥潯⁴†਍ഠ吊啒⁅†††ഠ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ †††嬠敓⁴畁潴敒潢瑯㴠䘠污敳⁝਍ഠ唊摰瑡湩⁧牰灯牥祴猨
景✠屜十单䅌呐偏剜住屔䥃噍㨲楗㍮弲协敒潣敶祲潃普杩牵瑡潩⹮慎敭∽楍牣獯景⁴楗摮睯⁳ㄱ倠潲䍼尺坜义佄南屼䑜癥捩履䡜牡摤獩に屜慐瑲瑩潩㍮✢഍倊潲数瑲⡹⥳甠摰瑡⁥畳捣獥晳汵മ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ䄊瑵副扥潯⁴†਍ഠ䘊䱁䕓†††ഠ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ䐊扥杵湉潦祔数†ഠ ਍‷††††††ഠ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍਍††††卛瑥䐠扥杵湉潦祔数㴠㜠൝ഊ唊摰瑡湩⁧牰灯牥祴猨
景✠屜十单䅌呐偏剜住屔䥃噍㨲楗㍮弲协敒潣敶祲潃普杩牵瑡潩⹮慎敭∽楍牣獯景⁴楗摮睯⁳ㄱ倠潲䍼尺坜义佄南屼䑜癥捩履䡜牡摤獩に屜慐瑲瑩潩㍮✢഍倊潲数瑲⡹⥳甠摰瑡⁥畳捣獥晳汵മ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ䐊扥杵湉潦祔数†ഠ ਍‷††††††ഠ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍਍††††坛䥍⁃慐敧楆敬氠獩嵴਍਍汁潬慣整䉤獡卥穩㵥ㄷ㠶਍畃牲湥啴慳敧ㄽ਍敄捳楲瑰潩㵮㩃灜条晥汩⹥祳൳䤊獮慴汬慄整㈽㈰〱㈷〹㌷ㄵ⸹㜷〱㠴㐭〲਍慎敭䌽尺慰敧楦敬献獹਍敐歡獕条㵥㤶਍瑓瑡獵ഽ吊浥偰条䙥汩㵥䅆卌൅ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍ഠ䄊瑵浯瑡捩慍慮敧偤条晥汩⁥†਍ഠ吊啒⁅††††††††††ഠ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍਍††††卛瑥䄠瑵浯瑡捩慍慮敧偤条晥汩⁥‽牔敵൝ഊ唊摰瑡湩⁧牰灯牥祴猨
景✠屜十单䅌呐偏剜住屔䥃噍㨲楗㍮弲潃灭瑵牥祓瑳浥丮浡㵥䄢啓䱓偁佔≐ധ਍牐灯牥祴猨
灵慤整猠捵散獳畦⹬഍㴊㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽ഽ ਍畁潴慭楴䵣湡条摥慐敧楦敬†ഠ ਍剔䕕†††††††††††਍ഠ㴊㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽ഽഊ †††嬠捂䕤楤⁴支畮扻摡敭潭祲嵽਍਍䅒⁍敄敦瑣൳ⴊⴭⴭⴭⴭⴭ਍摩湥楴楦牥†††††††扻摡敭潭祲ൽ ਍㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽㴽਍਍††楆楮桳摥漠潍〱ㄯ⼱〲ㄲ愠⁴㔱㈺㨸ㄲ㔮ഴ
 

Attachments

  • Tuneup.zip
    2.5 KB · Views: 1

My Computer

System One

  • Operating System
    Windows 11

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
Code:
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run "chkdsk /spotfix" to fix the issues.


Run the spotfix.

Overnight run: Chkdsk /b /v



C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)


Type: y



Run the chkdsk switches on all drives.



After completing chkdsk on all drives run Hard Disk Sentinel (free or trial version)

Post images or share links for the following tabs:

Overview
Temperature
SMART
Disk Performance
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

p64imp

New member
Local time
1:13 AM
Posts
11
All operations have been run. Took just over an hour to scan/repair my C:/D:.

Here are the screens from HD Sentinel:

1633997772795.png

1633997792863.png
1633997818089.png
1633997842521.png


Just a heads up, I have used HD Sentinel software for over 2 years (i'm a registered user). I noted that these WD SSD's never register health (i've run about 5-6 through this app and they never show up). This is typical for these guys unfortunately. Samsungs etc all show up, but not WD.
 

My Computer

System One

  • Operating System
    Windows 11

p64imp

New member
Local time
1:13 AM
Posts
11
Additionally, when i was running through the drivers to see if I couldn't get it to show up in HD Sentinel, i saw this:

1633998298965.png

this shows up for both drives. Info:

Device settings for SCSI\Disk&Ven_NVMe&Prod_WD_BLACK_SN850_2\5&49f9df6&0&000000 were not migrated from previous OS installation due to partial or ambiguous device match.

Last Device Instance Id: USBSTOR\Disk&Ven__USB&Prod__SanDisk_3.2Gen1&Rev_1.00\0101bd04ba9cbefbf6f223614355d587437b4bef050ac5b5190aa65eade9062
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF000FF00FFFFF130
Present: false
Status: 0xC0000719


What does this mean, and is it an issue?
 

My Computer

System One

  • Operating System
    Windows 11

p64imp

New member
Local time
1:13 AM
Posts
11
I just received another crash. I ran the v2 tool again and attached the log. Additionally, this is what i see when it crashes. After this it freezes up I'll provide pics in the next post.
 

Attachments

  • ASUSLAPTOP-(2021-10-11_18-06-26).zip
    839.6 KB · Views: 1

My Computer

System One

  • Operating System
    Windows 11

p64imp

New member
Local time
1:13 AM
Posts
11
Here are the crash images. You can see the artifacts in the screen and how it stopped before it could gather info for a crash log. One thing to note before this happened, i was just navigating in chrome, and noticed a couple screen black-outs, then after a minute i hit this.


20211011_180411.jpg20211011_180407.jpg
 

My Computer

System One

  • Operating System
    Windows 11

p64imp

New member
Local time
1:13 AM
Posts
11
If i get a replacement, would i be able to pull the ssd's and just plug them in to the other laptop and continue on? It would be the same exact hardware as the last one. I REALLY don't want to go through another full setup...

i know the drive would be bitlocker encrypted, so i would probably have to remove that first, anything else? Or would i need to start all over all over again?
 

My Computer

System One

  • Operating System
    Windows 11

p64imp

New member
Local time
1:13 AM
Posts
11
I'm guessing to make sure i'm totally out of the woods that i should just start new.

I'm going to start transferring the game data from this pc to a external hard drive so at least i dont have to re-download 3tb of game data again.

sigh this is such a pain. so so much work setting things up. This will be the 4th rebuild for me in 5 days.
 

My Computer

System One

  • Operating System
    Windows 11

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
Please make free backup images and / or clones and restore the image when you receive the new computer.

Also backup files using the "belt and suspenders" approach.


Search for: C:\WINDOWS\MEMORY.DMP
Save to the downloads folder > zip > post a share link into this thread




The posts below are the problems reported: BSOD and Livekernelreports

Both were related to the video software / hardware


The computer has dual graphics.
The livekernelreports displayed problems with the Nvidia GPU.


When the Memory dump is uploaded it can be debugged.




Code:
Event[4355]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2021-10-11T18:05:01.1760000Z
  Event ID: 1001
  Task: N/A
  Level: Error ?  Opcode: N/A
  Keyword: Classic  ?  User: N/A
  User Name: N/A
  Computer: ASUSLaptop
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000010e (0x0000000000000017, 0xffffb5070e258000, 0x0000000000000000, 0xffffffffc00002b6). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 508b4db1-755d-4cad-bec2-c4c55a907c24. ?



Code:
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000017, Unexpected system command failure.
Arg2: ffffb5070e258000
Arg3: 0000000000000000
Arg4: ffffffffc00002b6


Code:
10/12/2021 1:05 AM    Windows Error Reporting    Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 10e&#x000d;&#x000a;P2: 17&#x000d;&#x000a;P3: ffffb5070e258000&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: ffffffffc00002b6&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\101121-17015-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-18921-0.sysdata.xml&#x000d;&#x000a;\\?\C:\WINDOWS\MEMORY.DMP&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.206de312-6a51-44ba-a116-c4d66648e202.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0bc35862-94cc-4d4e-a9b9-c9251409a3af.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c3d77ccf-1b88-44fe-b6b0-2dda6701e463.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.87335df2-ef42-4cff-aaf3-7788145d877e.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_10e_aa31ea274fd8d531d066d3e55be2e1d9c24620_00000000_cab_792f1f35-ecaa-4ce1-90d5-bb7a52b13195&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 508b4db1-755d-4cad-bec2-c4c55a907c24&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0


Code:
10/12/2021 1:06 AM    Windows Error Reporting    Fault bucket 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge, type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 8731ca0c-4547-4542-9361-85eb12fede8e&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 10e&#x000d;&#x000a;P2: 17&#x000d;&#x000a;P3: ffffb5070e258000&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: ffffffffc00002b6&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\101121-17015-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-18921-0.sysdata.xml&#x000d;&#x000a;\\?\C:\WINDOWS\MEMORY.DMP&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.206de312-6a51-44ba-a116-c4d66648e202.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0bc35862-94cc-4d4e-a9b9-c9251409a3af.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c3d77ccf-1b88-44fe-b6b0-2dda6701e463.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.87335df2-ef42-4cff-aaf3-7788145d877e.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_10e_aa31ea274fd8d531d066d3e55be2e1d9c24620_00000000_cab_792f1f35-ecaa-4ce1-90d5-bb7a52b13195&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 508b4db1-755d-4cad-bec2-c4c55a907c24&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0



Code:
10/12/2021 1:00 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0525eb94-3c8c-4190-a4fa-7eaad9943e74&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffffb5070e063010&#x000d;&#x000a;P3: fffff806253ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211011-1800.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-3046921-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.dbcc7090-8b47-46bb-8f6b-d7640f9af86a.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bfe823fe-7f9d-4b17-9d28-4213aa8d909f.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.583853ba-4f97-439a-a776-b313f28a6e35.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ca02fee5-e2fe-4f88-bd1e-cbc60a983736.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.75e54a98-cfb5-4d4a-b862-341cf4495b98.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_1541712439b555272512c5ee9b601f4340609b_00000000_cab_f575fff3-3997-4aa8-9259-162327d4d659&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: f575fff3-3997-4aa8-9259-162327d4d659&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/9/2021 5:43 PM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 1f50086a-72d5-4bfc-a98e-7b52cd6ef07b&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffff9b8f9610e010&#x000d;&#x000a;P3: fffff8044b0ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211009-1042.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-2148390-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d364c036-7adf-454d-9d08-533034b187ed.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.15b37008-8988-4581-9ac5-fbd813b2298c.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_32add5943db4ccd05bcd875675eaa5fc74d99ede_00000000_cab_22189a07-3072-48be-90ee-35d158404c85\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20210915_1 EC_0_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8252e0f5-8915-47be-9187-34dab9f301d2.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_32add5943db4ccd05bcd875675eaa5fc74d99ede_00000000_cab_22189a07-3072-48be-90ee-35d158404c85\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d6f2e4e2-f16c-4bc8-9329-abbe8c77f3e1.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.de3f3e7f-96e2-41a1-ba54-638e4fe0a877.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e3a1430-c450-4d0d-bfc5-01fa8cf0d40d.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.e1371b89-7dc5-42fb-b842-c00afdf573c9.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_32add5943db4ccd05bcd875675eaa5fc74d99ede_00000000_cab_22189a07-3072-48be-90ee-35d158404c85&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 22189a07-3072-48be-90ee-35d158404c85&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/12/2021 1:02 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 290f3fe5-01a3-41e2-a2f7-11576016646e&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffffb506fb884050&#x000d;&#x000a;P3: fffff806253ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211011-1802.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-3186500-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c97a6077-4d05-4376-a9ae-55f18022d170.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ab14b5f9-8d5e-4b35-88cf-26831ca398bf.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d2a2ad19-4c18-4b5c-b422-33c758a12db5.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e22fa042-9b11-4f7f-8a91-b776023b014d.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.73a49e4d-dec3-48f5-bff7-520a559aec9f.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_baed0342822278a83cac9cfaa4afe7c14fd3645_00000000_cab_f9375a60-5342-4234-b354-f6d1a7f01326&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: f9375a60-5342-4234-b354-f6d1a7f01326&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/12/2021 12:57 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 3b643c80-2303-447c-b32e-fe7144c9dc91&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffffb507179e5010&#x000d;&#x000a;P3: fffff806253ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211011-1756.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-2838640-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.120a8506-4bb7-4ddd-b5f1-01eba933a410.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cc093f0a-290b-41ac-b852-915dde8c1f20.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.253a0083-920e-40cb-874d-c24bfde8f963.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.37afcc71-a0c7-498f-8413-feee37a7d0cc.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.e5c10665-50d6-4ec5-bf46-2cc455994f30.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_963ba4d6f169c01860572986a3dc3c22cdd041fd_00000000_cab_80fe207c-3758-4756-aba1-1c5ec66b9f36&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 80fe207c-3758-4756-aba1-1c5ec66b9f36&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/9/2021 6:47 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 3c75d990-4c87-4c03-af1e-2ad6702066bc&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffff9d81457f5010&#x000d;&#x000a;P3: fffff80770fea9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211008-2344.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-948921-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b040f1a-dcc1-4b29-8aae-146cef9fc15f.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c9e4b988-5f2e-4cb3-a498-de1a43c2e9cb.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_a2d44c871c596695a8edfce75e5ec9e11048_00000000_cab_280239be-fc60-4d6b-ae07-80aa4ad4ea2d\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20210915_1 EC_0_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ad5b03b8-dddf-47bb-a78d-0a19236326d5.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_a2d44c871c596695a8edfce75e5ec9e11048_00000000_cab_280239be-fc60-4d6b-ae07-80aa4ad4ea2d\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6afff1a4-1b69-4e82-b86d-288a410da1d8.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ab0a8a07-450f-42e1-a7af-d2ac321bbbeb.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e7388118-7038-406e-b3e1-bf5ba04f7d36.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.93ec0bab-7b9e-47a7-83ce-238f5ab7b6dc.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_a2d44c871c596695a8edfce75e5ec9e11048_00000000_cab_280239be-fc60-4d6b-ae07-80aa4ad4ea2d&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 280239be-fc60-4d6b-ae07-80aa4ad4ea2d&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/9/2021 11:10 PM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: c12b88c8-fd2d-4a0d-9ff6-391a39763624&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffff9b8f80bed050&#x000d;&#x000a;P3: fffff8044b0ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211009-1609.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-21777078-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c341b94a-ea41-49e1-afa5-19c8bc491873.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.45554208-2ec3-494f-bbf7-0106c633879d.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_f1f54b983483b5eabc2a47beff22b9ed02fbe72_00000000_cab_1fe687a8-9616-4f28-80c6-10c2fa3375cf\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20210915_1 EC_0_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b29d6b05-7d4a-4a4a-8b58-84d4a183482b.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_f1f54b983483b5eabc2a47beff22b9ed02fbe72_00000000_cab_1fe687a8-9616-4f28-80c6-10c2fa3375cf\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b2f5921a-41d6-42f7-b008-d3f5e858eca0.tmp.etl&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fddcfb62-ae99-4662-86a2-e651ff2c81dd.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7bf7d635-cda6-4204-87a5-06c88e14e3ca.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.aa8c1515-f534-44a7-9f8f-24ce04378c47.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_f1f54b983483b5eabc2a47beff22b9ed02fbe72_00000000_cab_1fe687a8-9616-4f28-80c6-10c2fa3375cf&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 1fe687a8-9616-4f28-80c6-10c2fa3375cf&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
10/12/2021 1:06 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere, type 0&#x000d;&#x000a;Event Name: LiveKernelEvent&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: de468d79-27df-44bd-bede-d5883e44631f&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 117&#x000d;&#x000a;P2: ffffb5070eb9d010&#x000d;&#x000a;P3: fffff806253ca9c4&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_22000&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 256_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20211011-1803.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\SystemTemp\WER-18921-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eee9c2b2-3786-46fe-aa88-ae4b74e65fd3.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.104c1bd6-6534-4abc-bd9f-dff4c11b467b.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.87b33ac7-72af-48e6-be1a-c422d41ff6fe.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a3a38108-eff1-4371-b047-fe0e90ec0078.tmp.txt&#x000d;&#x000a;\\?\C:\Windows\SystemTemp\WER.99ae8c7d-76fa-40da-8e58-f777c1cee722.tmp.WERDataCollectionStatus.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_a93fa79e96d464738f7011c96ee11607dd295d3_00000000_cab_5b58d35b-d0a7-417c-8a90-497417c1f5f0&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 5b58d35b-d0a7-417c-8a90-497417c1f5f0&#x000d;&#x000a;Report Status: 268435456&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

p64imp

New member
Local time
1:13 AM
Posts
11
Here is the link to my memory dump file:


One of my greatest concerns is that i return this only to find it was related to that memory chip, or ssd's (aka hardware upgrades i did).

I'm trying to prove that it is like the last user said, a gpu/cpu fault or general faulty laptop before i go through the heartache of sending this guy back.

I do not plan on using this memory module in the new laptop i receive, but i'm also not convinced it is causing all this. I have not yet pulled it out but did plan to. From the last user's observation though, i already ordered a replacement and planned on sending this one back (especially as amazon only has 2 replacements of this model left - once they dry up in this climate, they won't be back, so good time to act i guess).

I'm not familiar with the "belt and suspenders" approach terminology for backups. can you enlighten me? From googling it generally says to take precautions to minimize risk, however i would like to know how that pertains to a macrium reflect backup image.

There's no risk restoring an image taken on one laptop to restore to another laptop given the hardware remains the same i trust? Would it see different hardware and complain about software registrations for windows, office, etc.? There's no specific machine level registrations that software would carry out to cause me concern for restoring the image as well?

Thanks again, i'm indebted to you for your feedback.
 

My Computer

System One

  • Operating System
    Windows 11

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
Backup images are typically reliable methods to protect data.
Problems can occur if the image is made at the time of corruption of the operating system, drive file system, malware, etc.

Backing up files in addition to backup images is an extra layer of protection.

Sometimes saving images to the cloud or saving backup files to the cloud is an important step (fire, flood, other problems related to mother nature, etc.)

Restoring an image to different hardware I've not done and like you I was wondering if there could be problems. Somebody has already tested it. So consider opening a thread in the Eleven Forum backup and restore forum room.

The computer or motherboard manufacture is responsible for the hardware and software at the time of sale. So there should be no BSOD whether hardware or software related. It will take a while to download the file. I'll let you know later if there were any misbehaving drivers.

For hardware testing it's best to monitor stability / instability during swaps or removal on any potentially malfunctioning hardware.





Edit:

The memory dump was debugged.
There were no misbehaving drivers seen.

There was only one BSOD dump file.

It's often best to debug files from multiple crashes to see whether the underlying problem is malfunctioning hardware or a misbehaving driver.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

p64imp

New member
Local time
1:13 AM
Posts
11
So in your best opinion do you think the fault is from a malfunctioning GPU hardware on my Nvidia graphics chip?
 

My Computer

System One

  • Operating System
    Windows 11

zbook

Active member
Member
VIP
Local time
3:13 AM
Posts
145
The more the mini or memory dump files debugged the easier to determine driver versus hardware.

Windows has a tool to stress test drivers.

But again the computer or motherboard manufacturer is responsible for making sure the software works well with the hardware at the time of purchase. There should be no BSOD.

With the low inventory on Amazon you could make a brand new restore point and activate the tool.

This is a tutorial on Windows Driver Verifier (WDV): Enable and Disable Driver Verifier in Windows 10
 

My Computer

System One

  • Operating System
    Windows 10
Top Bottom