Windows 10: BSOD everytime

so basically when windows 8.1/10 whql support option is enabled only then it shows secure mode and it is disabled however i cant even see the usb. Prior to that i was able to still boot usb when i didnt enable WHQL option but got stuck on black screen with blinking white cursor. Both times i disabled fast boot.

since then i have gotten another crash so here is an updated file.

 

are there any alternatives to memtest i can run, i already ran windows memory diagnostics and that worked fine and gave no errors.

 

Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 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. Again..

 

The problem is I can't seem to run memtest, with fast boot and secure mode disabled it doesn't even show up on PC however with window whql support disabled I can atleast see the usb and when I try to boot it up I just get a black screen with a blinking cursor. So basically I'm not even able to run memtest

 

Is the USB a bootable USB?

 

Yes I have used the same usb before to install Windows as well so it's perfectly capable of booting stuff

 

Please try another USB to see if that improves anything

 

ok so i went to shop and bought a new usb stick and luckily it works with this one, it instantly booted (the memtest) so now its just doing its thing my itself so roughly how long do i leave it like this for? I know I am supposed to wait atleast 8 passes but how long does 8 passes usually take

 

Usually 8 passes takes around 7-10h, but it may vary for some unknown reasons. It could also take twice the time it should take or longer.

 

ok so i left pc on the whole day and i got about 20 passes and from what i can see not a single error in there. Seems like the RAM is perfectly fine. Now I am thinking of what else it could be, when i was installing all the drivers i did install something called msi ram disk which is basically a disk running on ram but i disabled that straight after install (didnt uninstall).
I doubt it could be the ramdisk, would you know of any other possible option

 

so i just looked around online had a look at these 2 error codes from event viewer and popped them in google:

- Windows failed fast startup with error status 0xC00000D4

- Windows failed fast startup with error status 0xC0000001

these are the 2 main errors showing up there and there event ID is 29 and it seems that these might me causing the "kernet-boot"

googled each of them and 0xC00000D4 seems to do something with fast startup and i have noticed while i have fast startup disabled in win10, I am not really getting any BSODs so far.

the other error has something to do with harddrive or something.


Here are the two links i got info from if you want to check:

KERNEL_DATA_INPAGE_ERROR and Device - Microsoft Community

http://www.tomshardware.co.uk/answer...xc00000d4.html

 

It sometimes happens that fast startup gives problems yes.

See how it goes the next few days and report back *Smile

 

Ok so for now I have that Windows whql support option enabled but just fast startup disabled...most likely that would be the issue so I'll give it a few days.

*Smile

Meanwhile though, I'd still wanna know why it was giving issues...because on my laptop it works just fine with fast startup but at the same time my laptop doesn't have the exact same drivers or hardware as my PC.

 

The many different possibilities in Windows is the why.
One can put together his own laptop/desktop, install software and drivers, connect devices and again drivers.
Due to this, so many difference in each system, including the Windows Update updates where not everyone gets the same update even though it is the same Windows version, it happens that something causes problems when it doesn't cause problems on another system. Simply because the system is different from another system.

It doesn't even matter if 2 systems are '100%' identical to each other, somewhere is a difference what causes that problem one is experiencing.

 

ok so far not a single problem while fast boot was disabled...i also included an updated dump file log thing.