multiple bsod's WIN10 , can't find an answer

Toggle sidebar Toggle sidebar
Sort by date Sort by votes
looks like you are running a april 2018 build of windows with modified window user kernel.
I would start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth

it also does not look like you have applied any of the motherboard driver updates from the motherboards vendors website.

the bugcheck happened when because of a bad call using a invalid memory address (zero)

I would most likely just download the current version of windows and reinstall, then apply the motherboard driver updates. if you have a valid license you windows should activate automatically.
you can get the current windows build from here:https://www.microsoft.com/en-us/software-download/windows10
the dism command can fix your old built but you still need to apply the windows updates anyway. it would also save the effort of having to find out why the files were modified in the first place.

 
Upvote 0 Downvote
I would check to see where you got the image from, and make sure that windows updates are not being blocked.
some hacked versions, just fake the activation and fake the update check.
you might be able to just run the dism.exe command (below) and apply all of the windows updates to get to the current patch level.

https://www.microsoft.com/en-us/itpro/windows-10/release-information

run winver and it will pop up a box and tell you the windows version you have installed.i think I switched to the fast ring and now have

version 1809 build 17763.55 dated 1/9/2018


 
Upvote 0 Downvote
basically windows tried to verify a critical file, could not and it attempted to shutdown your system and got a bugcheck after 5 seconds of running.

the file was smss.exe that is use for session manager used to logon. the system thinks it was corrupted. I can not check this file. your other files seem fine in the debugger, I do not see any overclock problems. can you boot at all? maybe safe mode? generally if that file is messed up you would have to reinstall/repair.
------------
the error was
1: kd> !error 0xfc0000428
Error code: (NTSTATUS) 0xc0000428 (3221226536) - Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
 
Upvote 0 Downvote
you should run a malwarebytes scan to see
I would also run crystaldiskinfo.exe and check the health of the drive.
I would run memtest86 to confirm memory timings.

smss.exe can be a target of malware but windows checks it for modification and shuts down the system and restores a copy from a hidden backup on your system when the system reboots. Malwarebytes might find something trying to worm its way into your system.

the other two tests are just in case the problem was random bad luck corrupting a critical file.
(file on a bad sector on the drive, or being loaded into a bad spot in memory)
generally when I see certain file corruptions I assume it is a target of malware/virus/hack. some of the old malware will work on old unpatched systems but when run on new systems will generate a bugcheck. (to stop the problem)



 
Upvote 0 Downvote
the debugger does not like your bios interface. something is wrong with either the bios or some of the support files that depend on the bios.

the system detected a corrupted windows long on service, it whet to do a shutdown, then the power management got a error and that lead to the bugcheck.

when windows did a power management call it got a error:
!error 0xc0000004
Error code: (NTSTATUS) 0xc0000004 (3221225476) - The specified information record length does not match the length required for the specified information class.

I would make sure your bios you have installed matches your motherboard version
then check to see if the motherboard driver has any power management support driveres.

I would also go into bios and reset it to defaults or start turning off functions. Like the power management or any speed step functions. make sure there is no overclocking in bios. make sure the pci/e bus is set to run at 100mhz

I would also change the memory dump to kernel and provide the next kernel dump
the file will be c:\windows\memory.dmp it will be larger than a minidump but will include more info on the hardware and the internal error logs.


 
Upvote 0 Downvote
looks the same as before.
system bugchecked after being up for 5 seconds,
smss.exe did not pass verification
bios information was messed up again.

maybe, changed the memory dump to kernel, then google "how to force a memory dump using the keyboard"
then reboot, and while the system seems to be running ok, force a kernel memory dump. provide the c:\windows\memory.dmp (kernel dump)
I can take a look and see if there is something suspect running or errors in the internal error logs.

you could also start cmd.exe or powershell as an admin then run
verifier.exe /standard /all
it will turn on driver checking and might catch a driver writing outside of its assigned memory space.
if it does it will call a bugcheck and stop the system and name the driver in the memory dump.
NOTE: be sure you know how to get into safe mode in case the system bugchecks on the next boot.
so you can turn off verifier via
verifier.exe /reset
also note: after done testing you have to turn off verifier or your system will run slowly until you do.








 
Upvote 0 Downvote
kernel is modified, bunch of windows core files modified.
would guess it is some rootkit/malware problem.

there are unexpected drivers being loaded. like some old setup program running in 32 bit subsystem tried to install windows core files on a 64 bit version of windows.

these are files that would not normally be installed. The strange thing is one of them looked had a current windows version build number on it.

I would wipe and reinstall. I would suspect the last setup program you ran as a source of the problems. maybe you need to find a 64 bit setup program.

at this point you will have to wipe and set things up again.

old programs from windows 7 and before might make hacks into core windows files. this is not allowed any more and windows will call a bugcheck if it is detected.

--------
looks like your system had two copies of smss.exe running from










 
Upvote 0 Downvote
i've reinstalled like 6 times, the only programs i got installed are discord,teamspeak,chrome(tried firefox on other install),fortnite and nvidia drivers. do u think any of them can be messing up the system?
 
Upvote 0 Downvote
well do the install, make sure bios and motherboard drivers are up to date. reboot and then install the nvidia gpu updates. reboot and apply any microsoft updates.
at this point you should be ok.

when you install the game

do not install discord or teamspeak or if you do, get them from some official link, and configure it manually.
I would guess that is where the problem is coming from. look in the windows task scheduler to see if some tast is scheduled that should not belong. often malware will schedule a task for hours after you run a program so it harder to tell what caused the problem. these add on programs are a good way to hack into someone's system and steal passwords. that is why the newer version of windows are making more checks and shutdown the system if hacks are found.
I have been given hacked discord and teamspeak setup programs from people I game with. often from their semi private website. manually config your software from a direct download from the vendor





 
Upvote 0 Downvote
disable all of the tasks you have shown.

i would also check your services and disable the intel content protection service.
(Intel(R) Content Protection HECI Service) or uninstall
INTEL SUR QC Software Asset Manager
it sounds like a old program that might be mucking around and conflict with the current windows 10 protections.






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

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom