BSOD booting up Laptop, 0x0000003b, ntoskrnl.exe


  1. Posts : 2
    Windows 7 64 bit
       #1

    BSOD booting up Laptop, 0x0000003b, ntoskrnl.exe


    I have had a problem booting up my laptop with a Blue Screen of Death error "0x0000003b" caused by "ntoskrnl.exe"

    Attached is the DMP file and my system info. I apologise if I have done anything wrong, I am a noobie here.

    Thanks in advance.
    - Quanny.
      My Computer


  2. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #2

    Hello Quanny and welcome to Sevenforums.

    * When did you start experiencing these crashes?
    * What diagnoses have you done so far?
    * Is your computer still available for RMA?


    BSOD Analyse

    Code:
    **************************Mon Aug 27 17:34:57.076 2012 (UTC + 2:00)**************************
    BugCheck 3B, {c0000005, fffff8000354623c, fffff880058f8d70, 0}
    Probably caused by : ntkrnlmp.exe ( nt!PsCheckThreadCpuQuota+8c )
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Sun Aug 12 16:24:34.614 2012 (UTC + 2:00)**************************
    BugCheck A, {ff, 2, 1, fffff800034fccf2}
    Probably caused by : tcpip.sys ( tcpip!InitializeEndpointContextFromParentContext+18 )
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Thu Jun 23 13:25:49.195 2011 (UTC + 2:00)**************************
    BugCheck 3B, {c0000005, fffff800032c64b4, fffff88008210d60, 0}
    Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceExclusiveLite+54 )
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

       Tip
    If you're having a custom customization layer on your Aero, it's likely to get restored to default.


    Press Start | search 'cmd' | Right-click it
    | open as Admin | type SFC /SCANNOW

    SFC /SCANNOW Command - System File Checker

    Most important, answer the questions and I'll dig your issue. :)

    Best Regards,
    Frederik.
      My Computer


  3. Posts : 2
    Windows 7 64 bit
    Thread Starter
       #3

    Hello, Frederik. Sorry for the lateness of my reply.

    I started experiencing these crashes last week, however, it appears I had one last year and I completely forgot.

    Since the creation of this thread, I haven't experienced a crash since the latest one I posted (that happened on August 27th). I looked into other user's problems and removed drivers that I haven't been using or that are old. I also removed any programs that I did not use and tried to limit the number of programs that would start up when Windows boots up.

    After doing some more searching around, I downloaded a program called BlueScreenView, but I was totally confused as to what was happening, to be honest. Looks the same as you have found.

    I have had this laptop for around two years now and it isn't under warranty anymore, so no longer under RMA, I believe.

    I have also ran the scan you suggested, and the results state that "Windows Resource Protection did not find any integrity violations."

    Is there anything else you can recommend?

    Thank you.
    - Quanny.
      My Computer


  4. Posts : 2,393
    Microsoft Windows 7 Ultimate: x64 (SP1)
       #4

    Alright I see. Let's enable driver verifier.

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
    You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

    For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
    For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

    Also, to ensure that you can recover, here's another couple of additional steps:
    - Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
    - Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
    Picture of a BSOD

    Then, here's the procedure to run Driver Verifier:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    Best Regards,
    Frederik.
      My Computer


 

  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 14:39.
Find Us