Consistant BSOD Lenovo I5 T410

  1. Posts : 3
    7 pro 32bit

    Consistant BSOD Lenovo I5 T410

    I need some help please:

    I keep getting a BSOD like clockwork on my Laptop.
    The Laptop can run in safe mode with no issues....Tested this last night and this it was still on this morning.
    I initially thought it was the ram so I removed the onboard 4Gb and replaced it with a new chip.
    I thought it was the video drivers so I tried all Lenovo's recommended drivers but it doesnt work cause according to the drivers I dont have a graphics card.
    I reloaded windows 7 32 to bit by doing a clean install and have not loaded any other drivers except the ones thats generic by windows7.
    I am clueless as I have tried every angle possible.

    Anyone pls

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.
    Locale ID: 1033
    Additional information about the problem:
    BCCode: 124
    BCP1: 00000000
    BCP2: 85C3C01C
    BCP3: F61EA240
    BCP4: 00040150
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    Files that help describe the problem:
    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows
    If the online privacy statement is not available, please read our privacy statement offline:
      My Computer

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

    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    We could also use some system information, which you can get easily by running msinfo32.
    To do that go to start>run>type msinfo32>enter

    When it is finished running go to file>save>name it and upload to us here.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under 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 (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
      My Computer

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

    Stop 0x124 is a hardware error

    If you are overclocking try resetting your processor to standard settings and see if that helps.

    If you continue to get BSOD here are some more things you may want to consider.

    This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

    Stop 0x124 - what it means and what to try

    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

    Generic "Stop 0x124" Troubleshooting Strategy:

    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

    2) Ensure that the machine is adequately cooled.
    If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.

    4) Update the motherboard BIOS according to the manufacturer's instructions.
    Their website should provide detailed instructions as to the brand and model-specific procedure.

    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

    Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

    Stop 0x124 - what it means and what to try
      My Computer

  4. Posts : 3
    7 pro 32bit
    Thread Starter

    Hi Ladies/Gemts:

    Seems like this issue really serious.
    I replaced the HDD today no joy same issue.
    I noticed the fan wasnt spinning on battery so I resolved issue in BIOS.
    I reloaded machine and no joy.
    I cant understand why its doing this...Its not overheating because now the fan spins the same as in safe mode which doesnt BSOD.

    Please find my log attached.

    Is this the one needed?
      My Computer

  5. Posts : 3
    7 pro 32bit
    Thread Starter

      My Computer

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

    Stiaan said:
    Hi Ladies/Gemts:

    Seems like this issue really serious.
    I replaced the HDD today no joy same issue.
    I noticed the fan wasnt spinning on battery so I resolved issue in BIOS.
    I reloaded machine and no joy.
    I cant understand why its doing this...Its not overheating because now the fan spins the same as in safe mode which doesnt BSOD.

    Please find my log attached.

    Is this the one needed?

    Still a 124 . Its probably not HD. Most likely cpu, mobo, power supply.
      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:56.
Find Us