none
ntoskrnl.exe problem (blue screen of death) RRS feed

  • General discussion

  • hello

    can i delete ntoskrnl.exe from my computer (i use windows 8.0=8) then replace a healthy ntoskrnl.exe

    from other computer using windows 8.0=8  ?


    Wednesday, December 4, 2013 7:02 AM

All replies

  • can anyone help me ???????
    Wednesday, December 4, 2013 11:57 AM
  • Why do you think the kernel is unhealty?  Have you tried a system rollback to fix this?


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Wednesday, December 4, 2013 12:14 PM
  • Why do you think the kernel is unhealty?  Have you tried a system rollback to fix this?


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    I'm 100% sure that my ntoskrnl.exe file is corrupt.

    I just want to understand that deleting this file is dangerous for my pc or not  :)

    Wednesday, December 4, 2013 4:42 PM
  • Stating that you are 100% sure the kernel is corrupt is pretty bogus, tell us how, it is rarely a corrupted kernel.

    If you want to try this, copy the file to the disk with a different name, such as xxxkrnl.exe and then follow the directions  given here for how to specify a different kernel http://msdn.microsoft.com/en-us/library/windows/hardware/ff542286(v=vs.85).aspx


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Wednesday, December 4, 2013 4:49 PM
  • thanks
    Wednesday, December 4, 2013 7:05 PM
  • what is the specific bugcheck? run !analyze -v on the memory dump file to show specifically what is going on. 99.9999% of the time it is not the kernel, rather a driver error.

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, December 4, 2013 7:21 PM
  • what is the specific bugcheck? run !analyze -v on the memory dump file to show specifically what is going on. 99.9999% of the time it is not the kernel, rather a driver error.

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    thanks
    Thursday, December 5, 2013 8:34 AM