Intermitant BSOD on shutdown w autorestart. ntoskrnl.exe? portcls.sys?

Page 1 of 2 12 LastLast

  1. Posts : 8
    windows 7, x64, home premium
       #1

    Intermitant BSOD on shutdown w autorestart. ntoskrnl.exe? portcls.sys?


    Intermittant BSOD on shutdown with auto-restart. BlueScreenView seems to flag ntoskrnl.exe & portcls.sys. I am uncertain how to deal with this.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    slowrobert said:
    Intermittant BSOD on shutdown with auto-restart. BlueScreenView seems to flag ntoskrnl.exe & portcls.sys. I am uncertain how to deal with this.
    Hello slowrobert.

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip





    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 8
    windows 7, x64, home premium
    Thread Starter
       #3

    Hello Arc,

    Thank you. Starting your suggestions.

    ...

    a few minutes later after starting Verifier.exe

    ...


    The computer would not boot, tried twice, did see the BSOD briefly.
    Disabled Verifier.exe. Including the Diagnostics file from today.
    Last edited by slowrobert; 24 Jan 2013 at 17:05.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Probably the verifier enabled crash dumps are not recorded. Before doing anything else, I would suggest you to try DV one more time. Just make it sure that you are not selecting any "microsoft" and "unknown" provided drivers. We can expect that it should work this time.

    Also free up the startup.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept the restart.
      My Computer


  5. Posts : 8
    windows 7, x64, home premium
    Thread Starter
       #5

    After multiple attempts at starting Verifier.exe without a crash, I finally found 3 entries from 'Toolwiz' that didn't want to be verified and were causing all the crashes.

    I am now running Verifier with all others (minus Microsoft) checked.

    However, as the shutdown BSOD has been so rather infrequent and I do not know how to replicate it, I doubt that Verifier will catch it in the act any time soon.

    Would a list of the drivers help?
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    slowrobert said:

    Would a list of the drivers help?
    We already have the list of your all installed drivers. And, any of these drivers may cause a crash, as usual. So we depend on driver verifier to a great extent.
      My Computer


  7. Posts : 8
    windows 7, x64, home premium
    Thread Starter
       #7

    Ran diver verifier all day yesterday, no BSOD upon shutdown.

    These BSOD's began shortly after puting my new SSD, so I was concerned that it may have been the problem.

    I just checked the install date of the Paragon software, it was installed on the 10-Jan-13, the first of these similar looking BSOD's occured on 1-Jan-13.

    Perhaps I should just run the computer normally (without Verifier...) until I discover what actions lead to the crash so I can replicate it on demand.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Do it. And check for any firmware update for the SSD, if available.
      My Computer


  9. Posts : 8
    windows 7, x64, home premium
    Thread Starter
       #9

    I will, and thank you.
      My Computer


  10. Posts : 8
    windows 7, x64, home premium
    Thread Starter
       #10

    Putting things back as they were; MSCONFIG items on, Verifier settings deleted; turned off the system and before restarting did 3 passes of Memcheck just to be certain (no errors).

    I noticed right away my temp logger, OpenHardware Monitor showing 0C for my cores. I checked with CoreTemp.exe and hwmonitor; all show 0C. The case temps show up, around 27C idle currently.

    Simply restarting the system did not help. No other changes made.

    I have noted that other posts mention something about unlocked chips not showing temp (running 4 cores on a 3 core rated chip); but have never not seen the core temps show up. They were showing up during the Driver Verifier test. Should I sart another thread?
      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 06:27.
Find Us