Windows 10: Multiple BSODs (Once Again)

I am back once again, with more crashes; after my last thread (Five months ago) all was fine, but now my computer is blue screening once again. I have had one BSOD every day for the past four days (If I recall correctly and including today) Every time they have happened I have been merely using the internet with Google Chrome, and possible doing file work (Like reading a pdf). Each error code is different each time; I believe the most recent was a spooler exception. (Though not 100% sure) All help is appreciated, thank you.

:)

 

Multiple issues once again with Windows 10 PC

Okay, I ran both /f and /r chkdsk tests on my hard drive, and it seems to have accomplished nothing either.

By "HD maker's Diagnostics", do you mean one of the tests that a hard drive brand has in some software (Example: SeaTools)? If so, which test would you like me to show you the results of? My hard drive brand is Seagate, and it is just under a year old.

 

Multiple issues once again with Windows 10 PC

Hi Left click the icon that looks like a paper clip. Then Right click and paste your .

html

(Insert hyperlink)

gb89

 

Are you having a gaming keyboard with sound output?

If yes, let us know in detail about it. I guess it is G510.

 

Yes, I use the Logitech G510 keyboard for my sound output, I have my headset with mic (Kingston HyperX Cloud) plugged into it through audio jack. And (obviously) it plugs into my computer through USB.

On a side-note it has recently been acting up, it has stopped automatically choosing my custom profile and I've had to choose it manually everyday (This has happened it the past though, and it always would just start working again, eventually). So it may just be a coincidence.

 

Well. Please remove that keaboard on a test basis. Apply any other keyboard for a reasonable time (say 7 days) and see how the computer runs.

We are getting a hint that a sound making keyboard is anyhow influencing the issue but we dont have a documented full proof to say it. So this elimination test will be very needed.

 

Very well, I will report back after the allotted time, unless anything else comes up.

 

Welp, my computer blue screened again just a few minutes before the time of writing this. I've attached the new file and I believe the error code mentioned Win32.sys. Before It BSOD'd I was simply using Google Chrome and working on a pdf with file explorer.

 

Please do two things.

Test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums
If it does not show any error, enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



Information Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


Warning Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.


Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
____________________________________________________________________________________________________ ________
Code: BugCheck 3B, {c0000005, fffff960d4dd0ec6, ffffd00023d35030, 0} Probably caused by : win32kbase.sys ( win32kbase!HMFreeObject+16 ) Followup: MachineOwner ---------[/quote]

 

Attachment 75657Yep, I got an error when testing ram

 

Sorry for the late reply, I was not in home for last two days, and was not able to reply.

A single error can rule out the RAM as failing, but the failure may be caused by one RAM stick itself, or by a failing DIMM slot. It is better to discriminate between these two before taking the next step.

I would suggest you to follow the Part Three: Results & Extended Testing part of MemTest86+ - Test RAM - Windows 10 Forums.

Please let us know this result.

 

Right, so I tested all four of my RAM sticks separately and only one of them ever gave an error, so I suppose I'll need to get a new one to replace it. I took out the corrupted stick and am now running on just the three, but my memory usage and disk usage seem kinda of high without it, should I keep it out or should I still use it until I can replace it?

edit: Nvm, I was stupid and forgot to read my motherboard's compatibility for the RAM sticks; ie. it doesn't support using just 3, so I put back in the fourth one and my take out two later.

 

If you find a stick of RAM is failing, it is good that the DIMM slot is not causing the issue. The motherboard is good.

When you decide to change the RAM, dont replace a single stick but replace the KIT. Always use the RAM came in a single KIT; those are tested to work together.

 

Yep, I was planning on just buying a new four set. I'll order them, switch them out, and hope that fixes the problem. Thank you for the help thus far.

 

Let us know how it goes. All the best!