Two Different BSOD Error Codes, Need Urgent Help


  1. Posts : 5
    Windows 7 Home Premium 64bit
       #1

    Two Different BSOD Error Codes, Need Urgent Help


    I use my laptop for photo/video work and internet use, but I've been having a ton of problems recently. In January, I did a full system reformat, but when it started installing automatic updates, the computer would either freeze or go to the blue screen. I then started putting the computer into hibernate most of the time (at night and such).

    It had been working for a while, but I would still occasionally get a blue screen, which would be fixed by a system restore point.

    A few days ago, I installed one font for my photo work, and the computer froze. I turned the laptop off and back on, and immediately got a blue screen, with the error code ending in 3B. I've attached a screenshot of that particular blue screen. The screenshot is of the old blue screen, NOT the one I got today.

    Yesterday, a friend advised me to run 'chk dsk', which I did. Afterward, the laptop worked PERFECTLY all day. I shut it down and went to sleep.

    This morning, I woke up, turned on the laptop, and had a NEW blue screen, with the error message ending in 0A (that's a zero). I'm now running in safe mode with networking, because every time I try to run in normal mode, I get that blue screen.

    I followed the directions on posting a BSOD issue, but I can't run step three. I've also enclosed a screenshot of what shows up during that, as an attachment.

    Finally, I've enclosed the zip file of the dump. It's very important that I get this fixed, as I'm unable to do my work. Thank you.

    I'm running Windows 7 Home Premium on an eMachines laptop. It is an OEM, it was already installed on the system when I purchased the laptop.
    Last edited by epwbigdaddy; 17 Mar 2012 at 19:19. Reason: Left some info off
      My Computer


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

    Two issues

    1-Symantec (causing memory exceptions)

    Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


    http://us.norton.com/support/kb/web_...080710133834EN

    Microsoft Security Essentials - Free Antivirus for Windows

    * Did you run a FULL SYSTEM scan with Malwarebytes?


    2-SP-1

    Please run the System Update Readiness Tool (SURT) and then update to SP-1


    32 Bit

    Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

    64 Bit

    Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details


    Now update to SP-1

    Learn how to install Windows 7 Service Pack 1 (SP1)









      My Computer


  3. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    I haven't actually run a Malwarebytes check since the reformat, as far as I can recall.

    Also, I noticed an error, I'm actually running 64bit, NOT 32bit. That's my mistake. However, one of the steps you've suggested, I can't do. It says it won't work in safe mode, but I can't run the computer in normal, so I don't know what to do.

    Here's a screenshot of the error message, and a screenshot of my computer specifics.
      My Computer


  4. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    I was following step one, removed Norton, and installed Windows Security Essentials. After the restart, it opened in normal mode, and started updating. In the middle of the update, I got a new blue screen, with the error code ending in 1E. Here is a screenshot.
      My Computer


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

    epwbigdaddy said:
    I was following step one, removed Norton, and installed Windows Security Essentials. After the restart, it opened in normal mode, and started updating. In the middle of the update, I got a new blue screen, with the error code ending in 1E. Here is a screenshot.
    Usually when there is a crash there is a DMP file. We need them each time.
      My Computer


  6. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    zigzag3143 said:
    epwbigdaddy said:
    I was following step one, removed Norton, and installed Windows Security Essentials. After the restart, it opened in normal mode, and started updating. In the middle of the update, I got a new blue screen, with the error code ending in 1E. Here is a screenshot.
    Usually when there is a crash there is a DMP file. We need them each time.
    Sorry about that. I'm running the dump file program again, I'll post the updated folder in a few minutes when it finishes.
      My Computer


  7. Posts : 5
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Here is the updated zip file.
      My Computer


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

    Three of the ones from 3/17/12 are related to memory exceptions.





    These crashes were caused by memory corruption/exception (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 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 or 6 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.

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

    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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - 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.

    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.
      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 18:27.
Find Us