MYRIAD Windows 10 errors/BSOD during installation & setup

Toggle sidebar Toggle sidebar
M

mada659

Commendable
Jun 2, 2016
4
0
1,510
I’ll start by saying that this is my first computer build, and that my knowledge of the subject is still..improving. Anyway, build is listed here:
http://pcpartpicker.com/list/rKGFf8

I have been trying to install Windows 10 on a new build, and have had weeks of complications trying to get through the installation, experiencing various BSOD screens at various stages. After multiple rounds of troubleshooting/doing the same thing 1000 times and ultimately reformatting the drive and starting over with the installation, I have managed to get the OS installed, but not without much of the same issues, and the system usually not staying stable long enough for me to install a Windows update or driver, retrieve a dump file, or really accomplish anything at all. These are all of the errors I have experienced multiple times.

During installation:
System Service Exception (dxgkrnl.sys)
System Thread exception not handled
Critical process died
Critical structure corruption
Kernel security check failure
Kmode exception not handled
Driver irql not less or equal
Page fault in nonpaged area (ntfs.sys)
Driver overran stack buffer
Memory management
IRQL gt zero at system service
Cache manager

After "successful" installation:
Attempted execute of non execute memory
Msrpc state violation
0xc000021a
Critical process died
Kernel security check failure
Apc index mismatch
Page fault in nonpaged area (win32kbase.sys)

Message box: "The instruction at 0x00007FFD0931747D referenced memory at 0Xffffffffffffffff. The memory could not be read."

Or sometimes the screen just goes black after login. And now it seems the paths of files I saved to the desktop are not working. Start menu doesnt open. System usually gets BSOD when you do just about anything.

Do these errors look as if this could be a hardware/compatibility issue, or just a driver issue? I am also skeptical of the SSD. Any help would be much appreciated!
 
Solution
J
try setting the command rate in the memory timings to 2 N or 2 T and test again with memtest86.
https://en.wikipedia.org/wiki/Memory_timings
often the BIOS will have this set incorrectly by default and the memory manufactures often don't make it clear what the setting should be.

It just seems like a common issue that pops up often.

also, each memory slot will have slightly different timings, it is just the nature of the electronics. You may be able to just move modules to around and get the system to pass. Generally, slots closer to the the CPU on the motherboard will be faster. (we are talking about very small timing numbers, but it has an effect at high clock rates. For 4GHz clock one clock tick is .00000000025 seconds)...
Sort by date Sort by votes
open command prompt with admin rights
type sfc /scannow and press enter

update all your motherboard drivers
update bios
update gpu drivres
then run driver booster and see what you missed

they all seem to be driver errors. Strange you got so many during installation though
you might want to run Samsung magician on the evo and check it out
run Data life guard on the WD drive: http://support.wdc.com/downloads.aspx?lang=en
 
Upvote 0 Downvote
how long does your machine stay up?

I would be updating the BIOS or reset it to defaults to get updated memory timings, then I would run memtest86 to confirm the memory timings are ok.
after that I would boot into windows 10 and run cmd.exe as a admin (windows key +x then type A)
then run
dism.exe /online /cleanup-image /restorehealth

if I still get a bugchek, then put the memory dump on a server, share the files for public access and post a link.
memory dumps are located at c:\windows\minidump directory by default.
 
Upvote 0 Downvote
I updated the motherboard drivers from the asrock website when I first was able to install windows. bios has been updated to the most recent version prior to the errors. I installed samsung magician, and configured for max performance, not sure if that messed things up.

The gpu driver .exe installation file worked once, but caused the computer to reboot. For a moment during its installation, the resolution changed, and looked like it was successfully installed before the system rebooted. Now even when not in safe mode, the resolution is comparable to that of safe mode, and the NVIDIA driver exe fails to install each time I attempt to reinstall it.

I ran sfc scannow in admin mode, in administrator account and few times it wouldnt complete before I received a DRIVER IRQL NOT LESS OR EQUAL bsod. finally got it to 100% but at the end received the error:
Windows resource protection found corrupt files and was unable to fix some of them data included in CBS.log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log . logging is currently not supported in offline servicing scenarios.
Simulatenously received an error message box: WerFault.exe – Application Error: The instruction at 0x0000yffe5e795b00 referenced memory at 0x000000000000005a. The memory could not be written. And when clicked OK, BSOD: PFN LIST CORRUPT
Been messing around with this troubleshooting process for the sfc scannow issues: https://www.infopackets.com/news/9620/how-fix-sfc-scannow-fails-wont-complete

Tried running Driver booster, and found 14 outdated drivers, ran it a few times over several reboots accompanied by irql driver error or critical structure corruption BSOD. After a few times it says now all drivers are up to date.

Its running memtest v.4.3.7 right now. Not really sure what the numbers are or should be telling me but its been running for 3hrs right now.
Pass 81%, 49% through test 8, 24 iterations, on pass 1 with 91 errors

Error confidence value:145
Lowest error address: 0001e533018- 485.1MB
Highest error addres: 0029aa46f78- 10666.2
Bits in error mask: cc000000
Bits in error- total: 4 min: 1, max:1 Avg: 1
Max contiguous errors: 1

But Still can’t really stay in a program long enough before critical structure corruption BSOD or similar aforementioned errors on restart. Resolution is also still crappy.

And up to this point I have actually had the WD HDD disconnected to simplify things.

Also, maybe unrelated, when I click eject removable media to spit out the usb Ive been using to transfer these drivers/programs, it gives me the option of ejecting the Samsung SSD 850 EVO 250GB. Is that normal to SSD's? I've never used one before, but it seems odd to me that it would give you the option to eject your main C: drive as removable media.
 
Upvote 0 Downvote


Machine usually stays up for a few minutes. if i try anything it will usually BSOD. Ill try when the memtest stops running
 
Upvote 0 Downvote
You have to get memtest86 to pass without any failures.
if the BIOS has been updated then all you can do is make sure the memory timings are set correctly in BIOS
in case the BIOS did not already select the proper memory timings. Then you would rerun the test.

using the dism command can help repair a windows install that occurred with bad memory settings.

if you can not get memtest86 to pass then you would need to try to isolate a bad ram stick or slot.
(pull out half of the ram and run the test again, and replace the ram until you can isolate a bad stick or bad memory slot)



 
Upvote 0 Downvote



The memory timings in bios appear to match what is advertised by the modules. if I increase the timings, could that potentially reduce errors? or is it safe to assume that the modules are bad if they cant operate without errors at their advertised timings. The last thing I was going to try was the other set of slots, to see if it was the motherboard...
 
Upvote 0 Downvote
try setting the command rate in the memory timings to 2 N or 2 T and test again with memtest86.
https://en.wikipedia.org/wiki/Memory_timings
often the BIOS will have this set incorrectly by default and the memory manufactures often don't make it clear what the setting should be.

It just seems like a common issue that pops up often.

also, each memory slot will have slightly different timings, it is just the nature of the electronics. You may be able to just move modules to around and get the system to pass. Generally, slots closer to the the CPU on the motherboard will be faster. (we are talking about very small timing numbers, but it has an effect at high clock rates. For 4GHz clock one clock tick is .00000000025 seconds) Memory clock rates are slower but still very small numbers. There has to be enough time for the electronics to setup the commands before the bits are read. If it is set too fast then the bits will be sample before they have reached the full voltage. the voltage determines if the bit is a one or a zero in binary.

Guess that brings up another point, sometimes you can fix these memory issues by increasing the voltage to the memory very slightly.








 
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