New Recoil 15 laptop with 16GB 3080 GPU!

[ubuysa]

Sadly the laptop has restarted itself again when I was away, the new files are uploaded into the same drive folder for you to take a look when free, thank you for your help!

The dumps in that Google Drive folder (https://drive.google.com/drive/folders/1C58rCTkI6OrEJnlHXZB8G9GmkbZikAmo) have the same timestamp and appear to be exactly the same dumps as the ones I've already looked at??

You might try removing the M.2 SSD and reinserting it fully. We've had a few people with strange issues that were solved by re-seating the M.2 SSD.

If you can get at the RAM easily then reseat that as well, stuff does move in transit sometimes.

I've taken a more detailed look at your kernel dump and there are a few things I'm quite concerned about...

1. What is midrive? It appears to be some sort of cloud service? There is an error in the active thread driver list for a driver called dump_midrive.sys which I'd put down to the amdkmdag.sys chipset driver problem. You also have a midrive.sys driver which I assume is also related to this midrive product. What is that and did you install it?

2. There are drivers loaded that appear to be related to a produce called Tencent PC Manager and that appears to be some sort of Chinese based anti-virus engine (softaal64_ev.sys, TAOKernelEx64_ev.sys, TAOAcceleratorEx64_ev.sys, TFsFltX64_ev.sys, TsNetHlpX64_ev.sys, TSSysKit64_EV.sys and TSDefenseBT64.sys)? It's flagged as a PUP (Potentially Unwanted Program) in many places and flagged as spyware in others. Have you perhaps installed this in error? If Windows Defender is active (and its drivers are loaded) then this may cause issues even if the Tencent product is legit.

3. There are two drivers loaded (XLGuard.sys and xlwfp.sys) that appear to relate to something called ShenZhen Thunder Networking Technologies, there is a suggestion that they are related to downloaded codecs. There are also suggestions that they may be some sort of Chinese spyware. They are certainly unusual and suspicious. There is an error in the active thread drivers list for Netwtw10.sys which is an Intel wireless card driver. I'd put that down to the amdkmdag.sys chipset driver problem as well, but perhaps it's being caused by these ShenZhen drivers?

I would investigate midrive if it's not something you have installed and setup. I would MOST DEFINITELY investigate the Tencent application and whatever the ShenZhen Thunder Networking thing is. On the face of it you would seem to have some highly suspicious drivers installed there and I'd want to get them out. If these products are some sort of spyware/trojan then they may be hard to remove. If they are products that you installed then do you really want and need them? If this were mine I'd be doing a clean install of Windows to be sure of getting rid of them.

I have no idea whether these rogue applications and drivers are causing your restarts but they certainly could be.

 

[Blahblahblah]

Upload any new dumps if it restarts again.

any idea what is going on with my laptop? I have uploaded new files to the drive here:

minidumps – Google Drive

drive.google.com

Thank you

 

[Blahblahblah]

The dumps in that Google Drive folder (https://drive.google.com/drive/folders/1C58rCTkI6OrEJnlHXZB8G9GmkbZikAmo) have the same timestamp and appear to be exactly the same dumps as the ones I've already looked at??

You might try removing the M.2 SSD and reinserting it fully. We've had a few people with strange issues that were solved by re-seating the M.2 SSD.

If you can get at the RAM easily then reseat that as well, stuff does move in transit sometimes.

I've taken a more detailed look at your kernel dump and there are a few things I'm quite concerned about...

1. What is midrive? It appears to be some sort of cloud service? There is an error in the active thread driver list for a driver called dump_midrive.sys which I'd put down to the amdkmdag.sys chipset driver problem. You also have a midrive.sys driver which I assume is also related to this midrive product. What is that and did you install it?

2. There are drivers loaded that appear to be related to a produce called Tencent PC Manager and that appears to be some sort of Chinese based anti-virus engine (softaal64_ev.sys, TAOKernelEx64_ev.sys, TAOAcceleratorEx64_ev.sys, TFsFltX64_ev.sys, TsNetHlpX64_ev.sys, TSSysKit64_EV.sys and TSDefenseBT64.sys)? It's flagged as a PUP (Potentially Unwanted Program) in many places and flagged as spyware in others. Have you perhaps installed this in error? If Windows Defender is active (and its drivers are loaded) then this may cause issues even if the Tencent product is legit.

3. There are two drivers loaded (XLGuard.sys and xlwfp.sys) that appear to relate to something called ShenZhen Thunder Networking Technologies, there is a suggestion that they are related to downloaded codecs. There are also suggestions that they may be some sort of Chinese spyware. They are certainly unusual and suspicious. There is an error in the active thread drivers list for Netwtw10.sys which is an Intel wireless card driver. I'd put that down to the amdkmdag.sys chipset driver problem as well, but perhaps it's being caused by these ShenZhen drivers?

I would investigate midrive if it's not something you have installed and setup. I would MOST DEFINITELY investigate the Tencent application and whatever the ShenZhen Thunder Networking thing is. On the face of it you would seem to have some highly suspicious drivers installed there and I'd want to get them out. If these products are some sort of spyware/trojan then they may be hard to remove. If they are products that you installed then do you really want and need them? If this were mine I'd be doing a clean install of Windows to be sure of getting rid of them.

I have no idea whether these rogue applications and drivers are causing your restarts but they certainly could be.

Thanks for this, Tencent is a Chinese social media company and I use it on all my devices, I am not surprised they flag up as potential spyware but there's not much to do about it, thunder is a Chinese downloading client I use.

But I am not sure what is midrive, I use a few cloud products including OneDrive, GoogleDrive, MEGA and Dropbox, I will take a look into this Midrive.

But it seems that these shutdowns only happens when the computer goes to sleep, it seems like some kind of error with power management? when I have the laptop on battery and screen closed, it seems like it just restarts itself again and again until the battery is flat (this happened today), but everything is fine when it is on and I am using it. I have uploaded the latest files into the same drive again, let me know if you find something.

Thank you again for your help on this!

 

[ubuysa]

any idea what is going on with my laptop? I have uploaded new files to the drive here:

minidumps – Google Drive

drive.google.com

Thank you

The minidump in here is the same as the one I've already seen (050221-11609-01.dmp). Are there any later minidumps in that folder? Check their date and time stamps.

The Application and System logs are current (ie. new compared to the last ones) but there is still nothing in there to indicate why the system restarted. I'm still seeing the errors for the Killer wireless card but they happen after the system has rebooted.

You might want to modify the auto-restart function so that the system halts rather than restarts to allow time for a kernel dump to be written.

To do this, type sysdm.cpl into the Run command box, in the window that opens click the Advanced tab, the click the bottom Settings button (Startup and Recovery). In there uncheck the 'Automatically Restart' checkbox - that will cause the system to halt on an error. Also check that the 'Write Debugging Information' is set to 'Automatic memory dump' and that the dump location is %SystemRoot%\MEMORY.DMP. Then click OK.

Then click the top Settings button (Performance) and then click the Advanced tab. In the Virtual Memory section click the Change button. Make sure that the top checkbox 'Automatically manage paging file sizes for all drives' is checked - everything else should then be greyed out. Then click OK.

You can then click OK to close the Performance dialog and then click OK again to close the System Properties dialog.

Now reboot.

You should now be getting a kernel dump (in C:\Windows\Memory.dmp), stopping the auto-restart should allow time for it to be written.

 

[Blahblahblah]

The minidump in here is the same as the one I've already seen (050221-11609-01.dmp). Are there any later minidumps in that folder? Check their date and time stamps.

The Application and System logs are current (ie. new compared to the last ones) but there is still nothing in there to indicate why the system restarted. I'm still seeing the errors for the Killer wireless card but they happen after the system has rebooted.

You might want to modify the auto-restart function so that the system halts rather than restarts to allow time for a kernel dump to be written.

To do this, type sysdm.cpl into the Run command box, in the window that opens click the Advanced tab, the click the bottom Settings button (Startup and Recovery). In there uncheck the 'Automatically Restart' checkbox - that will cause the system to halt on an error. Also check that the 'Write Debugging Information' is set to 'Automatic memory dump' and that the dump location is %SystemRoot%\MEMORY.DMP. Then click OK.

Then click the top Settings button (Performance) and then click the Advanced tab. In the Virtual Memory section click the Change button. Make sure that the top checkbox 'Automatically manage paging file sizes for all drives' is checked - everything else should then be greyed out. Then click OK.

You can then click OK to close the Performance dialog and then click OK again to close the System Properties dialog.

Now reboot.

You should now be getting a kernel dump (in C:\Windows\Memory.dmp), stopping the auto-restart should allow time for it to be written.

I have done everything here, it restarted, I have uploaded the latest Memory.dmp into the drive along with the new event files, I will let you know if it restarts again when I am not using it.
Thank you!

 

[ubuysa]

I have done everything here, it restarted, I have uploaded the latest Memory.dmp into the drive along with the new event files, I will let you know if it restarts again when I am not using it.
Thank you!

If you've unchecked the 'Automatically Restart' checkbox and it's still restarting then it's not because of BSODs. I would then be concerned that it's a hardware issue related to power transitions. I'm downloading the kernel dump you uploaded (memory.dmp) and I'll report back of course, but your best course of action may well be a completely clean reinstall of Windows to ensure that you have a stable OS, any restarts then would most likely be hardware related.

 

[ubuysa]

The kernel dump you uploaded is for exactly the same event (a BSOD) as the minidump I've seen, it's dated Sun May 2 17:06:33.597 2021.

However, since it's a kernel dump it does contain a lot more information and absolutely everything in this dump points at nvlddmkm.sys, the Nvidia graphics driver.

Here for instance is the stack trace showing the function calls made up to the bug check...

STACK_TEXT:
ffffdd84`24c16ca0 fffff807`320e2d2a     : 00000000`00001000 00000000`00000000 ffff9604`a51babc0 ffff9604`a0664788 : nvlddmkm+0x41f14a
ffffdd84`24c16d30 fffff807`320e35d4     : ffff9604`a6d64000 ffff9604`ad3f6660 00000000`0065d000 00000000`00001990 : nvlddmkm+0x472d2a
ffffdd84`24c16db0 fffff807`3236bb1f     : ffff9604`add46000 ffff9604`a51ae2f0 00000000`0e1f9b87 ffff9604`add46000 : nvlddmkm+0x4735d4
ffffdd84`24c16e20 fffff807`3208213d     : ffff9604`add46000 00000001`2cc16000 ffff9604`a51ae3b8 ffff9604`ad3f6660 : nvlddmkm+0x6fbb1f
ffffdd84`24c16ea0 fffff807`32082451     : ffff9604`a51ae2f0 ffff9604`add46000 ffff9604`aaa141f0 00000000`00000000 : nvlddmkm+0x41213d
ffffdd84`24c16f00 fffff807`31f1f0d1     : 00000000`00000005 ffff9604`add57000 ffff9604`add46000 00000000`00000000 : nvlddmkm+0x412451
ffffdd84`24c16f40 fffff807`32097eaf     : 00000000`00000008 ffff9604`acc7d010 ffff9604`00000005 ffff9604`addcb000 : nvlddmkm+0x2af0d1
ffffdd84`24c16fc0 fffff807`31f2609f     : ffff9604`add46000 00000000`00000005 00000000`00000000 ffff9604`add46000 : nvlddmkm+0x427eaf
ffffdd84`24c17000 fffff807`320938b2     : ffff9604`add46000 00000000`00000005 ffff9604`add52000 00000000`00000005 : nvlddmkm+0x2b609f
ffffdd84`24c17040 fffff807`320a9bf9     : ffff9604`add46000 ffff9604`addd4000 ffff9604`addd4000 ffff9604`add57000 : nvlddmkm+0x4238b2
ffffdd84`24c17080 fffff807`31d17894     : ffff9604`add46000 ffff9604`add52000 ffffdd84`24c17159 ffff9604`add46000 : nvlddmkm+0x439bf9
ffffdd84`24c170d0 fffff807`31ec852e     : ffff9604`add46000 ffff9604`add4f000 ffff9604`add46000 ffff9604`add4f000 : nvlddmkm+0xa7894
ffffdd84`24c171c0 fffff807`31ec86fe     : 00000001`00000001 00000000`00000003 ffff9604`add460ff ffff9604`add4f000 : nvlddmkm+0x25852e
ffffdd84`24c17270 fffff807`31cefbea     : ffff9604`add46000 ffff9604`add67000 00000000`00000000 00000000`00000000 : nvlddmkm+0x2586fe
ffffdd84`24c172a0 fffff807`329eb191     : ffff9604`a0792000 ffff9604`adfed000 ffffdd84`24c17449 00000000`00000001 : nvlddmkm+0x7fbea
ffffdd84`24c173d0 fffff807`329aeaed     : ffff9604`a0793734 00000000`00000001 00000000`00000001 fffff807`2180d0c5 : nvlddmkm!nvDumpConfig+0x4ae801
ffffdd84`24c174b0 fffff807`329ae663     : 00000000`00000000 ffff9604`a0792000 00000000`00000000 00000000`00000000 : nvlddmkm!nvDumpConfig+0x47215d
ffffdd84`24c17580 fffff807`329d9ade     : ffff9604`a0792000 ffffdd84`24c17679 00000000`00000001 00000000`00000007 : nvlddmkm!nvDumpConfig+0x471cd3
ffffdd84`24c175d0 fffff807`2dfd4b6d     : fffff807`329d99b4 00000000`00000001 00000000`00000000 00000000`ffffffff : nvlddmkm!nvDumpConfig+0x49d14e
ffffdd84`24c176e0 fffff807`2dfd40bf     : 00000000`00000000 ffffdd84`24c177a1 00000000`00000000 ffff9604`a094c6f0 : dxgkrnl!DpiDxgkDdiSetPowerState+0x59
ffffdd84`24c17740 fffff807`2dfd4fee     : 00000000`00000000 ffff9604`aa39cb90 00000000`00000001 00000000`00000001 : dxgkrnl!DpiFdoSetAdapterPowerState+0x15f
ffffdd84`24c17800 fffff807`2dfd4441     : ffff9604`9dbf3400 ffff9604`9dbf34f0 ffff9604`97b77df0 ffff9604`aa39cd80 : dxgkrnl!DpiFdoHandleDevicePower+0x2ee
ffffdd84`24c178a0 fffff807`2dfd5990     : ffff9604`aa39cb90 ffff9604`a09f5180 ffff9604`a09f5030 e94bd39e`4794807b : dxgkrnl!DpiFdoDispatchPower+0x21
ffffdd84`24c178d0 fffff807`329f2220     : ffff9604`adfed000 ffffdd84`24c17a99 ffff9604`adfed000 ffff9604`aa39cd80 : dxgkrnl!DpiDispatchPower+0xe0
ffffdd84`24c179f0 fffff807`329f1328     : ffff9604`a09f5030 ffff9604`a0792000 ffff9604`a09f5030 ffff9604`00000000 : nvlddmkm!nvDumpConfig+0x4b5890
ffffdd84`24c17b00 fffff807`1f39ce99     : ffff9604`952c92c0 ffffdd84`24c17bb0 ffff9604`aa39cb90 ffff9604`00000000 : nvlddmkm!nvDumpConfig+0x4b4998
ffffdd84`24c17b30 fffff807`1f2f53b5 : 00000000`00000000 fffff807`1f39ccc0 00000000`00000000 00000000`00000063 : nt!PopIrpWorker+0x1d9
ffffdd84`24c17bd0 fffff807`1f3fe348     : ffff8481`7715f180 ffff9604`952c92c0 fffff807`1f2f5360 00000001`40aa14a8 : nt!PspSystemThreadStartup+0x55
ffffdd84`24c17c20 00000000`00000000     : ffffdd84`24c18000 ffffdd84`24c11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

You read the stack trace from the bottom up, you can see repeated calls to nvlddmkm.sys following an interrupt request (the nt!PopIrpWorker+0x1d9) before they just stop because the IRP was held for too long (interrupt processing must be as rapid as possible, that's why the system sticks a timer on all interrupt processing)....

The IRP in question also shows nvlddmkm.sys as the driver holding the IRP.....

Irp is active with 6 stacks 5 is current (= 0xffff9604aa39cd80)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffff960497b9b0a0 00000000 fffff8072de8fc90-ffffdd8424c17838
           \Driver\pci    dxgkrnl!DpiFdoPowerCompletionRoutine
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9604a09f5030 00000000 fffff8071f3786f0-ffff9604ae44a918 Success Error Cancel pending
           \Driver\nvlddmkm    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff9604ae44a918

            Args: 00000000 00000000 00000000 00000000

Notice that the driver(s) referenced are nvlddmkm.sys and dxgkrnl.sys (the DirectX kernel).

The device stack shows the specific object responsible for the BSOD and also points at nvlddmkm.sys (or of course the graphics card)....

  !DevObj           !DrvObj            !DevExt           ObjectName
  ffff9604a09f5030  \Driver\nvlddmkm   ffff9604a09f5180
  ffff960497b77df0  \Driver\ACPI       ffff960497ac0be0
> ffff960497b9b0a0  \Driver\pci        ffff960497b9b1f0  NTPNP_PCI0020
!DevNode ffff960497b9b9e0 :
  DeviceInst is "PCI\VEN_10DE&DEV_249C&SUBSYS_11141D05&REV_A1\4&18a5db89&0&0009"
  ServiceName is "nvlddmkm"

Note that the PCI\VEN_10DE&DEV_249C is the device ID of the GeForce RTX 3080 laptop GPU.

The list of driver calls made by the active thread (the Idle thread) and which we've already seen in the minidump earlier include Netwtw10.sys, dump_midrive.sys (I still don't know what midrive is) and amdkmdag.sys. You've taken action related to these drivers since this dump was written of course.

fffff807`22e910d8  fffff807`2fd0c7d5Unable to load image \SystemRoot\System32\drivers\Netwtw10.sys, Win32 error 0n2
 Netwtw10+0xec7d5

fffff807`22e8fc18  fffff807`31b056dcUnable to load image \SystemRoot\System32\drivers\dump_midrive.sys, Win32 error 0n2
 dump_midrive+0x256dc

fffff807`22e8d5d8  fffff807`3e58e160Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0365573.inf_amd64_a1e6ef6331086c90\B365567\amdkmdag.sys, Win32 error 0n2
 amdkmdag+0x4d6e160

Although this kernel dump was taken before you updated drivers it is very clearly pointing either at the Nvidia graphics driver or at the RTX 3080 itself. Since you're still seeing restarts after ensuring that you have the latest drivers I would suspect the RTX 3080 itself.

I would suggest a completely clean reinstall of Windows from bootable media, deleting all existing UEFI partitions, allowing Windows Update to install all drivers, downloading and manually installing the latest RTX 3080 driver from Nvidia (don't use GeForce Experience for this) and then checking in Device Manager that everything has a suitable driver (no yellow triangles with black exclamation marks). I would strongly suggest that you avoid installing any other software to keep as pristine an operating system platform as you can. Since it fails in the idle thread you should simply be able to leave it after installing all drivers and see whether it restarts. If it does then it's pretty certain to be a hardware issue and most likely the RTX 3080.

Obviously if you get another BSOD upload C:\Windows\Memory.dmp immediately.

 

[Blahblahblah]

If you've unchecked the 'Automatically Restart' checkbox and it's still restarting then it's not because of BSODs. I would then be concerned that it's a hardware issue related to power transitions. I'm downloading the kernel dump you uploaded (memory.dmp) and I'll report back of course, but your best course of action may well be a completely clean reinstall of Windows to ensure that you have a stable OS, any restarts then would most likely be hardware related.

Thank you for this detailed explanation, the laptop now doesn't restart itself, it simply stays dead after it goes to sleep the screen and keyboard stays off but the fan stays on, until the battery runs dry that is. When the lid is closed it's the same. have to force restart it, then the laptop went in recovery mode to fix the system drive for some reason,it just seems like issues are getting bigger by the day... I cannot afford to spend too much time re-installing everything at the moment as I am using the laptop for work, will have to wait until a quite period to test it out to see if the fresh re-install works, if not then it's sending back to PCS for them to figure out what the issue is.


To be honest I am a little disappointed with PCS, as this is my first purchase with them and it is a top spec product...


I have uploaded the latest logs into the drive, don't know if you can see a thing or 2 to find out why the laptop just stays asleep now. but let me know if you can see something.

Thank you!

 

[ubuysa]

Thank you for this detailed explanation, the laptop now doesn't restart itself, it simply stays dead after it goes to sleep the screen and keyboard stays off but the fan stays on, until the battery runs dry that is. When the lid is closed it's the same. have to force restart it, then the laptop went in recovery mode to fix the system drive for some reason,it just seems like issues are getting bigger by the day... I cannot afford to spend too much time re-installing everything at the moment as I am using the laptop for work, will have to wait until a quite period to test it out to see if the fresh re-install works, if not then it's sending back to PCS for them to figure out what the issue is.


To be honest I am a little disappointed with PCS, as this is my first purchase with them and it is a top spec product...


I have uploaded the latest logs into the drive, don't know if you can see a thing or 2 to find out why the laptop just stays asleep now. but let me know if you can see something.

Thank you!

Given that kernel dump and now the issues that you're describing I would suspect that you have a hardware problem there, and I'd point at the GPU primarily. There would seem to be a problem with power transition states. It would have been very useful to test it with a fully clean reinstall of Windows just to be certain that this isn't software related, but I do understand your frustration and disappointment.

I think you should probably call PCS now and talk about an RMA. You'll be without the laptop for several weeks in that case, another reason why a clean install of Windows to confirm it's not a software issue is in your best interests. Point PCS at this thread and in particular at the kernel dump (memory.dmp). They may well ask you to do another fully clean install, they don't want you to have to send the laptop back if there is any chance it's a software issue.

I understand your disappointment with PCS because of these issues. All laptops and PCs from PCS should work first time out of the box and run without issue for a good 10 years, but sadly real life isn't that predictable. Electronic stuff fails, and sometimes fails early, and there is no way for PCS to know when they're building your laptop which components are likely to fail early. If there was a way to know that then they'd swap them out at build time. I know that doesn't make things any better for you but the one thing you can be sure of, and the main reason why many of us have PCS build our computers, is that PCS won't quibble (as some High Street companies are known to do) and it will get fixed under warranty.

Do keep us updated and let us know how you get on.

 

[Blahblahblah]

Given that kernel dump and now the issues that you're describing I would suspect that you have a hardware problem there, and I'd point at the GPU primarily. There would seem to be a problem with power transition states. It would have been very useful to test it with a fully clean reinstall of Windows just to be

Thank you for helping me this far, you have been very kind giving up your time to help me, at least now I know my only options I will RMA this when work quietens down a bit (After a clean reinstall of windows) and I can send the laptop back for PCS to figure out.

 

[ubuysa]

Thank you for helping me this far, you have been very kind giving up your time to help me, at least now I know my only options I will RMA this when work quietens down a bit (After a clean reinstall of windows) and I can send the laptop back for PCS to figure out.

I think that's the wisest course of action now. Be sure to point PCS at this thread and the kernel dump you have. Do keep us updated.

 

[Blahblahblah]

I think that's the wisest course of action now. Be sure to point PCS at this thread and the kernel dump you have. Do keep us updated.

Hey UBUYSA, the RMA has completed and comeback, it turned out to be a fault in the 1.6TB ENMOTUS FUZEDRIVE and the laptop motherboard, they have replaced these 2 components and the laptop is now fine! Luckily it wasn't the 3080p or I would have needed to wait for a while as they are ran out atm. Thank you so much for your help!

 

[Blahblahblah]

I think that's the wisest course of action now. Be sure to point PCS at this thread and the kernel dump you have. Do keep us updated.

Hi Ubuysa, after I got the laptop back from PCS it seems the issue is still there, but this time is a little strange, so the laptop will go into sleep mode for around 10-15 mins, if you wake it up within that time it is fine, but the laptop seems to crash during sleep if it sleeps too long lol. So if I go and wake it up after 10-15 mins, then it will crash or blue screen, then restarts again...

Please have a look at the shared google Drive folder to see if you can spot anything, also for some reason my c/windows folder do not have minidump folder or memory.dmp

minidumps – Google Drive

drive.google.com

Thank you!

 

[ubuysa]

I

Hi Ubuysa, after I got the laptop back from PCS it seems the issue is still there, but this time is a little strange, so the laptop will go into sleep mode for around 10-15 mins, if you wake it up within that time it is fine, but the laptop seems to crash during sleep if it sleeps too long lol. So if I go and wake it up after 10-15 mins, then it will crash or blue screen, then restarts again...

Please have a look at the shared google Drive folder to see if you can spot anything, also for some reason my c/windows folder do not have minidump folder or memory.dmp

minidumps – Google Drive

drive.google.com

Thank you!

There is nothing that leaps out at me in either of those logs, but if it's crashing whilst sleeping then I wouldn't expect to. If it's failing somehow during sleep then I would expect that to be a hardware issue.

I would contact PCS again and explain what it's doing now.

 

[Mnemonic]

Hi @Blahblahblah - Did you ever find/fix the issue?