Recent content by tony359

Guess I poked a sensitive area here

zbook, I know what WDC does and I know we are testing drivers to see if we can find a misbehaving one. I've been diligently following your instructions, I would like some feedback. Why are we testing different combinations, what did you see in the logs I sent you that made you issue a...

I appreciate you're trying to help me but you gave me very little feedback. "There are tests that are used to troubleshoot" does not qualify as feedback in my book. I've done almost 22 separate tests and before doing 5 more tests, I'd like to know more on the process happening behind the...

I'd love to look more into my issue but I'd like some feedback while we proceed.

I have but I'm not sure I am willing to continue forever without any feedback on your end. I appreciate your help though.

but you're not telling me anything about the process, what you're seeing, what the purpose of the tests is. Why the secrecy?

While I appreciate your help, where are we with the troubleshooting? Because I've lost count on how many tests I've done. Yes, I know you're not Microsoft but I feel there is a threshold where at some point I'll go out and buy another laptop 😀 What are you seeing? It seems that my Windows is...

test results. Microsoft OneDrive You didn't say but I used the GUI this time, selecting the tests you listed. I've also selected all drivers. Last group wasn't a verifier BSOD it was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Thanks but that is not what I meant, sorry for not being clear. If there is NO BSOD, once I reset WDV via terminal, do I need to reboot before running the next batch of WDV settings?

Thanks - I forgot to mention that the first BSOD which happened about 1 minute after I got safely into Windows, happened when I hit FN-Q which is the Lenovo hotkey to change the power settings. I could see the laptop was struggling a bit because of Verifier so I wanted to switch to a performance...

@zbook Test results here, the txt file has notes inside. Let me know if any questions. https://1drv.ms/u/c/0f215fbb023f1ee9/IQAd0dW0V5XBT5ZPlZLTOGHpATW927tZFlLv-LCOzbueIVc?e=Xhxanl

What I am trying to do is to find out whether a DUMP has been written after a BSOD or not. I don't want to run V2 eight times to then discover "Windows failed to write the dump each time". So My question is: if a dump is created is created in C:\Windows\Minidump correct? If I don't see a new...

This is what I am trying to understand.

Sorry @zbook I am not following you. I didn't restore the laptop. I was able to boot by just getting into safe mode and disable WDV via terminal. What I said was that the BSOD screen would remain on the below screen and the laptop wouldn't restart by itself so after many minutes I power cycled...

where can I see whether Windows has managed to create a dump - so I don't waste time creating V2 logs if there is nothing to see? Edit: I found it. But that is reported when I reboot in SAFE mode, what has that to do with the actual BSOD? And after that error, I see a "dump file generation...