Got a call today from a friend who I installed TP for on Toshiba L55-b5267, core i5, 6 gb RAM, saying it had crashed with blue screen "IRQL Not Less or Equal" while playing YouTube music.
We ran through the gamut of onboard and disk Repairs including Startup Repair, System Restore, Refresh and Reset and nothing would get it started.
I had made him a Macrium backup image but the PE disk wouldn't boot with an error that sounded like Secure Boot, which we turned off in BIOS, yet the disk then hung repeatedly at 2/3 loading.
Finally we reinstalled but this time I did not supply any drivers not provided by the installer or Windows Update which all I assume are vetted for TP. On the previous install I had imported a missing 8.1 chipset driver from Toshiba website.
Regrettably there was no way to rescue the Bugcheck file so would appreciate any suggestions on what to look for now in the fresh install. I also still have access to the Macrium backup image of the crashed install to restore to a partition if there is a reason to access it further for comparison.
Thanks for any feedback.
Well what is his system? Can't comment without knowing? Also many of these crashes I have encountered in the past are related to failed hardware of same kind or failed driver.
Toshiba L55-b5267, Core i5, 6gb RAM.
Reinstalled TP only to have it fail again at reboot irreparably. Refresh, reset will not complete, Auto repair fails to find cause, System REstore will not complete.
No access to crash dump.
Sorry there's not more. He wants 7 to replace it.
The problem might be hardware related. especially the RAM. Disable memory cache in the BIOS and run:
Memtest86+ - Advanced Memory Diagnostic Tool
Yes good call,The problem might be hardware related. especially the RAM. Disable memory cache in the BIOS and run:
Memtest86+ - Advanced Memory Diagnostic Tool
But if it is memory then 7 will be a problem too, ran into a memory problem a few years ago, found the bad ram and replaced it. It installed and ran no problems
also had a blue screen errors with installing with a bad Hard drive., replaced it and then it ran fine
We don't know until he re-install Windows 7. Macrium WinPE must be loaded into RAM before running and it hung, that's why I suspect the RAM might be the culprit.But if it is memory then 7 will be a problem too, ran into a memory problem a few years ago, found the bad ram and replaced it. It installed and ran no problems
also had a blue screen errors with installing with a bad Hard drive., replaced it and then it ran fine
Windows 10 seems to have an additional Recovery Option regarding bad drivers. I believe it is in the Advanced section somewhere, but if your friend has the Install Media, he can boot to that and try a repair, assuming you can't get there from the normal Repair process.
Maybe even try installing while offline so no drivers will download.
I always try to disable everything I can in the Bios prior to upgrading an OS. Things like Bluetooth can cause problems.
Edit: Oh, he might try removing the install media during the first reboot to see if it helps.
Make sure the firmware is up-to-date
Models:
L55-b5267: BIOS version 1.70 for Satellite L5x-B/S5x-B (PSKT4x/T8x/TAx/TEx, PSPQ2x/Q4x/Q6x/Q8x)
Posted Date: 2014-08-29 | Version: 1.70 | Size: 31.74M
L55-b5267RM: BIOS version 1.30 for Satellite L5x-B (PSKTUx)
Posted Date: 2014-08-05 | Version: 1.30 | Size: 37.07M
L55-b5267SM: BIOS version 1.30 for Satellite L5x-B (PSKTUx)
Posted Date: 2014-08-05 | Version: 1.30 | Size: 37.07M
L55-b5267WM: BIOS version 1.30 for Satellite L5x-B (PSKTUx)
Posted Date: 2014-08-05 | Version: 1.30 | Size: 37.07M
It looks as though the sub models are the same firmware, the URL seems to be different only by the referring page.
Also consider setting the defaults in the firmware.
Bill
.
Thanks Bill. He has v1.40. The changelog since then doesn't appear to have anything that applies to this at all. I'm not sure I want to chance a BIOS update via TeamViewer when he's now agreeing that Win7 is the best Upgrade from 8 which came with it. I should not have agreed to install TP but he was intrigued by it. I've promised him I'll install it as as Dual Boot when I come out to visit in spring.
I wonder if MS gets real time telemetry on crashes like this which are unrecoverable?
Given the "IRQL not less or equal" error on the original crash I'm guessing driver. But we had no crash file access.
I read something similar to this here albeit with Windows 8, I don't know if it's exactly the same issue Greg but it certainly sounds like it. I wasn't convinced with the troubleshooting methods at all but W7 saved the day.
