Recent content by PHaRcYDe

  1. P

    BSOD points to NTOSKRNL.EXE

    In terms of updating and removing there's really not much I can do. I have removed Intel Rapid Storage so that should take care of the Intel Management Engine Interface. The last time I updated my Broadcom Network Adapter, it put a driver on my computer that that Usama told me to remove. I have...
  2. P

    BSOD points to NTOSKRNL.EXE

    Update Here's the minidump file you requested. For some reason it appears as an invalid file when adding it to the uploader, I have provided a mediafire link instead. I'll continue to test the hardware when I have more time on my home PC. 110914-5343-01
  3. P

    BSOD points to NTOSKRNL.EXE

    Update I ran a couple verifier passes, one with third party drivers enabled and one with Windows drivers enabled. The third party drivers passed, Windows did not. Correct me if I'm wrong but doesn't a driver Verfier failure on Windows drivers normally point to a hardware failure? I will be...
  4. P

    BSOD points to NTOSKRNL.EXE

    Unfortunately I've ran into another NTOSKRNL.EXE error. There's no possible way that's it's ScpVBus related as this is a fresh install. I have included the minidump, let me know if you require the full file.
  5. P

    BSOD points to NTOSKRNL.EXE

    Now that is very odd. I downloaded DS4Windows some time back. I wasn't aware it was using drivers for the DS3. First time I'm hearing about motioninjoy but it looks like it's DS3 compatible only. Unfortunately I'll never if that was the cause, but I know what to avoid in the future. I finally...
  6. P

    BSOD points to NTOSKRNL.EXE

    Here's a link to the full crash dump file. MEMORY
  7. P

    BSOD points to NTOSKRNL.EXE

    Rather then edit the last post I'll leave it to reflect the issue I had. I did manage to get a crash dumps to write to the C:\Windows\Minidump This is from the most recent crash, hopefully it's the full file and not partial. Zipped and attached. Edit: About 90 minutes after this post I...
  8. P

    BSOD points to NTOSKRNL.EXE

    Hello. Sorry it took so long to get back, I was out of town for the weekend. Unfortunately there's no way for me to upload the full dump file because C:\Windows\Minidump is empty. This might explain the results of the last SF Diag run. The only thing I can think is to attempt to force the...
  9. P

    BSOD points to NTOSKRNL.EXE

    I believe I managed to get the crash dumps up and running again. Here's the zip of the SF tool, if you need the full /memory dump let me know. The Hardware Diagnostics are still showing a perfectly functioning drive.
  10. P

    BSOD points to NTOSKRNL.EXE

    Unfortunately after update Tuesday, crash dumps no longer function properly, this is probably just my unique circumstance. I'm not sure if they aren't being generated or simply aren't be saved in the right place. The SF Diagnostics Tool and even programs like WhoCrashed aren't seeing anything...
  11. P

    BSOD points to NTOSKRNL.EXE

    I understand, I left my CPU at stock after the second pass.
  12. P

    BSOD points to NTOSKRNL.EXE

    I've ran 2 hour passes on Prime95 on both my OC'd settings 3770k @ 4.6Ghz and the stock 3.5Ghz with no issues. Likewise, Memtest and Furmark have all cleared multiple passes.
  13. P

    BSOD points to NTOSKRNL.EXE

    Update The Asus and TuneUp drivers have been removed. Also the btw12cap.sys (Broadcom) has been removed. I was unable update CORK70.sys (Corsair Vengeance K70) as the only firmware update available is the same update currently in used. As for the CORM40.sys that is the Corsair Raptor M40...
  14. P

    BSOD points to NTOSKRNL.EXE

    Driver Verifier easily recreates the crash but only points to NTOSKNRL.EXE, sadly it won't give me the driver responsible. A virus scan will also cause a BSOD, both in Windows Defender and Bitdefender (now removed). Unfortunately I'm unable to see what was scanned that caused the failure. I've...
Back
Top