Bad memory causing BSOD

[petex8989]

My computer recently started getting the blue screen of death, and I discovered it was a faulty ram stick when I ran memtextx86. After I ran the test I decided to start up the pc with only one ram stick, (the one thats working), but then I keep getting looped with the BSOD, and couldn't get into windows. I put the bad ram stick back and the issue persisted. Any suggestions on how to fix this issue?

[petex8989]

I ended up resetting windows, but the BSOD is still persisting.

[Uptivuptiz]

What error code do you get when BSODing?

[petex8989]

11 minutes ago, Uptivuptiz said:

What error code do you get when BSODing?

Driver Verifier Detected Violation 

[petex8989]

I just tried a system restore, but after it finished, it gave this error "An unspecified error occurred during system restore (0x80070003).

[Uptivuptiz]

Ok. That's a driver issue then. Does it state a file name when BSODing?

[petex8989]

only sometimes, and the files changed. i only remember one fo the files, it was wudfpf.sys

[Uptivuptiz]

If you don't BSOD immediately after booting into windows try this guide to reset the Driver Verifier that might be causing problems.

[petex8989]

i BSOD before windows boots up, and it loops infinitely

[Uptivuptiz]

Just now, petex8989 said:

i BSOD before windows boots up, and it loops infinitely

Hm, ok. What you can do in this case is to create a windows 10 installation media and INSTEAD of clicking install you can click repair and it will take you to diagnostic tools.

[petex8989]

So I created the installation media, but the repair tools it provides are the same as the ones i already had, and none of them have worked. should i proceed with completely reinstalling windows?

[petex8989]

is it possible that windows is just not detecting the ram?

[Uptivuptiz]

Through those tools you should have access to a CMD, right? That MCD windows is located on the X: drive. You have to go to the directory where the normal CMD is located (C:\Windows\System32) Afterwards you can follow the guide I linked to before.

[petex8989]

when i do it, it says "No settings were changed", and the problem persists

[Uptivuptiz]

12 minutes ago, petex8989 said:

is it possible that windows is just not detecting the ram?

If windows wasn't detecting any RAM then you wouldn't even get a BSOD. This is a driver issue or something with Windows. A complete reinstall might fix it.

[petex8989]

would i be able to reinstall windows without losing my data?

[Uptivuptiz]

Just now, petex8989 said:

would i be able to reinstall windows without losing my data?

Not in this case. To be sure that windows does not BSOD again you would have to lose everything to reinstall.

[petex8989]

The ram sticks have issues with them, and i would probably be able to get an RMA on them, would new ram sticks change anything in this situation? or is it strictly a driver issue? i don't know how the drivers got messed up, this all happened after i used memtestx86.

[petex8989]

I just tried system restore a second time, and it seems to have fixed the issue. Not sure why it didnt work the first time.

[Uptivuptiz]

9 minutes ago, petex8989 said:

I just tried system restore a second time, and it seems to have fixed the issue. Not sure why it didnt work the first time.

Windows is windows: So wild and unpredictable lol  

[petex8989]

so now my issue is that im trying to run windows on only 1 ram stick, the one that works, but windows wont let me do it, and its going into another boot loop with the error this time being critical process died

[petex8989]

now its not even letting me do a system restore, when selecting a drive to restore, it doesnt show the main drive that windows is installed on, making it so that it cant restore that drive.

[Turtle Rig]

2 hours ago, petex8989 said:

I just tried a system restore, but after it finished, it gave this error "An unspecified error occurred during system restore (0x80070003).

Do it from safe mode and you won't get that message and it will work.  good luck

[petex8989]

I feel kinda dumb, i found the solution to the problem, i just needed to clear the cmos... everything works fine now.

 

Edit: I tired once again to remove the malfunctioning ram stick, clearing the CMOS again, but it didnt work this time, and when i put both ram sticks back in, clearing the CMOS still doesnt work.