Is this a pcspecialist system?HI:
The above error message is driving me crazy.
I have extracted the data requested from the BSOD sticky-thread entry (event logs, minidump, etc.), but I do not know how to upload the files to this forum, so I am stuck.
Can you advise?
Thanks.
And the specs?Thanks for the replies, guys.
Yes, my laptop is from PCSpecialist (it's about my 3rd or 4th, in fact).
I haven't uploded files to a filesharing site before, so am now going to Google Drive to try to do just that.
Done ( I think):
Windows key removed. Anything else to delete? From where to where?Just the top specs list from your PCS account is fine.
But you'll want to edit it to remove your Windows key, in case someone feels like pilfering it.
You can leave the rest in, but normally we only need the build info from your PCS account...so nothing from the 2nd part of the post (the 'detailed specification' section) as that tends to be from the a sales page listing possible configs and not the actual PCS configuration that you bought.Windows key removed. Anything else to delete? From where to where?
Thanks, Ubuysa - kernel dump uploaded to Google Drive in the folder named "PCSpecialist" (where the other data is).Thanks for the uploads but when uploading to Google Drive (or similar) you need to make the files public ('anyone with the link can access').
However, the 0x101 CLOCK_WATCHDOG_TIMEOUT BSOD cannot be fully debugged with the minidumps we typically ask for, we'll need the full kernel dump. It's the file C:\Windows\Memory.dmp. Please upload that to Google Drive - and make it public.
The 0x101 BSOD happens when a processor fails to respond to a clock synchronisation request. These requests are sent out regularly between the processors in order to keep everything in synch, if one processor doesn't respond then you get this BSOD. A bad driver that 'blocks' a CPU at an elevated IRQL can stop it responding to the clock synchronisation interrupt - the dump will tell us if that's the case - but I need to warn you that these BSODs generally turn out to be a bad CPU.
It's not a folder...it's a file called 'memory.dmp' in the Windows folder.There is no C:\Windows\Memory folder.
The folders jump from Media to Microsoft.NET
Have you serviced it since you've had it? Any performance laptop requires a repaste once a year to keep thermals in normal ranges, otherwise it will start overheating and that can lead to degredation of silicon.The BSOD appeared again & did its thing. When it finished I immediately checked in C:\Windows - but there was no memory.dmp file as shown in the post above. Definitely not there.
A new file had been created in C:/Windows/Minidump - but it would not let me zip it ("File not found or no read permission"). No joy with WinRar or 7-Zip either.
If, as suggested in an earlier post, the problem is likely to be a bad CPU, I might as well just have to put up with a BSOD every 2-3 days. It's not the end of the world. I don't want to waste any more of your time.
You checked optional updates? Not windows update? A lot of people don't realise how drivers are managed in windows.Everything is up-to-date re drivers, etc - first thing I checked.