Evo 5 RS
might want to soak test it as if it's cooked it might still play up
0x0000006B is typically hard disk or major corruption. Rebuild it.Have the laptop back with me today, my mate told me it was running ok for a while then BSOD'd... its now blue screening on start up, with the first error code: 0x000.....6B
I'd say it's not worth trying to repair. It's clearly f'ked and if I was in your position it would have been handed back before now or put in the bin.
There is obviously a serious underlying fault here that's going to keep coming back.
How old is this laptop?
as I said before, try lastly installing to a usb flash pen to see if the problem persists if you don't have a spare HDD.
0x0000006B is typically hard disk or major corruption. Rebuild it.
Had a few issues like this with laptops, you got another unit you can swap out the RAM with ? If the HDD has slight platter clash it may BSOD when it tries to read from that section if the disk (clicking can be a sign of this normally caused from being dropped)
If the GPU is damaged from the high heat cycles you would normally get artefacts on the screen, my d630 got so hot it melted the solder attaching it to the board
Debugger Help said:The PROCESS1_INITIALIZATION_FAILED bug check has a value of 0x0000006B. This bug check indicates that the initialization of the Microsoft Windows operating system failed.
Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.
This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.