Constant BSODs with different error messages

[Meet8939]

When I start my pc, I get my login screen after I enter the password I get a blue screen which says Windows ran into a problem and needs to restart. I tried safe mode as well but after entering the password it shows the same problem blue screen. I tried resetting option and troubleshooting options but did not succeed. I have a Windows setup on my pendrive, how can I reinstall Windows or solve the problem?

[Meet8939]

Just now, Meet8939 said:

When I start my pc, I get my login screen after I enter the password I get a blue screen which says Windows ran into a problem and needs to restart. I tried safe mode as well but after entering the password it shows the same problem blue screen. I tried resetting option and troubleshooting options but did not succeed. I have a Windows setup on my pendrive, how can I reinstall Windows or solve the problem?

I was going to reinstall by formatting C, but thought to try this forum for a solution of this problem.

 

[LukeSavenije]

3 minutes ago, Meet8939 said:

When I start my pc, I get my login screen after I enter the password I get a blue screen which says Windows ran into a problem and needs to restart. I tried safe mode as well but after entering the password it shows the same problem blue screen. I tried resetting option and troubleshooting options but did not succeed. I have a Windows setup on my pendrive, how can I reinstall Windows or solve the problem?

what error code?

and why did you post this in the linux/non-windows section?

[Meet8939]

4 minutes ago, LukeSavenije said:

what error code?

and why did you post this in the linux/non-windows section?

Tut there is no error code displayed just error name as 'System Service exception'. I looked it up on google and it showed that you could repair it by starting PC in safe mode and upgrade drivers. I tried that but it showed the same problem in safe mode.

I thought this section was for Operating System related things, so I posted here.

[LukeSavenije]

11 minutes ago, Meet8939 said:

Tut there is no error code displayed just error name as 'System Service exception'. I looked it up on google and it showed that you could repair it by starting PC in safe mode and upgrade drivers. I tried that but it showed the same problem in safe mode.

I thought this section was for Operating System related things, so I posted here.

okay. try a soft reset, startup repair, going to an older build. I've had problems with 1803 since a while too

[Meet8939]

2 minutes ago, LukeSavenije said:

okay. try a soft reset, startup repair, going to an older build. I've had problems with 1803 since a while too

I tried startup repair, but it showed ' startup repair couldn't solve it'. It doesn't even let me go to an older build.

[LukeSavenije]

4 minutes ago, Meet8939 said:

I tried startup repair, but it showed ' startup repair couldn't solve it'. It doesn't even let me go to an older build.

what about a soft reset?

[Canada EH]

What Windows os do you have?

 

I'd just reinstall.

[Master Disaster]

We'd need more information to help. Hardware specs? Windows version? Did anything change or update before the problem started?

 

Most of the time that BSOD is caused by a bad driver and can usually be fixed by removing the driver but safe mode should have allowed you to boot to desktop.

 

Can you snap a picture of the BSOD with your phone and post it?

[NelizMastr]

Custom build or OEM PC? HP has problems with a keyboard driver that bricked after a Windows update.

[homeap5]

You can put that drive into another computer - different hardware should prevent BSOD related to drivers. Then you can remove bad drivers and plug your drive back.

[WkdPaul]

* Thread moved to the Troubleshooting section *

[Meet8939]

I am having a series of BSODs with my computer for past few days. On first day it showed Memory management issue. After using every possible way to repair using Windows repair from USB I asked my brother who also has a computer to format C and install Windows fresh. When he connected my hard drive to his PC his Windows didn't start at all and showed message of 'Bad System Config'. By watching online for some solutions we tried it but it didn't work, he then installed Windows on his hard drive to start it. I saw few videos about copying and deleting Windows from CMD and tried it and it worked. I installed fresh Windows on the same drive, just after half an hour it got a new BSOD with message 'Bad System Config'. I did the same formatting and installing again, but next time it became pretty hard to install it, few times it didn't even showed my hard drive. I finally was able to install Windows and it looked stable, but when I updated it and it restarted when it started it again showed a BSOD with error message 'Execution of Non-executable Memory'. I saw what it was on YouTube with its solution and am running Windows memory diagnostic tool through CMD. I am very confused about what is wrong as it is frequently showing a BSOD. And for record this not my first time deleting and installing Windows on my PC, I did it a lot of time and have good knowledge about it, but unable to pin point the issue with this one.

 

Here is the current BSOD, it also won't restart after reaching 100% on the 'saving data and restarting'. I was also thinking about installing a different operating system for testing is it just a Windows issue of a hardware issue, should I do it?

[Jurrunio]

hopefully your system is stable enough for you to run crystaldiskinfo to check s.m.a.r.t. data of the storage drives.

 

If storage drives are fine, I suppose the RAM to be dying. That's what caused my desktop to crash at random times with random reasons until I replaced the old sticks.

[Radium_Angel]

29 minutes ago, Meet8939 said:

So please suggest me!

Failing hard drive or bad RAM.

[homeap5]

44 minutes ago, Meet8939 said:

(...) And for record this not my first time deleting and installing Windows on my PC, I did it a lot of time and have good knowledge about it, but unable to pin point the issue with this one.

It is nothing to be proud of. You have "good knowledge" of constantly installing the same operating system - that means that you never solve any problem but always delete everything and start from zero. It's like to be a very experienced car mechanic who always fix car by replacing engine (or buying new car). Sorry, but this is not how you should fix anything.

 

System has event viewer where you can find error codes. There are many tools that can check your hard drive, memory etc. And what is most important - you should start with cables checking - SATA cables, 24pin, 4/8 pin, GPU etc. Use only one ram if you have more that one and check then. Check with other drive plugged in. Basically check everything BUT system - if it works, it works and it can help you to find real problem. Leave your system alone and every time you want to reinstall your system, repeat 10 times: "I don't really need to do that".

[Meet8939]

3 hours ago, homeap5 said:

It is nothing to be proud of. You have "good knowledge" of constantly installing the same operating system - that means that you never solve any problem but always delete everything and start from zero. It's like to be a very experienced car mechanic who always fix car by replacing engine (or buying new car). Sorry, but this is not how you should fix anything.

 

System has event viewer where you can find error codes. There are many tools that can check your hard drive, memory etc. And what is most important - you should start with cables checking - SATA cables, 24pin, 4/8 pin, GPU etc. Use only one ram if you have more that one and check then. Check with other drive plugged in. Basically check everything BUT system - if it works, it works and it can help you to find real problem. Leave your system alone and every time you want to reinstall your system, repeat 10 times: "I don't really need to do that".

I did install Windows again most of the times because it was some problem in Windows software, I tried recovering it but if it didn't happen I was left only option to reinstall it. This time I think it is a hardware issue and I was not so sure what steps should I take first. But you really helped, my Windows just loaded after removing one of the ram sticks, I think it was a faulty ram but will still check if it runs after I put it back for final result.

Thanks for the help! I will try to do this before doing a complete new installation of the Windows.

 

I tried that ram module in the place of the one in which it booted, it worked. Now placed my both module as they were and it's working now. I don't understand how did this happen?

[LogicalDrm]

First of all, which Windows and what drive and mobo are you using? HDD or SSD and how old mobo, as in BIOS or UEFI. What you should do, since you are already ready to format and do fresh reinstall, is just do it. That will tell if its hardware or OS issue. You can try with Linux, or some other Windows too.

 

Use single drive on YOUR own system and format drive (delete partitions). Then install Windows on to it. If BSODs continue after that, its time to look for hardware issues.

 

Bad System Config means that there are drivers issues. This usually happens when you move Win7 or older Windows to another computer. They don't take hardware changes easy. Memory can be multiple things, including actual memory issues. But also things related to too small pagefile or memory leaks.

[homeap5]

Its called reseating ram module. Sometimes it can help. Probably ram was bad plugged first time. And probably previous problems with Windows was because of that too. Do not reinstall Windows from now. Newer. It's not needed.

[Meet8939]

1 hour ago, LoGiCalDrm said:

First of all, which Windows and what drive and mobo are you using? HDD or SSD and how old mobo, as in BIOS or UEFI. What you should do, since you are already ready to format and do fresh reinstall, is just do it. That will tell if its hardware or OS issue. You can try with Linux, or some other Windows too.

 

Use single drive on YOUR own system and format drive (delete partitions). Then install Windows on to it. If BSODs continue after that, its time to look for hardware issues.

 

Bad System Config means that there are drivers issues. This usually happens when you move Win7 or older Windows to another computer. They don't take hardware changes easy. Memory can be multiple things, including actual memory issues. But also things related to too small pagefile or memory leaks.

OS: Windows 10 pro

Motherboard: Gigabyte G41 Express chipset

CPU: Intel Pentium E5300

Hard disk: 256GB 

it may be somewhere around 8-10 years old.

Now after few minutes of my computer started working I restarted it to check, it showed another BSOD with error message 'Critical Service Failed'. I'm very confused as to what is happening to it. I have tried startup repair but it didn't do anything.

[LogicalDrm]

1 minute ago, Meet8939 said:

OS: Windows 10 pro

Motherboard: Gigabyte G41 Express chipset

CPU: Intel Pentium E5300

Hard disk: 256GB 

it may be somewhere around 8-10 years old.

Now after few minutes of my computer started working I restarted it to check, it showed another BSOD with error message 'Critical Service Failed'. I'm very confused as to what is happening to it. I have tried startup repair but it didn't do anything.

Did you use GPT instead of MBR when installing?

[Meet8939]

6 minutes ago, LoGiCalDrm said:

Did you use GPT instead of MBR when installing?

I didn't understand what you are asking can you please simplify it

 

[UnwantedLinks]

Try reseating your ram, and removing your CMOS and putting it back in.

[LogicalDrm]

1 hour ago, Meet8939 said:

I didn't understand what you are asking can you please simplify it

When you partitioned drive, which bootmanager system did you use? I'm just ruling out possible issues. But if you have fresh install already and issues continue, then its hardware problem.