PC crash with error code (0xc0000428) and turns on and off by itself every 5 seconds.

[afrotv]

Title says it all. Random crash with that error code, but the visuals were distorted. It auto restarted and now just turns on (the case light turns on) and then turns off (the case light fades off.)

 

[Colif]

Did it give you a file name that was cause of error? Looking at this, it can be caused by winload which sure explain why it won't startup - https://neosmart.net/wiki/0xc0000428/ - see if fix 1 helps (I don't normally recommend 3rd party fixes but then Microsoft suggested it here - https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/status-0xc0000428-windows-cannot-verify-the/61e0a86d-b444-4d79-a027-46edb6a62aed)

0xc0000428: Windows cannot verify the digital signature for this file

 

[afrotv]

There probably was a file name, but the graphic was too distorted. It almost looked like artifacting. The entire screen was illegible.

 

[Colif]

Is this a brand name PC or Custom? If brand name, what make/model? if Custom, show me a list of parts.

were you playing a game when it crashed?

 

[afrotv]

Its a custom. MSI z97, 4790k, 8gb ram, Sapphire 290x, caviar blue. I took out the CMOS battery, ram, and GPU for a minute then reinstalled. It turned back on but the error came up again on desktop. At first it was a game, the second time it was desktop.

 

[Colif]

So PC boots or just does the on/off cycle?

if it doesn't boot, do you have a Win 10 installer? If not, on another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB - its a handy boot drive

Assuming it doesn't work, did you try the neosmart option above? From what I can tell the error often caused by winload.exe not working. That link might fix it.

otherwise, we see if we can get to the error dump that should have been created on 1 of the crashes.
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type notepad and press enter
notepad should open (amazing) and once it does, go to File/open and Explorer should open.
Navigate to C:\windows
change view to show hidden files/folders
If the MEMORY.dmp file is below several GB in size, cope it to a USB drive and on another PC, upload it to a file sharing web site and show link here. It should tell us what crashed.

If PC does boot to desktop, use file explorer to get the memory.dmp file and upload it for us.

 

[afrotv]

My PC doesn't boot. I press the power button, my desktop powers on for 3 seconds, and then turns off again. This repeats until I pull the plug. I cant even get to a page where I can do diagnostics. Here are some hardware tests that I've ran:

TEST 1---------
Variable: Took out GPU
Computer would turn on for 5 seconds and go back into the on/off loop

Test 2----------
Variable: Removed ram as well
Computer would turn on, but no peripherals would turn on. Did not turn off by itself.

Test 3----------
Variable: Only reinstalled the GPU
Results same as test 2

Test 4------
Variable: only one stick of RAM
Computer booted.

 

[Colif]

what happens if you unplug the hdd? I am expecting an error will occur but just curious.

the error code is just a windows error so shouldn't cause PC to turn off. I can see it causing the error trying to get into windows but it sounds like it doesn't even try to access windows, and just restarts.

Could be anything from an assembly error to a hardware malfunction.

First:
http://www.tomshardware.co.uk/forum/274745-13-step-step-guide-building
Maybe you made a basic mistake.

Second:
Work systematically through our standard checklist and troubleshooting thread:
http://www.tomshardware.com/forum/261145-31-read-posting-boot-problems
I mean work through, not just read over it. We spent a lot of time on this. It should find most of the problems.

Third (now it is time to get serious):
The following is an expansion of my troubleshooting tips in the breadboarding link in the "Cannot boot" thread.
http://www.tomshardware.com/forum/261145-31-read-posting-boot-problems

I have tested the following beep patterns on Gigabyte, eVGA, and ECS motherboards. Other BIOS' may be different, but they all use a single short beep for a successful POST.

Breadboard - that will help isolate any kind of case problem you might have.
http://www.tomshardware.com/forum/262730-31-breadboarding

Breadboard with just motherboard, CPU & HSF, case speaker, and PSU.

Make sure you plug the CPU power cable in. The system will not boot without it.

I always breadboard a new build. It takes only a few minutes, and you know you are putting good parts in the case once you are finished.

You can turn on the PC by momentarily shorting the two pins that the case power switch goes to. You should hear a series of long, single beeps indicating memory problems. Silence indicates a problem with (in most likely order) the PSU, motherboard, or CPU. Remember, at this time, you do not have a graphics card installed so the load on your PSU will be reduced.

If no beeps:
Running fans and drives and motherboard LED's do not necessarily indicate a good PSU. In the absence of a single short beep, they also do not indicate that the system is booting.

At this point, you can sort of check the PSU. Try to borrow a known good PSU of around 550 - 600 watts. That will power just about any system with a single GPU. If you cannot do that, use a DMM to measure the voltages. Measure between the colored wires and either chassis ground or the black wires. Yellow wires should be 12 volts. Red wires: +5 volts, orange wires: +3.3 volts, blue wire : -12 volts, violet wire (standby power supply): 5 volts always on. The green wire should also have 5 volts on it. It should go to 0 volts when you press the case power button (this is also a good way to test the power switch and the associated wiring), then back to 5 volts when you release the case power switch. Tolerances are +/- 5% except for the -12 volts which is +/- 10%.

The green wire should be 5 volts whenever the PSU is plugged in and the PSU switch is on. It will drop to about 0 volts when the case switch is pressed and go back to 5 volts after it is released.

The gray wire is really important. It should go from 0 to +5 volts when you turn the PSU on with the case switch. CPU needs this signal to boot.

You can turn on the PSU by completely disconnecting the PSU and using a paperclip or jumper wire to short the green wire to one of the neighboring black wires.
http://www.youtube.com/watch?v=5FWXgQSokF4&feature=youtube_gdata

A way that might be easier is to use the main power plug. Working from the back of the plug where the wires come out, use a bare paperclip to short between the green wire and one of the neighboring black wires. That will do the same thing with an installed PSU. It is also an easy way to bypass a questionable case power switch.

This checks the PSU under no load conditions, so it is not completely reliable. But if it can not pass this, it is dead. Then repeat the checks with the PSU plugged into the computer to put a load on the PSU.

If the system beeps:
If it looks like the PSU is good, install a memory stick. Boot. Beep pattern should change to one long and several short beeps indicating a missing graphics card (unless you have on board graphics available). In that case, remove any card and connect the monitor cable to the motherboard connector.
Silence, long single beeps, or series of short beeps indicate a problem with the memory. If you get short beeps verify that the memory is in the appropriate motherboard slots.

Insert the video card and connect any necessary PCIe power connectors. Boot. At this point, the system should POST successfully (a single short beep). Notice that you do not need keyboard, mouse, monitor, or drives to successfully POST.
At this point, if the system doesn't work, it's either the video card or an inadequate PSU. Or rarely - the motherboard's PCIe interface.

Now start connecting the rest of the devices starting with the monitor, then keyboard and mouse, then the rest of the devices, testing after each step. It's possible that you can pass the POST with a defective video card. The POST routines can only check the video interface. It cannot check the internal parts of the video card.

http://www.tomshardware.com/forum/334395-31-computer-turns-seconds-turning

 

[afrotv]

I opened MEMORY.DMP in notepad, but I don't think I have the means to read it(it just looks like wingdings). Side note: with one stick of ram, my PC has been on for 30 min with no problems.

https://drive.google.com/file/d/1wQJmurXThBdkw6Pf19vWumRa9MssWVq5/view?usp=sharing this is the dump file.

 

[afrotv]

I haven't tried unplugging the HDD. Since it booted, I have only done what you said to do in notepad.

 

[afrotv]

Do all motherboards follow those beeps for breadboarding?

 

[Colif]

quote is 6 years old, you may find the motherboard doesn't actually have a speaker to beep out of.

What are specs of PC? What motherboard? I can go find the beep codes associated with it then.

I will get someone to read dump files, he may not answer now though as I suspect he is asleep.

 

[afrotv]

I installed WDK to read it, but I cant find the .dmp file anymore. All I did was copypaste it over to the text document and close it. It doesnt appear in c:/windows anymore.

 

[Colif]

Well, its on your google drive so hopefully we can read that copy. You could always download that but you wouldn't have the permissions needed to put it in the windows folder, so the debugger may not find it. My friend has a program that can read them, someone else might reply before then who can read them as well.

oh, its a text file.. and a rather big one at that. I had thought you uploaded the dmp file

So you booted off the USB and accessed the menus through notepad... I wonder where the original dmp went. If its gone, one upside is it won't be as big next time.

 

[afrotv]

The file on the google drive is a .txt document and not a .dmp
I merely copy pasted the contents of the memory.dmp to a notepad to upload it.

 

[afrotv]

I didn't boot from USB. After reseating just one stick of RAM, the computer booted normally.

 

[Colif]

OK, i was a little confused about that.

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

the minidump will only be 256kb, slightly easier for my friend to download.

search cortana for reliability history
choose control panel option
any error should create a red X. Click on them and in the bottom panel, click on view technical details link. Copy/paste anything you find in here.

 

[afrotv]

It is getting late. I will get you more information tomorrow. Thanks for everything so far.

 

[afrotv]

I was messing around with the seating of the RAM sticks and I want to note this before I forget.
I am genuinely confused now.
Lets call them Stick 1 and Stick 2 and Positions 1-4.
Stick 1 Pos 1 = boot
Stick 2 Pos 1 = boot
Stick 1 Pos 2 + Stick 2 Pos 4 = on/off 3 second cycle with no boot.
Stick 2 Pos 2 + Stick 1 Pos 4 = boot
Stick 1 Pos 2 + Stick 2 Pos 4 = boot

I'm going to try and recreate the BSOD tomorrow.If I can't then I am lost on what to do. My only options right now are to wait for your friend (thats if the dump text file is readable) or wipe my HDD and clean install. I'll wait on the latter until its the last sole option.

 

[Colif]

Try using memtest86 to create a bootable USB. Use it to test each stick, 1 at a time, up to 8 passes. Only error count you want is 0, any higher is too many. Remove/replace sticks with errors.

Get some sleep, don't let PC keep you up all night.

 

[gardenman]

There's 2 basic types of files, text (TXT, HTML, etc) and binary (EXE, DLL, etc). Well there's probably other types but lets stick to the basics. When you open a binary file in a text editor such as Notepad, it loses alot of it's information. There are special characters in a binary file which cannot be displayed or opened in the average text editor. So it wasn't fullly loaded in Notepad and when you copied/pasted it lost alot of important information.

Want to see some special characters? Open notepad and hold down the Alt key and type 219. Then try Alt+178 then Alt+177 then Alt+176. Thats 4 special binary characters. Try to save the file (as a normal ANSI file) and you'll get a warning in Notepad, it will want to use Unicode. I use to run a BBS system and we used such characters all the time on our screens. I'm now off topic.

I did download the TXT file you posted and the debugger threw up an error which means the file was invalid (because of the copy/paste in the text editor).

Loading Dump File [C:\Users\UserName\Desktop\test.dmp]
Could not match Dump File signature - invalid file format
Could not open dump file [C:\Users\UserName\Desktop\test.dmp], Win32 error 0n87
"The parameter is incorrect."
Debuggee initialization failed, Win32 error 0n87
The parameter is incorrect.

Upload other dump files that you can get from your system and we'll look at those. Be sure to upload the original file, don't open them in notepad. You can ZIP them up if you like.

 

[afrotv]

I recreated the crash, and I have a new dump file, but when I try to upload it, it says that I don't have permissions. I've ran my browser as admin. How can I upload this?

Update: https://drive.google.com/file/d/1W8gr7FJKM96O_BFZH-HpAFW5-1_PZmcN/view?usp=sharing This is a new link with a dmp file instead of a txt file.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/op5n.html

File: MEMORY.DMP (Aug 9 2018 - 12:17:53)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: win32kfull.sys (Process: Steam.exe)
Uptime: 0 Day(s), 5 Hour(s), 59 Min(s), and 48 Sec(s)

Motherboard: https://us.msi.com/Motherboard/Z97-GAMING-5.html
I'm not sure that I've identified your motherboard correctly because you are using BIOS version 1.12 (from 2015) which is not listed on the motherboard's webpage. It could be that you are using version 1.C and it's just not being identified correctly in the dump file. Wait for Colif's opinion before trying to update your BIOS. Note to Colif: It could be a "hex" type of number, where version 10 is A, 11 is B, 12 is C, therefore meaning it's version 1.C which correlates with the date on the page.

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

I see you worked it out, you normally have to copy dump files to another folder and then upload the copies from that folder. Windows owns the 0riginals where they are.

Update your Killer drivers - https://www.killernetworking.com/driver-downloads/category/other-downloads

Do you have a MSI Z97 Gaming 3, 5 or 7? that bios number doesn't match dates on any of the boards.
Go to the utility tab of the support page for your motherboard and download Live Update 6, it will check the drivers installed and suggest new ones, probably including a new BIOS

 

[afrotv]

I updated everything through live update 6, and my computer doesnt boot with 2 ram sticks(both 0 error count) in slots 2+4 or 1+3, but it turns on for 5s instead of 2s now. The computer does however boot when RAM is in slots 1+2. Computer will only boot with 1 stick of ram or non dual-channel.