Windows 10: Occasional BSOD / freeze

Nothing useful in the dump again, rats!

Looking through the Event Viewer log, I see this was the last thing to happen before a BSOD.
Code: Event[36037]: Log Name: System Source: Service Control Manager Date: 2016-08-10T20:46:41.613 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-21-3838516596-1117518111-2304458171-1000 User Name: user-PC\user Computer: user-PC Description: A service was installed in the system. Service Name: MagicianSataModeReader Service File Name: C:\Program Files (x86)\Samsung Magician\magdrvamd64.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:[/quote] The next thing I see is that a restart occurred, no shutdown.

Code: Event[36038]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2016-08-10T23:52:17.765 Event ID: 12 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: user-PC Description: The operating system started at system time ?2016?-?08?-?11T04:52:17.497760700Z.[/quote] When did you install Samsung Magician? I think it was to check the SSD firmware, right. Try uninstalling it for now.

 

Looking through your install programs, there are a lot, including some tweakers (ASUS Tweak being one).

Have you set all over clocking to normal? Are all voltages set to normal?
What anti-virus are you using?
Try disabling most if not all programs from auto starting at boot time.

 

Samsung Magician came with the SSD, so I've had that for a long time. Just never updated it until recently.

I don't overclock - ASUS Tweak I just keep around to monitor GPU temp and such.

Currently using BitDefender.

 

Hi panmyxia,

Please follow the suggestions @Ztruker provides:
1. Uninstall all 3rd party AV programs and use Windows Defender while troubleshooting,
2. Install the RST from MSI

If you're overclocking something, revert back while troubleshooting.

Please remove ASUS & MSI programs while troubleshooting.

If you didn't yet, make sure the USB network adapter is in a different USB port than the previous USB network adapter.

Please remove all USB devices you don't need, all USB devices except for mouse, keyboard & USB network adapter.


While troubleshooting = the whole time until you say that you don't have a problem anymore.

 

BitDefender uninstalled, RST is already installed, ASUS Tweak uninstalled, network adapter USB moved, and more programs disabled at startup except for things I use.

 

Okay. So I just had two in a row. A friend of mine seems to think it's my SSD, is this a problem that occurs much? It's about a year old.

 

RST does not have the version from MSI?

Before you installed the new USB network adapter, did you remove the program from the previous USB network adapter from your system?

What is the reason that your friend thinks it may be the SSD causing problems?

 

He's had a similar problem before, though it was on a HDD. He ended up replacing it. My SSD isn't old, and it isn't showing signs of failing though.

Just uninstalled the Realtek WLAN thing. That was giving me issues last time, just seems I didn't think to uninstall the program.

MSI doesn't have a special version of RST as far as I can tell, it's just the same thing you can download from Intel. I could try reinstalling later.

 

I'm not meaning to say MSI has a special version or something, just install the one MSI provides. Updated version aren't always the best onces.

 

Okay, I've got the version from MSI re-installed. Ver. 14.5.0.1081

 

There are many who have similar problems, but different causes because the problem is not the same.

Symptoms might be the same, but the problem why it occurs is mostly different which is why different solutions work for different users where not all solution works for everyone.

 

That's what I figured. Anyway, so far so good. Though, learning from past blue screens, it may be several more days until the next one. Unless we've magically fixed it. If it doesn't happen for at least another week, I'll mark this as solved (again).

 

I would recommend to not mark this thread as solved until you think the problem really is solved.
Marking a thread as solved and unsolved because the problem has returned and solved again isn't a doing. It'll make a thread unreadable and we'll loose track of what has been done since the last time.
For this reason it is recommended once you'vee marked a thread as solved, to create a new thread when the problem has returned.

If I didn't let some users do this, some threads would've been tons of pages where I wouldn't want to spend time on finding out what I suggested since the last time. Of course the moderators don't allow that to happen, but I think you know what I mean *Smile

 

Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.

Please post each screenshot in your next reply/replies.

 

Please remove either the single or dual ranks memory, mixed memory may cause various of problems that sometimes are difficult to identify. After the removal please make sure the remaining sticks are seated as your motherboard supports (coloured slots)