BSOD Stop Code: 0x03b


  1. Posts : 3
    Windows 7 (64bit)
       #1

    BSOD Stop Code: 0x03b


    Hi,

    I've had an HP Pavilion dv6-3124nr notebook for about a year and a half. After about 4 months, I started getting the BSOD with the System Service Exception stop code of 0x03b. I recovered the sytem per instructions from HP and it seemed to stop. About two or three months ago, I started getting it again during random activity. At one point it noted a hardware issue so I stopped using my Microsoft wireless mouse. It seemed to have stopped. Now, I'm running in Safe Mode with Networking because the computer won't stay up for more then 10 minutes otherwise without the same BSOD stop code.

    I'm attaching the minidump files as per the forum instructions and I've given you as much information about the system as I know how to. Hope you can help......I'm running out of ideas as I've already consulted with all the computer "gurus" I know.

    Thanks
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2


    These crashes were caused by memory corruption/exception (Cx05) probably a driver.
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have a Raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5-7 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.


    RAM - Test with Memtest86+






    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.

    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).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - 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 "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - 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.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    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.
    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


    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.

    Thanks to JCGriff2 & Usasma.

    Sysnative Forums

    Driver Reference Table (DRT)


    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
      My Computer


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

    Please follow JMH's suggestions in addition please remove IObit as its filemonitor.sys is related to your crashing.
      My Computer


  4. Posts : 3
    Windows 7 (64bit)
    Thread Starter
       #4

    Thank you for the quick reply. I must admit, I'm not familiar with some of what you referenced. What is a Raid? How do I know if I'm overclocking something and how do I STOP it?

    Once I answer these questions and continue on with your recommended tests, how do I go about determining the good slots verse the bad ones? Do I have to physically remove cards from the computer? Sorry, these might be stupid questions; but I want to make sure I don't waste a ton of time doing this troubleshooting only to find out I can't fix the problem anyway.

    Thanks
      My Computer


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

    Scottie36 said:
    Thank you for the quick reply. I must admit, I'm not familiar with some of what you referenced. What is a Raid? How do I know if I'm overclocking something and how do I STOP it?

    Once I answer these questions and continue on with your recommended tests, how do I go about determining the good slots verse the bad ones? Do I have to physically remove cards from the computer? Sorry, these might be stupid questions; but I want to make sure I don't waste a ton of time doing this troubleshooting only to find out I can't fix the problem anyway.

    Thanks
    RAID, Raid - Wikipedia, the free encyclopedia

    If you havent changed anything chances are you arent overclocking, so dont worry.

    RE: Memtest.

    If you arent under warranty, and you dont have a laptop, then when you test the ram and find a good one, use it to test each motherboard slot.

    Memtest does need to run for 6-8 passes so it does take a long time but is worth it.

    Let us know if you need help
      My Computer


  6. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #6
      My Computer


  7. Posts : 3
    Windows 7 (64bit)
    Thread Starter
       #7

    Additional BSOD crahses


    Hello all,

    Well, it's been several months since I've had a problem as described above. Once again, I'm getting the 0x03b System Service Exception BSOD crashes. They come fairly quickly after signing on to my user account and everything booting up. I am and have been using the computer in safe mode which has allowed me to continue using it. Unfortunately, Office 2010 won't run because some of the files don't start in Safe Mode. I know I had sent in a minidump file with the last serious of posts in this thread. If that would be helpful in diagnosing, please send instructions on how to do that again.

    If anyone can give me some input into this matter, it would be very helpful. My guys here at work all seem to think it's a hardware issue since the computer runs fine if Safe Mode.

    Any help will be appreciated

    Thanks
      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 19:37.
Find Us