D
Deleted member 17413
Guest
...Who, the OP?
I think Sassy is just the username....
I think Sassy is just the username....
PC restarts/locks up
- Thread starter Sassy
- Start date
ubuysa
The BSOD Doctor
Got them thanks. I'll take a look tomorrow.Ahhh, I thought the scan that @AgentCooper said to try did it, I had no more reboots all of last night or from 10am this morning, but alas, it just happened again
Latest Memory.dmp
Dropbox
www.dropbox.com
Latest Application
Dropbox
Latest System
Dropbox
Thank you again in advance!
Me? Nah, I'm just a pussy cat. This pussy cat.....
Got them thanks. I'll take a look tomorrow.
Thank you ever so much!
ubuysa
The BSOD Doctor
I'm not sure you're going to be so happy, it looks to me like you may have a hardware error, and possibly the same issue that's affecting users with four 3600MHz RAM sticks in an AMD build.....
In the kernel dump the stop code (as you noted) is CRTITCAL_PROCESS_DIED which means pretty much what it says, a critical Windows process ended unexpectedly. The process that died in this case was services.exe - the Windows Service Control Manager, the component that looks after all the system services. My guess is that one of the services encountered a fatal error and crashed, taking services.exe down with it.
The module that failed was daxexec.dll, the stack trace shows things falling apart immediately after it is called. Sadly I'm not able to discover exactly what that module actually does. I do know that DAX (Data Analysis and Expression) is a 'language' used for statistical analysis and which is implemented in Windows as a set of functions used by, amongst others, Excel. I may be stretching informed guesswork a bit far here though.
The list of driver calls by the failing thread does show an error for our old favourite nvlddmkm.sys - the Nvidia graphics driver. It may be that the driver needs updating, the timestamp on the version you have is Jan 22nd 2021. Based on what else we see here though I think this may be a red herring or even a symptom rather than the cause. It's worth bearing in mind that there may be a graphics issue here though.
The idea of a hardware fault is continued in your System log (the Application log contains nothing of interest). There are several log entries in there by WHEA, the Windows Hardware Error Architecture reporting hardware faults. The component identified here is the processor cache, so perhaps there is a CPU issue here, or perhaps that's just what caught a hardware error somewhere else? There are three of these in your system log between 20th Feb and 26th Feb. There is also another BSOD in there which did capture a dump - that's probably the one that I didn't download or analyse and which is now not in the cloud anymore. That's my mistake (and a good lesson) because the stop code for that one was WHEA_UNCORRECTABLE_ERROR which indicates a hardware problem. Sadly there would have been an error fault record in there which may have identified the failing component. If you still have that dump anywhere please upload it again!
Personally I think this is a hardware issue and it would not surprise me in the least to find that this is another example of the four 3600MHz RAM sticks in an AMD build issue. I appreciate that you only have two 3600MHz RAM sticks installed but you're not the only user having issues with two RAM sticks in an AMD build.
Before PCS will consider a hardware issue they will want you to do two things, so you might as well do them now and save the cost of hanging on to the phone to them for two hours only to be told to do this.....
First they will want to test your RAM, so download Memtest and extract the tool from the downloaded archive. Run the tool to make a bootable USB stick containing Memtest (it doesn't need to be a big USB stick, less than 1GB will be fine, but it will erase everything else on the USB stick). Then boot that USB stick and Memtest will start running. Allow it to complete the four iterations of the 13 different tests that this free version does, this will take many hours on your 16GB so leave it running overnight. Even one single error reported is a failure. If that happens remove one stick and re-run Memtest on each stick one at a time. If you get errors on one or both sticks then RAM is your problem and you'll need to contact PCS (by phone) to get the RAM replaced.
Even if Memtest runs clean with no errors then the second thing we need to do is to confirm that your Windows system is complete and stable and the only way to do that is with a clean reinstall.
1. Unplug everything from the PC except the monitor, mouse and keyboard (and Ethernet if you cable connect to the router).
2. Download and run the Windows Media Creation Tool to make a bootable USB stick (8GB min) containing the installation files for the latest version of Windows 10.
3. Boot that USB and select a Custom Install.
4. Delete all UEFI partitions on your system drive (there will be four) so that the whole drive shows as 'unallocated space'.
5. Highlight that unallocated space and click the Next button. The installer will create the correct partition structure and install Windows.
6. Once Windows is installed, go through the setup carefully ensuring that you understand the implications of every choice you're making.
7. When the setup is complete run Windows Update repeatedly - even across reboots - until no more updates are found (this is vitally important). Also install all optional updates that are found.
8. Download the Nvidia graphics driver for your build from the Nvidia website and install the driver manually.
9. Download and run the AMD driver support tool and install all drivers that it finds. At this point you'll have a stable and reliable Windows platform, don't spoil that by making any configuration changes, by plugging in other hardware, or by installing other software (expect my suggestions below). Now we need to stress test the PC to see whether it's stable.
10. Since previous minidumps have pointed at the graphics card download and run Unigine Heaven* to stress the GPU.
11. To stress the CPU (and RAM) download and run Prime95*.
* Others with more experience of stress testing that I may have better suggestions.
That should keep you out of trouble over the weekend.....
Last edited:
ubuysa
The BSOD Doctor
For some reason the forum won't let me add links inline in that post, so they're here:
Memtest https://www.memtest86.com
Windows Media Creation Tool https://www.microsoft.com/en-us/software-download/windows10
Unigine Heaven https://benchmark.unigine.com/heaven
Prime95 https://www.mersenne.org/download/
Memtest https://www.memtest86.com
Windows Media Creation Tool https://www.microsoft.com/en-us/software-download/windows10
Unigine Heaven https://benchmark.unigine.com/heaven
Prime95 https://www.mersenne.org/download/
Hoooo boy!
It's interesting there were errors from the 20th because the PC wasn't ordered until the 22nd and arrived the 23rd - if it was showing errors previous to those dates then I feel like it shouldn't have passed QC and been shipped.
I did think of a Windows re-install myself, but I was worried that may break the warranty or something so was very hesitant to do so.
I'll crack on with all of this over the weekend and keep you posted
Thank you again, so much for taking the time to help me with this, you guys have been so very helpful and I appreciate you all!
It's interesting there were errors from the 20th because the PC wasn't ordered until the 22nd and arrived the 23rd - if it was showing errors previous to those dates then I feel like it shouldn't have passed QC and been shipped.
I did think of a Windows re-install myself, but I was worried that may break the warranty or something so was very hesitant to do so.
I'll crack on with all of this over the weekend and keep you posted
Thank you again, so much for taking the time to help me with this, you guys have been so very helpful and I appreciate you all!
ubuysa
The BSOD Doctor
It's likely that the errors before you got it was Q&A stress testing it then.
I am still concerned this is the RAM-AMD issue though.
ubuysa
The BSOD Doctor
I have a horrible feeling that this is some sort of timing issue that can affect other configurations than 4 x 3600....
Depends on how many people are experiencing this issue
ubuysa
The BSOD Doctor
There are easily enough people having similar issues with 4 x 3600 MHz to show that this is more than just a one-off.
jamiephillips909
Godlike
Sassy could you take a photo of your ram ? And post it here ?
Good morning!
Just a quick update, memtest was done and it passed, so the next stage later today will be the clean re-install of Windows.
@jamiephillips909 - if you'd still like a photo I will get to it when I can. I have a chronic illness and I'm still feeling the effects of taking delivery of the pc and setting it up (it weighs a ton!)
Just a quick update, memtest was done and it passed, so the next stage later today will be the clean re-install of Windows.
@jamiephillips909 - if you'd still like a photo I will get to it when I can. I have a chronic illness and I'm still feeling the effects of taking delivery of the pc and setting it up (it weighs a ton!)
jamiephillips909
Godlike
no photo needed then dont worry about it
just wanted to see if your ram is in the grey slots and not in the black slots no photo required you can have a look yourself when your feeling up to it every time i have to move my pc it really takes it out of me aswell so no problem !!
its most probably in the right location but just checking as on other forums on self build they have not inserted the ram into the recommended slots on the motherboard
Last edited:
Hello again everyone!
Just an update...and not a good one.
The reboots/crashes continued, it was RMA'd and sent back to me with the diagnostic that it was an incorrect BIOS setting.
Aaaand, it's just had an identical crash/reboot. I could cry
I'll be calling them tomorrow, but in the meantime, if our resident DMP guru @ubuysa could have another look, we may get further with what I can tell them?
No BSOD, just a black screen with white text from whatever application is open and some high contrast RGB pixels where images/graphics are but I have uploaded the info just incase it's still at all helpful.
https://1drv.ms/u/s!Ai7-9eythfRng3mWAP8xb2OH18eG?e=kdjNRa - Memory.dmp
https://1drv.ms/t/s!Ai7-9eythfRng3ig4PrBBANQqhmm - Sysinfo
https://1drv.ms/u/s!Ai7-9eythfRng3bMNXH3CiXJJqsq - Application Event Viewer
https://1drv.ms/u/s!Ai7-9eythfRng3e86MT0u3jg3Jhw - SystemEvent Viewer
I think that's everything!
Just an update...and not a good one.
The reboots/crashes continued, it was RMA'd and sent back to me with the diagnostic that it was an incorrect BIOS setting.
Aaaand, it's just had an identical crash/reboot. I could cry
I'll be calling them tomorrow, but in the meantime, if our resident DMP guru @ubuysa could have another look, we may get further with what I can tell them?
No BSOD, just a black screen with white text from whatever application is open and some high contrast RGB pixels where images/graphics are but I have uploaded the info just incase it's still at all helpful.
https://1drv.ms/u/s!Ai7-9eythfRng3mWAP8xb2OH18eG?e=kdjNRa - Memory.dmp
https://1drv.ms/t/s!Ai7-9eythfRng3ig4PrBBANQqhmm - Sysinfo
https://1drv.ms/u/s!Ai7-9eythfRng3bMNXH3CiXJJqsq - Application Event Viewer
https://1drv.ms/u/s!Ai7-9eythfRng3e86MT0u3jg3Jhw - SystemEvent Viewer
I think that's everything!
I forgot to add - this is what I see when it reboots, this stays on the screen for a few seconds before the PC will reboot itself.
It's always the same no matter what application is on the monitors, black background, white text and weird RGB where images or graphics should be.
This picture is Chrome - you can see my bookmarks bar along the top and above that the tabs I had open, and Discord was also on top of Chrome, where the weird red pixelly 'streaks' are were where gifs were.
This was taken before the RMA, but I saw the exact same thing on todays reboot post RMA
It's always the same no matter what application is on the monitors, black background, white text and weird RGB where images or graphics should be.
This picture is Chrome - you can see my bookmarks bar along the top and above that the tabs I had open, and Discord was also on top of Chrome, where the weird red pixelly 'streaks' are were where gifs were.
This was taken before the RMA, but I saw the exact same thing on todays reboot post RMA
ubuysa
The BSOD Doctor
This is a hardware error plain and simple, the stop code is a WHEA_UNCORRECTABLE_ERROR. (WHEA is the Windows Hardware Error Architecture).
The relevant part of the WHEA error record is this....
....the relevant error is the BUSL1_SRC_IRD_I_NOTIMEOUT_ERR (Proc 12 Bank 1).
The stack trace for the active thread shows a number of calls to the Nvidia graphics processor immediately before a machine check error which ultimately leads to the bug check and BSOD. Below is the entire stack trace (minus all the addresses and such). You read these traces from the bottom up and you can clearly see the system thread startup as the kernel is called, a bunch of calls to nvlddmkm (none of which ever complete and return), the machine check abort and then a series of Hardware Abstraction Layer (HAL) calls (to handle the machine check) leading into the WHEA and the bug check...
The image you posted has all the hallmarks of a graphics card error which ties in very well with these stack trace entries and the machine check BSOD. This is a hardware error, most likely related to the Nvidia graphics card.
I would contact PCS as soon as possible. Send them the dump link and the analysis above if you like. This has likely been your problem all along, to be fair to PCS though until this dump there has been no clear indication of the cause. Now there is.
The relevant part of the WHEA error record is this....
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffb187969a3138
Section @ ffffb187969a32c0
Offset : 664
Length : 272
Flags : 0x00000000
Severity : Fatal
Error : BUSL1_SRC_IRD_I_NOTIMEOUT_ERR (Proc 12 Bank 1)
Status : 0xbc800800060c0859
Address : 0x0000000406963840
Misc. : 0xd01a0ffe00000000....the relevant error is the BUSL1_SRC_IRD_I_NOTIMEOUT_ERR (Proc 12 Bank 1).
The stack trace for the active thread shows a number of calls to the Nvidia graphics processor immediately before a machine check error which ultimately leads to the bug check and BSOD. Below is the entire stack trace (minus all the addresses and such). You read these traces from the bottom up and you can clearly see the system thread startup as the kernel is called, a bunch of calls to nvlddmkm (none of which ever complete and return), the machine check abort and then a series of Hardware Abstraction Layer (HAL) calls (to handle the machine check) leading into the WHEA and the bug check...
Code:
HalBugCheckSystem+0xca
PSHED!PshedBugCheckSystem+0x10
nt!WheaReportHwError+0x46e
nt!HalpMcaReportError+0xb1
nt!HalpMceHandlerCore+0xef
nt!HalpMceHandler+0xe0
nt!HalpHandleMachineCheck+0xe9
nt!HalHandleMcheck+0x35
nt!KiHandleMcheck+0x9
nt!KxMcheckAbort+0x7a
nt!KiMcheckAbort+0x277 (TrapFrame @ ffffc900`cf38de70)
nvlddmkm+0x4c6e6b
nvlddmkm+0x3360f7
nvlddmkm+0x1c66f8
nvlddmkm+0x16e7e2
nvlddmkm+0x16ca10
nvlddmkm+0x16cc4e
nvlddmkm+0x16ccee
nvlddmkm+0xb77bd
nvlddmkm+0xb772f
nvlddmkm+0x814ced
nvlddmkm+0x814f45
nvlddmkm+0x6688
nvlddmkm+0xc68aa2
nvlddmkm+0x816678
nt!PspSystemThreadStartup+0x55
nt!KiStartSystemThread+0x28The image you posted has all the hallmarks of a graphics card error which ties in very well with these stack trace entries and the machine check BSOD. This is a hardware error, most likely related to the Nvidia graphics card.
I would contact PCS as soon as possible. Send them the dump link and the analysis above if you like. This has likely been your problem all along, to be fair to PCS though until this dump there has been no clear indication of the cause. Now there is.
Thank you so very much for your input @ubuysa!
I did point them to this thread in the RMA and I'll do so again as it has a lot more information than before - I'll be calling them in the morning.
Thank you for taking time out of your Sunday evening to go over the logs for me, at least we can point fingers more accurately at the GPU now and PCS can get this sorted for me (their service has been wonderful and very fast throughout the whole RMA)
Now...what are the chances of finding another 3070 in stock
I did point them to this thread in the RMA and I'll do so again as it has a lot more information than before - I'll be calling them in the morning.
Thank you for taking time out of your Sunday evening to go over the logs for me, at least we can point fingers more accurately at the GPU now and PCS can get this sorted for me (their service has been wonderful and very fast throughout the whole RMA)
Now...what are the chances of finding another 3070 in stock
ubuysa
The BSOD Doctor
Morning. I just took a look at your drivers file that you kindly provided. Although I'm quite sure your recent BSOD is a hardware error there are some drivers you have that raise some red flags for me...
First off, you have Bullguard installed. I don't think Bullguard caused your latest BSOD but we know from experience on here that Bullguard does cause BSODs and all manner of other issues too. You don't need it, Windows Defender is plenty good enough and it's free (you'll have to pay for Bullguard). My advice is to get rid of Bullguard. Permenantly.
You have a number of Logitech drivers installed. Logitech make great hardware and less reliable software. I would advise only installing Logitech software that you absolutely need (for customising mouse and keyboard for example) and avoid all non-essential Logitech software. I just don't trust it.
First off, you have Bullguard installed. I don't think Bullguard caused your latest BSOD but we know from experience on here that Bullguard does cause BSODs and all manner of other issues too. You don't need it, Windows Defender is plenty good enough and it's free (you'll have to pay for Bullguard). My advice is to get rid of Bullguard. Permenantly.
You have a number of Logitech drivers installed. Logitech make great hardware and less reliable software. I would advise only installing Logitech software that you absolutely need (for customising mouse and keyboard for example) and avoid all non-essential Logitech software. I just don't trust it.
Good morning
I uninstalled Bullguard when I originally got the PC, when they sent it back to me after the RMA it was a fresh Windows re-install and it was back on again, I just hadn't got around to uninstalling again, it was on the to-do list but as it was happening previously without it, I'm presuming it isn't related.
I have a Logitech keyboard, I just installed the 'Gaming Software' program to customise the G keys I have on the keyboard as I use them frequently. I haven't installed any other drivers/software from Logitech and/or the keyboard. I don't know if there is a more 'lightweight' software Logitech do that means I can customise the G keys?
I uninstalled Bullguard when I originally got the PC, when they sent it back to me after the RMA it was a fresh Windows re-install and it was back on again, I just hadn't got around to uninstalling again, it was on the to-do list but as it was happening previously without it, I'm presuming it isn't related.
I have a Logitech keyboard, I just installed the 'Gaming Software' program to customise the G keys I have on the keyboard as I use them frequently. I haven't installed any other drivers/software from Logitech and/or the keyboard. I don't know if there is a more 'lightweight' software Logitech do that means I can customise the G keys?