• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Blue Screen While Windows 10 booting up

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Update: For example just now I booted up and no BSOD. So I have a feeling it might really be linked to the windows updates and a driver not being properly updated. Is it possible to determine which driver it is though?
 
I don't immediately see anything in that list that would cause you problems. Possibly the MSI Super Charger or Avast is doing something strange, but those are just guesses.

You could try removing both (Windows Defender will automatically take over as your AV) and see if there are any changes.
 
On this note. Is Avast (or other) really necessary as an antivirus or can I easily have Windows Defender as my mian AV?

Personal preference. Do you download a lot? AVs are good with files you obtain from less-than-reliable sources, but not to much when it comes to monitoring your browsing sessions. Ad blockers and carefulness on your part is your best defense there. AVs are good as a last defense, and even then, mainly do their job when you actually run them (not just running in the background).
 
Hey, I just run the memtest and it gave me these results:





Must admid though that it went just through 1 pass. On monday when going to work I will let it run for 9+ hours (if its even worth it?)

Btw the memtest looks really different from the tutorials on the web. It just shows pass 1/4 (as shown at the pictures), seems like only 4 passes can be done with the test?

PS: thanks for helping me out, really appreciate it 🙂
 
It did it again, tried to uninstall Avast and install AVG. Let's see if that's it. Have a strong feeling that it might really be a program which causes the crashes during booting as it tries to load.
 
MBR issues cause Windows not to load at all. If you are still getting into Windows, the items discussed in that article do not apply to you. Let us know if anything improves with the AV change.
 
I never run it, save one time when I wanted to see what it would do. If the issue returns, remove one stick of RAM and see what happens.
 
Hey all,

Here you can see after installing AVG antivirus instead of Avast I got no BSODs. So we can assume it was caused by the Antivirus not faulty RAM?? This took place from 16.5.2016 - 21.5.2016.



On the 22.5.2016 i got BSOD again but that was because of installing bad drivers for my graphics card. This dmp file:

On Sun 22.05.2016 6:39:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052216-7796-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680E3F9F830, 0x822000036869C867, 0xFFFFE0005F370080)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


However, after installing the newest drivers for Overwatch. I got 2 errors in a row. May it be again because of the GPU drivers??

On Thu 26.05.2016 16:45:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052616-7156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000318EB0, 0x1000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 26.05.2016 16:45:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000318EB0, 0x1000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 25.05.2016 15:44:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052516-7296-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsDeleteScb+0x145)
Bugcheck code: 0x50 (0xFFFFF800A2B39FA0, 0x10, 0xFFFFF800A2B39FA0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Back
Top