BSOD ntoskrnl.exe Windows 8.1

Toggle sidebar Toggle sidebar
A

AJCook

Reputable
Jan 18, 2016
3
0
4,510
Hi there, for the past two weeks I've been suffering numerous BSODs throughout the day attributed to ntoskrnl.exe according to bluescreenview and windows debugger. I changed my ram from an old 4 to two new 4GB sticks a few days before it all began but with work haven't really had much time to test things. I ran windows memory diagnostic with five passes and it came out A-OK but, with the aforementioned time restraints, haven't had the time to try memtest.

Having read similar problems here which pointed at a problem with drivers I updated my bios, gpu and windows but it's not had much impact. Same with defender scan, malwarebytes scan. sfc /scannow seemingly alternates between finding nothing, or finding corruptions and fixing them. Neither has anything changed since I tried dism.exe ... /restorehealth.

In terms of a common cause one or two BSODs usually occur when I first boot my computer in the morning, followed by one or two throughout the day. Generally they're when I'm browsing the internet or browsing folders. I think it's only ever happened once while I've been playing computer games. Pale moon's been erratic as hell, crashing several times a day since this began.

Anyways, here's a link to a zip with all my dumps since it began http://www.filedropper.com/minidump_1, if anyone could shed some light on what the hell to do I'd be massively appreciative.

Thanks
 
Solution
J
sometimes different audio sources can mess up graphics. You might disable any audio source that you don't actually have a speaker connected to.
Also, update to the current drivers for all of your audio sources, ie motherboard drivers at your motherboard vendor website. many driver updates here:
http://www.asrock.com/mb/Intel/Z97%20Pro3/?cat=Download&os=Win8a
-------
this bugcheck was called because directx tried to free memory it did not own any more. the subcode was 0xc0000409 The system detected an overrun of a stack-based buffer in this application.

basically, a program corrupted the directx data when directx tried to clean up its resources it tried to free a address it did not own. This resulted in the bugcheck.
the app that...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
overall I would un install the evolve software and the
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver software, this last driver tends to be tricky to remove and most people have to use this method:https://technet.microsoft.com/en-us/library/cc730875.aspx

IE I think the uninstaller with the software really does not work.

if you still have the problem after removing the drivers, the next step would be to start cmd.exe as an admin
and run
verifier.exe /standard /all
and reboot, this will force windows to look for drivers that are causing memory corruption. when it finds on it will bugcheck and name the driver.
Note: be sure to know how to get in safe mode so you can turn off verifier.exe by
verifier.exe /reset

I suspect the problem is going to be in a service but i know it will just bugcheck on the Scarlet.Crush
driver if it is installed while verifier is on.

----------
machine info:
BIOS_VERSION: P2.10
BIOS_DATE: 10/13/2015
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: Z97 Pro3
Processor Version Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3200MHz


third bugcheck, looks like the system tried to do some cleanup but when it tried to make sure the object was not in use it looks at a counter that should be zero and it was not zero. IE something modified the counter or was using the resource when it should not have been. system uptime was 11 seconds.



second bugcheck looks like a service finished a copy and the system tried to free up virutual memory and then bugcheck. Looks like the system was trying to install some software at the time of the bugcheck. Again the bugcheck was while attempting to free virtual memory. Most likely you have a service that is messing up.

I would run a malwarebytes scan and look for malware, and run crystaldiskinfo.exe to read your smart data from your drive to see if there are lots of errors.

looked on the most current bugcheck.
it was cause by a service running, trying to read from the registry but using a bad memory address.
It was a generic service host (svchost.exe) It could be a bug in the service or another driver corrupting memory.
system was up 35 seconds so I would guess the service is the problem.

- It looks like you have a keyserver installed on the machine. Indication of a pirate software.
- I would remove ScpVBus.sys Sun May 05 14:31:26 2013 because bugs in the driver .

do you use this software ?:
Echobit Evolve Virtual Miniport (Ethernet) driver
evolve.sys Fri Aug 06 21:47:00 2010
 
Upvote 0 Downvote
A

AJCook

Reputable
Jan 18, 2016
3
0
4,510


Hi, thanks for the reply. I deleted the Evolve software as I no longer used it, along with the Scarlet.Crush driver using the method you linked to, and I ran malwarebytes with nothing found. No changes this morning so I tried /verifier and was stuck in a BSOD restart loop until I could turn it off. Here are the two dumps made, with the earlier/larger being the /verifier BSOD and the second one that happened after I'd turned /verifier off.
Thanks for the help so far!
http://www.filedropper.com/minidump_2

Also I deleted the Evolve software but the Evolve Virtual Ethernet Adapter's still listed in device manager, so I disabled it for now.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the second bugceck was caused when wininit.exe process was terminated. This is a required process so the system bugchecked. it looks like the process was killed intentionally rather than just hitting a bug and crashing.


the first bugcheck was called because some device driver provide a required piece of code.
this driver is still loaded, I would think it is the one being flagged but I can not tell without looking at a kernel memory dump. The information is not stored in a minidump.
looks like this driver did not get removed. (people always take many tries to get rid of this driver)
\SystemRoot\System32\drivers\ScpVBus.sys Sun May 05 14:31:26 2013


 
Upvote 0 Downvote
A

AJCook

Reputable
Jan 18, 2016
3
0
4,510

This time round I removed the driver with pnputil and with device manager and, first time booting today, it's running fine. I turned on verifier.exe, restarted and again no bsod or anything. I think you've done it!
Thank you so much!

Edit: Ok so there weren't the typical crashes I get at the start but I did just have a BSOD in the middle of my work. I set it to kernal dumps so fingers crossed it had some useful information.
http://www.filedropper.com/012016-6406-01
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
sometimes different audio sources can mess up graphics. You might disable any audio source that you don't actually have a speaker connected to.
Also, update to the current drivers for all of your audio sources, ie motherboard drivers at your motherboard vendor website. many driver updates here:
http://www.asrock.com/mb/Intel/Z97%20Pro3/?cat=Download&os=Win8a
-------
this bugcheck was called because directx tried to free memory it did not own any more. the subcode was 0xc0000409 The system detected an overrun of a stack-based buffer in this application.

basically, a program corrupted the directx data when directx tried to clean up its resources it tried to free a address it did not own. This resulted in the bugcheck.
the app that was running was palemoon.exe

it can be a bug in the game or the graphics driver.

also, this was a minidump, kernel dumps are stored in a different location/file name:
c:\windows\memory.dmp



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom