OMG! not the BSOD! Help.

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by bmoreGUY, Jan 11, 2015.

  1. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Hello guys,

    So I decided to be a cheapskate and purchase a i5 T530 thinkpad on craigslist. What I thought was a good deal ended up so far being a heart pounding nightmare. As soon as I brought the laptop home I encountered my 1st dreaded and depressing BSOD asking the laptop why didn't you BSOD when I was testing you out! As far as the laptop goes, the only thing I know about it is that it look almost new, its a IBM lenovo thinkpad T530. It's an i5(3230M), 4gb ram, 500gb HD, with a fresh copy of windows 7 64. The BSOD happens about once per day. Sonething strange I want to point out.. one time it BSOD and it showed a few strange minor artifact on the screen while restarting than it went away and screen cleared. I thought that was weird. BSOD happens randomly. This is what I pulled from the dump using blue screen viewer. Any help would be much appreciated. Hopefully I didn't waste my hard earned money on someone's scam :-(

    =================================================
    Dump File : 011015-33743-01.dmp
    Crash Time : 1/10/2015 9:14:12 PM
    Bug Check String : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code : 0x0000003b
    Parameter 1 : 00000000`c0000005
    Parameter 2 : fffff800`02adfe94
    Parameter 3 : fffff880`0a852c80
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\011015-33743-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 291,800
    Dump File Time : 1/10/2015 9:15:18 PM
    ==================================================

    ==================================================
    Dump File : 011015-47751-01.dmp
    Crash Time : 1/10/2015 8:58:57 AM
    Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x0000001e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff800`02b46d03
    Parameter 3 : 00000000`00000001
    Parameter 4 : 00006800`00000208
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\011015-47751-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 290,936
    Dump File Time : 1/10/2015 9:00:39 AM
    ==================================================

    ==================================================
    Dump File : 010915-19983-01.dmp
    Crash Time : 1/9/2015 4:30:47 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00005002
    Parameter 2 : fffff700`01080000
    Parameter 3 : 00000000`000001e1
    Parameter 4 : 000090e2`fffffffe
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7efc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+7efc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\010915-19983-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 272,832
    Dump File Time : 1/9/2015 4:31:29 AM
    ==================================================
     
  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Hi,
    from the above I see that Data held in the RAM couldn't be read because either the data or RAM is corrupt. To really debug properly I/we need to see your dump files located in a folder marked 'minidump' found via the main Windows folder. If you find that no such folder exists then you may need to set the machine up to produce dump files.

    Go to Start and type in sysdm.cpl and press Enter
    Click on the Advanced tab
    Click on the Startup and Recovery Settings button
    Ensure that Automatically restart is unchecked
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
    found later.
    Click and apply to exit the dialogs, then reboot for the changes to take effect.

    Once you have some dump files read this thread and then post the results:
    http://windowsforum.com/threads/how-to-ask-for-help-with-a-bsod-problem.38837/
     
  3. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Thanks for the reply kemical. Yes it did create minidump files. Here they are. Thank you!
     

    Attached Files:

  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002b46d03, 1, 680000000208}
    
    Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
    
    Followup: MachineOwner
    
    Hi,
    looking at all three dump files one can see that they are possibly memory related. However, checking your system details I noticed that both Bios and drivers are out of date. The above Bugcheck especially can be caused by either one of those.
    SystemFamily = ThinkPad T530
    BiosVersion = 2.55
    BiosReleaseDate = 08/12/2013

    Update both drivers and Bios using this support page although do double check that it's correct for your machine (make sure you apply any patches and firmware too):
    http://support.lenovo.com/gb/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t530

    I see your running AVG AV. If the bsod continues after updating the above then try removing AVG as it is known for causing the odd issue from time to time. Use MSE in it's place as it's ultra stable:
    http://windows.microsoft.com/en-GB/windows/security-essentials-download

    If after making the above changes you still get the bsod then you need to test your RAM.
    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

    Post any new dump files.
     
  5. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Thank you. I'll go ahead and update both bios and driver but, what exact driver do I need to update? The link you provided has the bios but I cant seem to understand which driver I need to update. Here is the latest BSOD report also. Thank you for your help sir!
     

    Attached Files:

  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80002a7366a, fffff8800c295620, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+24a )
    
    Followup: MachineOwner
    
    Hi,
    I'd update everything that's applicable. Just choose the correct operating system from the drop down menu and then methodically go through the list. Some of the downloads you'll notice are applications so you can ignore them but specifically you want to be aiming at chipset, graphics, audio and network. Don't forget the bios too.
    If the bsod continues after then try my suggestion concerning testing the RAM.
     
  7. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    I went through every driver I could and I also updated the bios. However, I had a problem with the video driver. It won't let me update because it says that my system doesn't meet the minimum requirement. I'm a little puzzled by this. Do you have any idea why this might be? Inside the readme it doesn't state what is the minimum requirement.

    I got my finger crossed. So far it seem good. I haven't gotten a BSOD in over 24hrs. I'm really hoping it was just a bios issue. I'll keep you updated sir.
     
  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Can you remember which of the GPU downloads you used? You have drivers for the Intel graphics as well as Nvidia Optimus which one did you try?
     
  9. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Yes. I tried the Intel graphics driver.

    I'm also still getting BSOD. Same caused by "memory management"
     
  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Read post #4 again.

    Have you tried the Nvidia driver? You could also try right clicking on the actual driver, hit properties then run as admin.
     
  11. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Look like the memtest is next in order after I see if I can update the graphic driver properly. I'll keep you updated. Thank you.
     
    kemical likes this.
  12. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Ok, so I found out that Lenovo has it's own diagnostic tool to test bunch of hardware such as the ram, motherboard, HDD, etc..etc.. so I ran every Lenovo diagnostic test available and the only thing that came back with error is the physical ram test. It actually failed in 4 different places which include moving inversion 32bit test, random pattern test, random number sequence test, and block move test. So I'm not 100% certain but does it look like the culprit might just be the ram stick itself? Thanks for your help so far.
     
    kemical likes this.
  13. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    Lenovo Diagnostics - Log
    upload_2015-1-16_0-34-12. Failed
    Errors were found
    Physical Memory Result Code:WME3VV3O0-UK8VCI
    UDI: Physical Memory
    Physical Memory: 4.000 GB
    Resources:
    Resource type:
    Bank
    Index: 0
    Manufacturer: Hynix/Hyundai
    Speed: 1600 MHz
    Size: 4.000 GB
    Part number: HMT451S6MFR8C-PB
    Serial: 294BC82B
    Type: DDR3
    1/15/2015 23:57:25 - Advanced Integrity Test upload_2015-1-16_0-34-12. Passed (8.55s)
    1/15/2015 23:57:34 - Address Test upload_2015-1-16_0-34-12. Passed (3.97s)
    1/15/2015 23:57:38 - Bit Low Test upload_2015-1-16_0-34-12. Passed (6.89s)
    1/15/2015 23:57:45 - Bit High Test upload_2015-1-16_0-34-12. Passed (7.06s)
    1/15/2015 23:57:52 - Walking Ones Left Test upload_2015-1-16_0-34-12. Passed (46.19s)
    1/15/2015 23:58:38 - Walking Ones Right Test upload_2015-1-16_0-34-12. Passed (46.41s)
    1/15/2015 23:59:24 - Modulo-20 Test upload_2015-1-16_0-34-12. Passed (103.78s)
    1/16/2015 00:01:08 - Moving Inversions 8bit Test upload_2015-1-16_0-34-12. Passed (97.42s)
    1/16/2015 00:02:45 - Moving Inversions 32bit Test
    1/16/2015 00:02:47 - Critical: Memory address 0x00000000A46A3310 wrote 0x0000000400000004 read 0x0000F10400000004
    Failed (1.69s)
    1/16/2015 00:02:47 - Random Pattern Test
    1/16/2015 00:02:49 - Critical: Memory address 0x00000000B3C68310 wrote 0xBB6167B75FB7D11D read 0xBB61F0B75FB7D11D
    Failed (1.66s)
    1/16/2015 00:02:49 - Random Number Sequence Test
    1/16/2015 00:03:05 - Critical: Memory address 0x00000000DA026310 wrote 0x000051D400002ED1 read 0x0000F1D400002ED1
    Failed (16.59s)
    1/16/2015 00:03:05 - Block Move Test Failed (67.19s)
     
    kemical likes this.
  14. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    Hi,
    yes it looks like a stick has failed. Memtest86 would have also found the same thing so it's saved you a job of running that. You can determine which stick it is by removing a stick and repeating the test. Do this for each stick and you usually find it's just one stick thats faulty although sometimes two can go down.
    I should imagine this is why the lappie was sold. Perhaps the former owner didn't have your resourcefulness and failed to determine the issue. Anyway it's a relatively easy fix in that you just need to swop the offending stick for one that is running fine.
     
  15. bmoreGUY

    bmoreGUY Member

    Joined:
    Jan 11, 2015
    Messages:
    9
    Likes Received:
    3
    WOW! it's like a new computer now. I didn't realize just how much a bad physical ram stick can cause problems. I was constantly getting errors when downloading applications, corrupt file messages, and just bunch of weird issues left and right. I didn't think it was due to the faulty ram at first since I had no idea that bad ram can cause so many problems. The good news is that as soon as I replaced the 4gb stick with 8gb brand new stick I got from best buy today everything came alive. No more errors, no more download and install issues, and no more restart on it's own. So it look like the faulty physical ram stick was the issue. I haven't used the laptop long enough to see if the blue screen will show again but I have a good feeling I shouldn't, but I do have my fingers crossed.

    Thank you for your help so far as I truly appreciate it :)

    I will let you know if I get another blue screen but hopefully I won't have any reason to reply back here.
     
  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,784
    Likes Received:
    1,563
    That's great to hear well done! Post back if you should need to but in any case best of luck.
     

Share This Page

Loading...