Windows 10: Multiple Bsods in win10

Well, some people can't run that command and I have no reason why they can't. Just to test, I have run it several different ways and it runs fine for me. But, I know several people who can't. It is a good opportunity to correct things that are wrong.

 

Yes. But by that I mean just the Dism /Online /Cleanup-Image /RestoreHealth, the installation on a USB, the mounted ISO file and they all work for me. If you have been having this problem since you built the computer, I would suspect a hardware issue.
Please make sure your SSD has the latest Firmware, please go into bios and tell me the CPU Temp, Motherboard temp, the +12V, +5V and +3.3V temps. Also, Do you have a spare hard drive we could use for testing? We need one that we can remove everything on it. And please upload a new DM Log collector so I can try to see if anything has changed.

 

I updated my ssd firmware. My 3.3v is 3.284 my 5v is 5.070 and my 12v is 12.096
my cup temp is around 55-57*c and my system temp is 43*c and I don't have a spare internal hd

 

Here's my dm log (haven't had any new bsods today)

 

I've gotten some differecies in a bsod or two one says netio.sys

 

Loiez, sorry for the delay. This is what I found in the last 3 dumps.

Code: KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000004, The thread's stack pointer was outside the legal stack extents for the thread. Arg2: ffffd001456b7540, Address of the trap frame for the exception that caused the bugcheck Arg3: ffffd001456b7498, Address of the exception record for the exception that caused the bugcheck Arg4: 0000000000000000, Reserved Debugging Details:[/quote] Code: ffffd000`22c3bfa8 fffff800`bf61792cUnable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x21792c[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck 139, {3, ffffd001c414c5c0, ffffd001c414c518, 0} Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+de ) Followup: MachineOwner High Definition Audio Bus Driver[/quote] Code: APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->CombinedApcDisable field. This consists of two separate 16-bit fields, the SpecialApcDisable and the KernelApcDisable. A negative value of either indicates that a driver has disabled special or normal APCs (respectively) without re-enabling them; a positive value indicates that a driver has enabled special or normal APCs (respectively) too many times. Arguments: Arg1: 00007ffc5d7e3aaa, Address of system call function or worker routine Arg2: 0000000000000001, Thread->ApcStateIndex Arg3: 0000000000000000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable Arg4: ffffd00025e67b80, Call type (0 - system call, 1 - worker routine) Debugging Details:[/quote] Code: ffffd000`284a97a0 fffff801`eb7c1308 NETIO!handleTableLock ffffd000`284a97a8 fffff801`f0f1b002Unable to load image appexDrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for appexDrv.sys *** ERROR: Module load completed but symbols could not be loaded for appexDrv.sys appexDrv+0xb002[/quote] Code: ffffd000`284a8558 fffff801`ee50d97fUnable to load image athrx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys athrx+0x1ed97f[/quote] I think you can tell that the dumps are all over the place. In looking through the dumps It seems like most of the errors (not necessarily the ones mentioned above) Seemed to be either Network or hard drive related.

The athrx.sys is the Atheros network adapter driver. If that is a wireless driver, can you try running without it installed for a while please.

Please go to Device Manager and see if you have any listings with a yellow triangle or any other indications they are not working.

Make sure you have updated drivers from your Motherboard"s web site http://www.gigabyte.com/products/pro...px?pid=4727#dl

I believe you have said you updated your SSD to the most current software.

Please run Seatools for DOS on your Mechanical Hard drive.

The CPU temps you quoted seem entirely too high for your CPU. What CPU Cooler do you have?

 

A bit after I posted the dm log I set my driver for my wireless card back to the default driver

 

Try it that way, but it may end up having to remove the card. If it is a driver issue, it will still load the drivers when the card is detected on startup. But, try it that way and see if it helps.

 

Sorry for the delayed response but I've run into a bit of a problem with seatools. When I boot it up (from usb) it says no drives were found what should I do? (Ps I've been got a new bsod last night with the bug check of memory_management do I need to give you a new dm log?

 

Sure, upload a new DM log in a new post. With Seatools, make sure your BIOS Sata Controller is set to IDE. Seatools can't detect the drives set in AHCI mode. You will have to boot into bios and change to IDE and boot straight into Seatools. When the test is completed, go straight back into BIOS and change back to AHCI mode, then boot into the OS.

 

Thanks, should I do a long test even if the short test came up good?
And if so how long will it take?

 

Absolutely. The short test passes most of the times even with a bad drive. It's the long test that will really check it.

 

Well my mechanical hd passed the long test what should I do now?

 

I think you are just trying to give me a hard time. *Wink Let's try Driver Verifier.



Warning Be sure to create a System Restore point before proceeding further https://www.tenforums.com/tutorials/4...dows-10-a.html

DRIVER VERIFIER
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.


Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.


Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. 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 System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

There are no limitations. Use your computer any way you want. We are putting extra stress on the Non Microsoft drivers in hopes it will BSOD and catch the offending driver. Be sure you create a restore point before enabling Driver Verifier. Sort the drivers by Provider and enable it on every driver NOT provided by Microsoft. There is a slight chance you will have to do a clean install, but every precaution has been taken so that does not happen. It's beginning to look like you may end up doing one anyway.

 

It's the same thing.

See if this will help With Driver Verifier

[youtube]BjsofLPNosc[/youtube]