BSOD can't get into normal mode, BCCode: 3b

dAstraea said:

From what I remember I access it through the System Recovery Options. Btw, is it normal for you not to see your graphics card or idk what it's called in safe mode? coz i tried checking my dxdiag.exe and went to the display tab, there's nothing there to see.

That is normal yes.
In safe mode, only the very minimum is loaded. Many features you might be used to are not loaded in safe mode because they are not needed for Windows to function. The graphics card is one of the elements Windows doesn't necessarily need, because it has an alternative driver (Microsoft Basic Display Adapter) that is also used when you for example (re)install Windows without any driver or are temporarily uninstalling your display drivers to reinstall them.

Vineet Garg said:

Hi axe0 & dAstraea,
Greets,
@ axe0 : Sir, why he is not able to get the logs ? Does he have any problem with the page file or something like that ?

Just thoughts :
I know very little about BSODs but if it can be of any help ?
- Will it make any sense if he just try to boot into a win 7 RE which is full of utilities & drivers ? Can he get some information from there ? Would not it say better even if he is only able to boot there normally ? If my suspicion is right, I don't think a WinRE will be of much help.
- Would not it say that there is some serious software /driver / virus problem in the installed OS which is not even allowing him to boot ? A malware problem is quite rare with BSODs, I've personally never seen malware cause a BSOD with a situation I worked on

Thanks & Regards. ...

From the dumps I figured that something seriously wrong was going on, with the logs I requested I attempted to find out what the exact situation is. Since this is the first time that even in safe mode collecting those logs basically failed it gives an indication what's going on.

FYI, the pagefile is only related to the dumps, the other files have nothing to do with the pagefile and rely on built-in tools from Windows. As such I suspect, not entirely unexpected TBH, corruption in Windows which I expect to be related to another underlying problem.

Regarding the suggestions about Linux, Linux is usually one of the last options if most other suggestions have failed to identify the root cause and that's rarely the case since if most other options fail hardware troubleshooting will suffice.

@dAstraea, please run the following memory test. Unfortunately the built-in memory diagnostic test is known for not being the greatest.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Hi axe0,
Sir,
Thanks for clearing all the doubts.

Thanks & Regards. ...

Unfortunately that confirms my suspicion, your laptop should not have shutdown so that means the RAM or hard drive isn't causing issues. It would be either the CPU or motherboard, I would guess the motherboard though that there may be a defect causing power issues.