locked
Windows 7 x64 Sudden BSOD Issues RRS feed

  • Question

  • Hello folks,

    Thanks ahead of time for taking a look at my error logs and hopefully being able to pinpoint my issue.  I have suddenly (as of the last 3 days) been getting major BSOD issues once my computer has been on a little while.  The system will suddenly stop loading any executables, aero will crash, and then any programs running will soon crash.  I saw it coming this last time and attempted to shut down the computer, which resulted in an instant BSOD crash. 

    I have previously rebooted in safe mode and done a clean boot (i.e. I disabled all non-microsoft processes).  It has not solved my issue. 

    Here's the link to my public .zip of my log files.  I have other files saved also that have been created over the past 2-3 days in that directory that I can upload of necessary too. 

    http://cid-671ba6b52469707b.office.live.com/self.aspx/.Documents/Error%20logs.zip

    Thank you much for any assistance you can provide,

    sebastion

    *edit*

    Wow,

    So I restarted, and had some issues getting it to boot.  I finally got in, but I got a windows services error, Aero is NOT loaded, and I only have 7 shortcuts on the desktop.  Basically, desktop did not load.

    Just got some errors that said Microsoft Shell Hardware Detection stopped working, as did Microsoft Windows Search Indexer. 

    Wish I knew why this was suddenly happening.  *sigh*

    • Edited by s3basti0n Monday, January 24, 2011 8:22 AM add info
    Monday, January 24, 2011 3:47 AM

Answers

All replies

  • Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

    Cause

    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    http://msdn.microsoft.com/en-us/library/ff558949%28VS.85%29.aspx


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Access violation

    PROCESS_NAME:  SearchProtocol

    nt!ObpCloseHandleTableEntry+0x3e

    Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2][3] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [4], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    Also run the command prompt with admin rights [5] and run chkdsk C: /r /f.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download
    [3] http://forum.imgburn.com/index.php?showtopic=61
    [4] http://www.cpuid.com/softwares/cpu-z.html
    [5] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Wednesday, January 26, 2011 1:29 PM
    • Marked as answer by Cloud_TS Tuesday, February 1, 2011 10:00 AM
    Monday, January 24, 2011 1:35 PM
  • Since I have 12 gigs of RAM in the computer, will I need to run multiple versions of the memtest?  Or will running it off the new bootable CD take all of that into account?

    A friend advised me to try this:

    I analyzed your data, and your crash was due to a driver fault (video). I would try to uninstall your video drivers completely, then reinstall the latest ones for your card. If you still have an issue, it's going to likely be hardware. I would expect the video card would be getting too hot, or some other hardware issue with it (such as video memory). Don't suppose it's under warranty?

    Is that reasonable to try before the above?  Or shall I just move directly to the memtest and CPU-Z stuff?

    Monday, January 24, 2011 7:37 PM
  • Is that reasonable to try before the above?  Or shall I just move directly to the memtest and CPU-Z stuff?

    I can't see anything related to Video driver in the dump. The crash ist often caused by graphic card driver,s but not in your case.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Monday, January 24, 2011 8:01 PM
  • Thanks for the quick reply. I just made the ISO disk, so I will leave that in overnight to run the memtest (hoping it starts automatically when I attempt to reboot with the CD in the tray... if not I'll have to figure out how to specifically run it). Is there merit in doing the CPU-Z tests prior to the memtest before I run it overnight? Or is the order of the troubleshooting important? Thanks again for all your help as I work through this issue.
    Tuesday, January 25, 2011 4:42 AM
  • the ordner is not important. I only want to know the RAM timings.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 25, 2011 3:22 PM
  • Okay, I ran the memtest86+ overnight (6 hours 45 min and counting) with over a million errors. Now I'm wondering how to evaluate the results to determine the exact cause of my errors. Google-fu tells me that interpreting the results in and of itself isn't really doable and that I should simply open up the box, remove 3 of the 4 sticks of RAM, and test each stick individually, is this what you suggest?
    Tuesday, January 25, 2011 3:30 PM
  •  that I should simply open up the box, remove 3 of the 4 sticks of RAM, and test each stick individually, is this what you suggest?
    yes, this is the way to find the damaged RAM module.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, January 25, 2011 4:38 PM
  • I'll swap sticks out tonight and see if I can find the trouble module.  Is there any issues/potential concerns with BIOS settings or something I'm not thinking about if I pull 2 sticks out at a time to trouble shoot?  I have 4 sticks right now, so I planned on removing 2, running the memtest again, and then swapping sticks in and out (maintaining 2 at any given time) to determine which module is bad, or if the issue is some other hardware.
    Wednesday, January 26, 2011 12:45 AM
  • So tonight I was able to finally sit down and fiddle with the RAM in my box. I managed to find 1 module that was routinely causing errors. I'm currently running another memtest86+ with 5 of the 6 Corsair XMS3-1333 2048MB modules in just to ensure that they are error free. I even went as far as swapping one of the "good" sticks into the slot where the problem stick had been to ensure it was actually the RAM and not the slot. I'm going to leave it on overnight, but thus far 14 min into the tests there have been no errors. All other previous passes had 10 to 12 thousand errors by now (over 4000 after the first couple of tests). When I pulled one of the modules out the computer forced me into the bios to reset my overclocking back to default factory settings. I wasn't aware that my computer had been overclocked, and while I'm much more concerned about getting a replacement for the RAM, I'm wondering if I should expect any issues with that. I also swapped the boot order to make the CD/DVD drive boot before either of the HDs in order to make memtest work again (for some reason it was being ornery... perhaps because of the factory default settings).
    Wednesday, January 26, 2011 9:48 AM
  • So tonight I was able to finally sit down and fiddle with the RAM in my box. I managed to find 1 module that was routinely causing errors.
    Ok, so you now found out the damaged RAM. Check if you have warranty on the RAM to get new one.
    I also swapped the boot order to make the CD/DVD drive boot before either of the HDs in order to make memtest work again (for some reason it was being ornery... perhaps because of the factory default settings).

    This is fine. To speed up the boot, the HDD is set as first position to avoid the slow DVD/CD access each time you boot. I can seelect a Bootmenu with F12 if I want to boot from a different device and not my HDD.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, January 26, 2011 1:29 PM