• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

BSOD (Dpc_Watchdog_Violation)

Status
Not open for further replies.

Exyztence

PCHF Member
Apr 11, 2020
126
0
27
Hi there!
about 2 weeks ago I had a thread in this forum and I wrote with Phillpower2. it would be great if he could help me here too, because he knows more about the subject.
Currently, I am without my GPU, which is on RMA.
The BSOD started again. What I think, is that they are related to IDE ATA/ATAPI controllers. When In device manager I go right-click it, then properties and driver details, I've got only ,,storahci.sys" listed. As I read, most of the people have iaStorA.sys, which I am missing. It is in system32/drivers but I don't see it in this list. I also read that iaStorA.sys is related to hal.dll and ntoskrnl.exe which were causing my BSOD when I checked minidump in ,,bluescreenview" app. I also wanted to install Intel RST, but it says ,, wrong machine type".
Could you please help me what should I do?
Below is .zip with 3 minidumps of BSOD that occurred today.
Greetings,
Oliwier.
 

Attachments

  • minidumps.zip
    1.2 MB · Views: 5
If you wish to continue troubleshooting this it can be done at your previous thread here which you abandoned, the thread can be reopened by request but will only remain open on two conditions, you stick to what suggestions are made and keep your thread updated, slip up on either and the thread will be closed permanently, we are here to try and help people not run around after them continually asking for an update.

Fwiw, the three crashes were caused by the exact same thing as in your previous thread so you obviously haven't taken any of the previous advice on board :(

This duplicate thread is closed.
 
Status
Not open for further replies.