Solved On-going BSOD (Random Occurences)

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Virus removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Status
Not open for further replies.

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#1
Good Afternoon,

You previously helped me out way back in regards to this:

https://pchelpforum.net/t/system-32-audioses-dll.12773/

This led to my computer being partitioned into 2 accessible versions of Windows.
I have been primarily using the automatically selected (On Logon) one since I partitioned them and it has been working excellently, until recently.

Certain blue screen examples have been (based loosely on memory):
1) Attempted Write to Readonly Memory
2) Something related to a Win32K.sys
3) IRQL_NOT_LESS_OR_EQUAL
4)Today I had something related to the term "kernel"
Apologies for the poor examples.

I have also received crashes where a large audible buzz occurs and the comp instantly shuts down. Also sometimes a plain black screen would appear on boot-up.

I have performed certain actions in CMD (admin) such as - chkdsk /c, chkdsk /d and sfc scannow

I am currently in the alternate partition when typing this and no crash has occurred. Do you think this is directly related to that partition?

Apologies for the wall of text!

Looking forward to hearing back from you

Thanks,

Shaz.
 

Attachments

Bruce

Forum Regular
PCHF Advisor
PCHF Member
Oct 8, 2017
315
82
52
Yeppoon, QLD, Australia.
#4
based on the examples given and from what you are describing, I think your issue falls into one of three categories.
1) hard drive failure (that primary partition)
2) faulty memory
3) OS corruption

admittedly, pretty broad net but there you go. :)
no "here, flick this switch and you are fixed" solution.

so I would start the whole exercise with testing the memory, leave only one stick in at a time and run the PC and see how that effects things.

then, if you are having no issues when using that secondary partition, that would put more credence on either that installed OS or the partition itself as the issue. so a reinstall of the OS would a) freshen up any file corruption and b) that process may highlight some bad areas of the drive.

then you get into the area of how old is that drive? and if you have to reload Windows, why not do it to a new drive? and then, why not use the opportunity to do all that to a SSD?
 

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#5
Thanks for the response i will take a look when j get home from work (18:00 GMT).

Ideally what I would want is just the one individual OS and not have the 2 individual partitions. Since I posted I've realised the 2nd partition has audio probably stemming from my initial problem back in 2016. After testing memory later is there an option revert back one individual drive and perhaps do a complete windows reinstall?

Thanks.
 

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#6
Update: Upon turning on (Still with both memory sticks in) I have encountered a new BSOD upon startup - "System Thread Exception not handled". Don't know if this contributes to any particular factor.
 

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#7
Second update (Ram Sticks): I have tried them both solo in the first slot. For about 45 minutes each and experiences no crashes or BSOD.
Unable to launch with them solo in the third slot (Don't know if this just how MoBo's work?). Receive the error code 55 (no memory installed).

Edit - One of the sticks has crashed on it's own (Not BSOD). Testing the other for a longer period of time.

Thanks again.
 
Last edited:

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#8
Third Update: I have tried the second individual ram stick on its own for about 4 hours and no crash or BSOD has occurred so perhaps this may indicate something faulty with the over RAM stick?
 

Bruce

Forum Regular
PCHF Advisor
PCHF Member
Oct 8, 2017
315
82
52
Yeppoon, QLD, Australia.
#11
I'd run it on what seems to be the good RAM stick for a few days - to be sure, to be sure.
then if you want to get more memory, for your motherboard make/model, look up their compatibility list and use that as a guide.
but generally speaking, as long as you get the type of memory for your slots and the frequency right, you're usually good to go.
 

jmarket

PCHF Owner
PCHF Owner
Support Team
Security Team
Jan 10, 2015
1,525
399
PCHF Bunker
pchelpforum.net
#12
If you're running Windows 10, W10 has it's own built-in memory diagnostics tool. So before you go out buying hardware, please do some software-based diagnostics first. I use these tools in my day-to-day job as an IT Technician, and these are always done first.

First start with RAM. To do this, do the following:

  • Click Start, type mdsched.exe in the Search box, and then press Enter.
  • Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.
  • Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically. If you want to perform fewer or more tests, press F1, use the Up and Down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.
  • When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.
Please let us know what the results say :) After that we'll move on to HD testing. Bruce is right, it falls into one of 3 hardware, and we need to eliminate each one as suspect
 

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#14
Right so after some testing of each RAM stick in each MoBo. One stick works fine in each port and the other not do much. I guess it's down to buying a new set of sticks!
 

Shazoom

PCHF Member
PCHF Member
Sep 22, 2016
35
12
24
#16
Terribly sorry! I thought I had updated you earlier.

So yeah, after initially testing each stick in the Motherboard slots individually it was 100% a RAM Stick failure that was causing the BSOD.

I will be purchasing a replacement soon and that should hopefully solve the problem!

Thanks for the suggestion which fixed the problem!
 
Likes: jmarket
Status
Not open for further replies.