Search results

  1. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    alright, so im gonna see about getting a new hard drive then, plus that does make a bit more sense, because from what ive heard online windows wouldn't boot up if ntoskrnl was corrupted. thanks, any more advice?
  2. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    in that case, would replacing the hard drive and transferring the files fix the issue? or would transferring the files just continue the issue?
  3. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    i ran another chkdsk scan and that was what i got from it
  4. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    Update: i decided to not go to the "geeksquad" just yet, and i ended up getting my pc to turn on again, here are the screenshots you wanted Axe0:
  5. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    My computer doesn’t want to turn on right now... I turned it on to do what ace 0 said, but it didn’t “turn on” the fans and lights were on, the monitor stays in sleep mode(same with any monitor I plug in) and whatever mouse or keyboard I use don’t seem to have any affect. So I’m probably gonna...
  6. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    Looking at some of the other dump files it also shows that nvlddmkm.sys+1372e2 and Hal.dll+54d1 may also be part of the problem causing the watchdog violation, I’m not sure if these are drivers I have to update/reinstall, or what, but if they are could I also get assistance with were to update...
  7. E

    Watchdog violation BSOD, possibly caused by ntoskrnl.exe

    I have been getting BSOD while using graphically extensive programs, when checking the dump file with blue screen view the only thing that is a different color is a red ntoskrnl.exe+18ae3c . I have been working on troubleshooting my pc for 3 days now, and the ntoskrnl seems to be the only thing...
Back
Top