Windows 10: BSOD using your computer as usual 0x0000000a ffff8580`5edf1000

Hello everyone, my mini computer, display blue screen and restarts automatically.The computer is new and there is no virus threat.Someone can be of help to understand the cause?Thank you !

:)

 

BSOD SYSTEM_SERVICE_EXCEPTION after update Visual Studio 2015 on Win 10

BugCheck 3B, {c0000096, ffff8580640ed850, ffff85805f3baca0, 0}

*** WARNING: Unable to verify timestamp for VMMR0.r0

*** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0

Probably caused by : memory_corruption

Followup: memory_corruption

ffff8580`5f3bab40 00000000`00000008

ffff8580`5f3bab48 fffff802`416dffeb VMMR0+0x1ffeb

ffff8580`5f3bab50 fffff802`7b6a4bf2 nt!IopSynchronousServiceTail+0x1c2

ffff8580`5f3bab58 fffff802`416c0000 VMMR0

ffff8580`5f3bab60 fffff802`417b7010 VMMR0+0xf7010

ffff8580`5f3bab68 fffff802`416c0000 VMMR0

ffff8580`5f3bab70 fffff802`417b7040 VMMR0+0xf7040

ffff8580`5f3bab78 fffff802`421f0000*** WARNING: Unable to verify timestamp for
VBoxDrv.sys

*** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys

VBoxDrv

ffff8580`5f3bab80 fffff802`4222a888 VBoxDrv+0x3a888

ffff8580`5f3bab88 fffff802`421f0000 VBoxDrv

ffff8580`5f3bab90 fffff802`4222af24 VBoxDrv+0x3af24

You most recent crash was caused by VirtualBox. Update or completely remove it.

 

Bugcheck error

Hi,

The error codes 0x0000000a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80124ccadde) is usually associated with a faulty driver or incompatible software or hardware. We suggest checking this
article and follow the troubleshooting step provided as an initial troubleshooting steps to resolve your
BSOD issue.

Update us with the outcome so we can provide further assistance.

 

So far this year every BSOD has been for a different cause

Code: BugCheck A, {ffff85805edf1000, 2, 0, fffff80021fd89b0} Probably caused by : sdbus.sys ( sdbus!SdbusDataCommandWorker+1099 ) BugCheck 19, {22, ffffd10f02e00000, 0, 0} fffff80399a2e338: Unable to get MiVisibleState Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c18a ) BugCheck D1, {ffffffffffffffff, 2, 1, fffff8017525aa34} *** WARNING: Unable to verify timestamp for rtux64w10.sys *** ERROR: Module load completed but symbols could not be loaded for rtux64w10.sys Probably caused by : NETIO.SYS ( NETIO!WfpCreateReassemblyContext+28 ) BugCheck 7F, {8, ffffb20180908a30, 83f2e7d0, ffff875d0d29caa6} *** WARNING: Unable to verify checksum for win32kfull.sys Probably caused by : memory_corruption BugCheck 3B, {c0000005, fffff8013d8d805d, ffff9301d9561600, 0} Probably caused by : memory_corruption[/quote] With this sort of behaviour it suggests you have some basic driver problems but the last 2 also point to possibly bad memory modules. The latter is easy to check for:





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.


Let's start with that and then move onto other possible causes.