I Found the Problem i just need alittle help please.

Page 1 of 2 12 LastLast

  1. Posts : 29
    win 7 64 ultimate
       #1

    I Found the Problem i just need alittle help please.


    Hi people

    After constant crashing at random,i used the verifier contained in windows which allowed me to find that the ntoskrnl driver is the culprit of random crashing bsod.

    What i would like to know is....

    How do i replace this file once going into repair with the windows 7 dvd in the drive?I know how to get to the repair screen but i dont know what to type.

    I have used google and can only find a soultion with xp...

    This is what i typed in once i got the command console up

    C: \windows
    C: \windows\system32
    expand f:\i386\ntoksrnl.ex_ c:windows\system32


    I got this far but once i hit enter to overwrite the file it says f:\i386\ntoskrnl.ex_ cannot be opened.

    I also tried bootcfg /rebuild but windows command prompt said bootcfg ?


    Can somebody show me exactly the correct procedure to type please as its taken me ages to find the problem,now all i need to do is fix it.
    Thanks
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    v3teran said:
    Hi people

    After constant crashing at random,i used the verifier contained in windows which allowed me to find that the ntoskrnl driver is the culprit of random crashing bsod.

    What i would like to know is....

    How do i replace this file once going into repair with the windows 7 dvd in the drive?I know how to get to the repair screen but i dont know what to type.

    I have used google and can only find a soultion with xp...

    This is what i typed in once i got the command console up

    C: \windows
    C: \windows\system32
    expand f:\i386\ntoksrnl.ex_ c:windows\system32


    I got this far but once i hit enter to overwrite the file it says f:\i386\ntoskrnl.ex_ cannot be opened.

    I also tried bootcfg /rebuild but windows command prompt said bootcfg ?


    Can somebody show me exactly the correct procedure to type please as its taken me ages to find the problem,now all i need to do is fix it.
    Thanks

    I can pretty well asure you it is not ntoskrnl that is causing your crashes. I cant tell you what does until I have the actual DMP file created when the computer crashed. ise these to find and upload it to us. https://www.sevenforums.com/crash-loc...d-problem.html

    Ken
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #3

    To add to Ken's post, ntoksrnl.exe is a critical Windows system file, and all bugs in it were most assuredly gotten out before the Betas even.

    ntoksrnl.exe is the default file Windbg, BlueScreenView, and WhoCrashedIt blame.
      My Computer


  4. Posts : 29
    win 7 64 ultimate
    Thread Starter
       #4

    Hi guys thanks for replying,in regards to your response are you sure its not ntoksrnl?the reason i say this is beacause when i used the verifier and i enabled the ntoksrnl on reboot it bsod,also when i bsod it shows ntoksrnl in bluescreenviewer.

    i have uploaded a dmp file.
      My Computer


  5. Posts : 29
    win 7 64 ultimate
    Thread Starter
       #5

    Here is also another dump file that kept Bsod everytime i booted into windows once i enabled the ntoskrnl in verifier,the only way to boot back into windows was to "use last known good configuration"

    Im no expert but it seems to me its the ntoskrnl but im open to suggestions and learning
    thanks
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    v3teran said:
    Hi guys thanks for replying,in regards to your response are you sure its not ntoksrnl?the reason i say this is beacause when i used the verifier and i enabled the ntoksrnl on reboot it bsod,also when i bsod it shows ntoksrnl in bluescreenviewer.

    i have uploaded a dmp file.
    Absolutely not ntoskrnl. Blus screen view often gives "incomplete" results which is one reason we dont use it, nor who crashed.

    One thing I notice is you have some old drivers that in themselves could be the casue of the crash. They are:

    Code:
    ffff880`01a00000 fffff880`01a14380   pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
    fffff880`08382000 fffff880`0838d000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`0883b000 fffff880`08841000   RTCore64 RTCore64.sys Wed May 25 02:39:12 2005 (42941D90)
    fffff880`01a00000 fffff880`01a14380   pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
    fffff880`0883b000 fffff880`08841000   RTCore64 RTCore64.sys Wed May 25 02:39:12 2005 (42941D90)
    fffff880`08382000 fffff880`0838d000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    Those should be updated.

    Ken
      My Computer


  7. Posts : 29
    win 7 64 ultimate
    Thread Starter
       #7

    I have driver genius,but it doesnt detect these drivers when i run a refresh,i have found RTcore 64,where do i put it?
      My Computer


  8. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #8

    I concur with Ken and Jonathan. I would be shocked if ntoskrnl was the real cause.
      My Computer


  9. Posts : 29
    win 7 64 ultimate
    Thread Starter
       #9

    CarlTR6 said:
    I concur with Ken and Jonathan. I would be shocked if ntoskrnl was the real cause.
    ok so where do i put the rtcore64,i have downloaded it,where do i put it?
      My Computer


  10. Posts : 29
    win 7 64 ultimate
    Thread Starter
       #10

    if i reinstall windows will that fix it?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:48.
Find Us