Windows 10: Post-Upgrade BSODs various error msg

Attachment 87809 Dm log

I upgraded from windows 7 to windows 10 during april this year, and experienced blue screens as well as some desktop errors, but after about a week of woes, i didn't experience any crashes until the beginning of june. It was at this point that i decided to format my drives and attempt a clean installation of windows 10, after which the problems continued.

Furthermore, after crashes i frequently get a blank black screen upon restart and am unable to reach the express gate. Sometimes this happens before the crash report has been recorded, which is why i dont have records of all the crashes ive experienced. So far i have not been able to fix this through any means except powering off the computer for a sufficiently long time(10 minutes seems to work). if i restart it again without waiting, i'll just see a black screen.
The crashes almost exclusively occur soon after startup/wakeup and when using a web browser or running a game, particularly processor-intensive ones(even if they aren't graphically demanding, such as when running games on emulators)


:)

 

BSOD - Various Errors

BugCheck 19, {20, ffff848fc9df7000, ffff848fc9df74d0, 44d0000}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+1092 )

Device: ASUS Notebook X555UB

BIOS DATE: 10/18/2015 Version 204

Current BIOS Version and DATE:

Version 301 2017/03/31

X555UB | Laptops | ASUS Global

Update the BIOS and the Drivers. (mostly the
Chipset driver BugCheck A )

Regards.

 

Blue Screen after short idle (system_service_exception caused by ntoskrnl.exe)

I just tried the Driver verifier test.

After the restart, it BSod'ed just at the beggining of the boot.

The error msg at the blue screen was: DRIVER_VERIFIER_DETECTED_VIOLATION (aswVmm.sys)

I rebooted few times, getting either the bsod error msg above or IRQL_NOT_LESS_OR_EQUAL.. these bsod were occuring at the booting, before windows fully started..

So finally I rebooted, pressed F8 and managed to successfully start at safe mode and disabled verifier.

I've went to Windows/Minidump but there wasn't any new dmp file...

 

Your motherboard does not natively support Windows 10. please let us know the source of the drivers you installed?

You are getting various different BSODs which is a strong indication of hardware/compatibility related issue. You are saying that it all started after you upgraded to windows 10. So the source of the drivers would play a critical role in the issue, prima facie.

Among various issues, some OHCI related issue is seen.
Code: BugCheck D1, {2140000, 2, 0, fffff80084a0334c} Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneAsyncTd+1dc ) Followup: MachineOwner ---------[/quote] You should try the Windows 8 / 8.1 Legacy driver for the firewire. https://support.microsoft.com/en-us/kb/2970191

Let us know how it goes.

 

im sorry, im not exactly sure i understand the question.

i haven't manually installed any drivers for my motherboard

also, im not using any firewire devices, nor do i appear to have any firewire port. does this matter at all?

 

My question was .... how you got the drivers? If you havent done it manually, then it is configured by windows updates, and should not install a firewire port driver when it is not there.

Your explanation is required here.

 

its been there since i installed windows
or so it seems, at least.

 

Let us stress them? 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.

 

sorry for the long wait Attachment 90837

here's the minidump i was able to gather through verifier

 

This is pointing to your DualShock 3 controller driver.
Code: BugCheck C9, {21f, fffff8004273b174, ffffe00145d734c0, 0} Unable to load image \SystemRoot\System32\drivers\ScpVBus.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ScpVBus.sys *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys Probably caused by : ntkrnlmp.exe Followup: MachineOwner ---------[/quote] It seems to be a little old for Windows 10.
Code: Image name: ScpVBus.sys Timestamp: Mon May 06 03:01:26 2013 (5186CFAE)[/quote] Please seh for any possible update that is compatible with windows 10 and apply it.

 

i doubt that there's any updates, ps4 has been out for awhile now and DS4 hasn't gotten any official pc support

ive been using a 3rd party wrapper in order to use a ds4

 

Tough situation there, mate. You either have to abandon the DS4 used with DS3 wrapper or have to accept those BSODs; till you get the proper driver for that device.

 

the latter, because ive had bsod's to spare even before was using this controller