PC has weird crashes

[andris.loiv]

I built my PC in mid-July, had to send the mobo back for bios update (2000 ryzen wasn't compatible) It was completely fine until the end of August, I think. With some win update, I started getting bsod's. Quite rarely, they still happen randomly. Sometimes not for many-many days. They usually go by MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL etc. Memory related bsods, I ran the windows memtest and memtest86 for quite a long time (about 10 hours) and no issues what so ever. And I very rarely have these.. black screens and PC restarts itself randomly. I have used BSV also, it gives me mostly ntoskrnl.exe issues (0x0000003b, 0x0000001e, 0x00000050)

My PC specs:

Ryzen 5 2600x @3.6GHz (stock) although the voltage seems very low - around 1 volt
Using the stock cpu cooler (temps around 52c under load)
Gainward Geforce GTX 1060 6GB
2x8GB G.Skill (the FlareX, that's compatible with Ryzen) RAM @2400MHz (stock) voltage is around 1.2v
Thermaltake TR2 S 600W PSU
Gigabyte GA-AB350M HD3 motherboard
Seagate Barracuda 7200RPM 1TB HDD (ST1000DM010-2EP102)
Windows 10 Home (edit: forgot to add it)

And the thing is, I can play games just fine - it has never crashed when gaming. Only when booting or just randomly idle/browsing. It can't be the memory, I've tested it too many times to count. Sorry for the long post, never done this before.

EDIT: The problem lied in DRAM voltage, was a bit too low for the component to be stable. Hope it helps someone to troubleshoot their PC.

 

[prince_xaine]

IRQL_NOT_LESS_OR_EQUAL is usually a driver issue. I would download some free software such as Driver booster from iobit.com and see if you have outdated drivers. Or you can do it manually.

 

[andris.loiv]

There was some sata driver that I had to update, will let you know when I get another BSOD

 

[dudio]

Your power supply is questionable.
I went thru two of those in a short period.
Do you have access to a better quality one to rule it out?

 

[andris.loiv]

Yeah I thought so also, but no, at the moment I don't. But I could try it in another system. The other system's psu doesn't have the 6-pin PCI-E connector so I couldn't power my graphics card. I could buy a new one soon though. I've also read, that these issues point towards the HDD also.
Edit: Yet shouldn't it crash during loads then? When I game or do some system stressing, everything's fine.
Edit2: Although if the PSU is the culprit, I could RMA it since I have the guarantee for it for 2 years atleast

 

[andris.loiv]

Here are my minidumps http://s000.tinyupload.com/index.php?file_id=76541335108355296532, just in case it helps

 

[johnbl]

two copies of HWiNFO64A.SYS running from different directories.
C:\WINDOWS\SysWOW64\drivers\HWiNFO64A.SYS Tue Mar 31 02:51:32 2015
C:\WINDOWS\system32\drivers\HWiNFO64A.SYS Tue Apr 10 07:40:08 2018

(remove the first driver)

first bugcheck was in a file system, two tables that should have matched did not match.

update the bios, then update to the current motherboard drivers and retest for failure.
https://www.gigabyte.com/Motherboard/GA-AB350M-HD3-rev-1x#support-dl-bios
(check to see if this is the correct motherboard. your bios version does not have the correct date and might have been a beta version, not sure)


machine info:
BIOS Version F23d
BIOS Starting Address Segment f000
BIOS Release Date 04/17/2018
Manufacturer Gigabyte Technology Co., Ltd.
Product Name AB350M-HD3
Processor Manufacturer Advanced Micro Devices, Inc.
Processor ID 820f8000fffb8b17
Processor Version AMD Ryzen 5 2600X Six-Core Processor
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 4250MHz
Current Speed 3600MHz

 

[andris.loiv]

Thank you for the answer. I haven't removed system drivers before, how should I delete it?
That is the correct motherboard, I'll update the bios as soon as I can

 

[johnbl]

I think you can delete the HWiNFO64A.SYS driver directly. other drivers are registered and stored in a hidden location. if you delete or modify them with out a proper setup program they get restored from the hidden copy after the next time your system reboot.
Always best to run a installer or uninstaller if you can.

certain driver version have to match your bios version which is why try to get copies of drivers from the motherboard vendor before you attempt to use windows generic drivers.

Thank you for the answer. I haven't removed system drivers before, how should I delete it?
That is the correct motherboard, I'll update the bios as soon as I can

 

[andris.loiv]

Can't delete it directly, it's open in some program it says. What uninstaller would you recommend? Sorry, haven't done this stuff before

 

[johnbl]

you should try and boot into safe mode and delete the file if you are doing it manually.
otherwise you have to use a uninstaller that installed the program. Problem is you have two versions of the same program that did the install.

i would go to https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and download autoruns64.exe then look in the menu and select hide microsoft entries
this should limit the amount of info you have to look at.
there will be check boxes, you can uncheck a driver and it will be prevented from loading on the next boot. this will make it so the file is not in use and you can delete it manually.
you can also delete the entry and the file will not load when windows boots. then it will not matter if you delete the file from your system.

Can't delete it directly, it's open in some program it says. What uninstaller would you recommend? Sorry, haven't done this stuff before

 

[andris.loiv]

Alright, I disabled the 2015 one, I'll boot into safe mode and delete it. Then delete the entry overall, after that the bios update and original mobo drivers

 

[andris.loiv]

you should try and boot into safe mode and delete the file if you are doing it manually.
otherwise you have to use a uninstaller that installed the program. Problem is you have two versions of the same program that did the install.

i would go to https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and download autoruns64.exe then look in the menu and select hide microsoft entries
this should limit the amount of info you have to look at.
there will be check boxes, you can uncheck a driver and it will be prevented from loading on the next boot. this will make it so the file is not in use and you can delete it manually.
you can also delete the entry and the file will not load when windows boots. then it will not matter if you delete the file from your system.

Can't delete it directly, it's open in some program it says. What uninstaller would you recommend? Sorry, haven't done this stuff before

By the way, I have a question, what does all this have to do with ntoskrnl.sys? Is it just some windows kernel driver that's conflicting with others?

 

[andris.loiv]

you should try and boot into safe mode and delete the file if you are doing it manually.
otherwise you have to use a uninstaller that installed the program. Problem is you have two versions of the same program that did the install.

i would go to https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
and download autoruns64.exe then look in the menu and select hide microsoft entries
this should limit the amount of info you have to look at.
there will be check boxes, you can uncheck a driver and it will be prevented from loading on the next boot. this will make it so the file is not in use and you can delete it manually.
you can also delete the entry and the file will not load when windows boots. then it will not matter if you delete the file from your system.

Can't delete it directly, it's open in some program it says. What uninstaller would you recommend? Sorry, haven't done this stuff before

Okay, I flashed my bios to f23, deleted that file and the entry of it. Did numerous reboots etc, seems to be quite stable at the moment. But can't be sure yet, since this thing didn't/doesn't have a certain pattern. I'll let you know when it blue screens on me again. Thank you in advance, couldn't have done it myself.

 

[andris.loiv]

Nope, still crashed, can't view the minidump file in BSV though. http://s000.tinyupload.com/?file_id=04741028452856596461 the error was KMODE_EXCEPTION_NOT_HANDLED

 

[johnbl]

file size shows as zero bytes. looks like the upload never finished.

when ever a device driver causes a bugcheck it will break in the driver itself or the windows interface to the driver. (the nt kernel file)

Nope, still crashed, can't view the minidump file in BSV though. http://s000.tinyupload.com/?file_id=04741028452856596461 the error was KMODE_EXCEPTION_NOT_HANDLED

 

[andris.loiv]

I will post the dumpfile when another bsod happens, not sure why it didn't finish uploading. I did the S.M.A.R.T check on my HDD also, no errors/issues there

 

[andris.loiv]

http://s000.tinyupload.com/?file_id=09891256107970564613 It happened yesterday, now it's not 0 bytes - hope it helps

 

[andris.loiv]

Another one happened just a bit ago http://s000.tinyupload.com/?file_id=41199642485783112669

 

[johnbl]

basically the system bugchecked because of a counter going below zero. the system counts references to data uses so it knows if the memory is no longer being used. tried to free up its use of a block too many times. this is most likely a programming error.

the running process was steam, normally i would suspect a network driver but in this case i would disable
your malwarebytes rootkit detector software and see if you still get a bugcheck.
your network driver looks very current but you might check for a update or roll it a back a version.

I could not read the bios info from this memory dump.
generally this means there is some sort of low level problem with the bios interface.


this is the file that makes microcode patches for bugs/errors in amd CPUs
\SystemRoot\system32\mcupdate_AuthenticAMD.dll ***** Invalid (84956950)
for some reason it is being marked as invalid.

generally the first line of patches are done with the bios updates, then when windows boots it loads the current cpu specific patches for the people that don't update the bios. (some motherboard vendors take months to put out bios patches, or stop after a year or two)

I would start cmd.exe or power shell as an admin then run
dism.exe /online /cleanup-image /restorehealth
just to see if it fixes this file. I would then make sure I install the current windows updates.

for this bugcheck you would need to change the memory dump to kernel and provide the much larger kernel memory dump file c:\windows\memory.dmp

it will have the pooltags markers so the debugger might be able to see what allocated the memory.

 

[andris.loiv]

basically the system bugchecked because of a counter going below zero. the system counts references to data uses so it knows if the memory is no longer being used. tried to free up its use of a block too many times. this is most likely a programming error.

the running process was steam, normally i would suspect a network driver but in this case i would disable
your malwarebytes rootkit detector software and see if you still get a bugcheck.
your network driver looks very current but you might check for a update or roll it a back a version.

I could not read the bios info from this memory dump.
generally this means there is some sort of low level problem with the bios interface.


this is the file that makes microcode patches for bugs/errors in amd CPUs
\SystemRoot\system32\mcupdate_AuthenticAMD.dll ***** Invalid (84956950)
for some reason it is being marked as invalid.

generally the first line of patches are done with the bios updates, then when windows boots it loads the current cpu specific patches for the people that don't update the bios. (some motherboard vendors take months to put out bios patches, or stop after a year or two)

I would start cmd.exe or power shell as an admin then run
dism.exe /online /cleanup-image /restorehealth
just to see if it fixes this file. I would then make sure I install the current windows updates.

for this bugcheck you would need to change the memory dump to kernel and provide the much larger kernel memory dump file c:\windows\memory.dmp

it will have the pooltags markers so the debugger might be able to see what allocated the memory.

Okay, thanks for the answer!
I had my PC on today for quite a while, didn't bsod, but I guess it's only a matter of time. I'll run that command and disable malwarebytes rootkit detector if it bsods. Should I worry about that bios problem or it's just some patching issue? Do I just upload the file or do I have to make some changes to the dmp file?

 

[andris.loiv]

This morning when my PC was booting, it bsod'd http://s000.tinyupload.com/?file_id=28664261497799911094

Edit: and 2 more later http://s000.tinyupload.com/?file_id=87624594594122890405

 

[johnbl]

your internal build number is 17134.1 the current update for that build is 17134.345
(basically, 345 build versions behind on windows setup updates)
you should try and get the updates installed or even do a clean install of the fixed
17763.55 that was updated oct 9 2018

otherwise you should look at all of the various updates in the old build and see if any have AMD cpu specific updates.

here is a link to the build info:https://www.microsoft.com/en-us/itpro/windows-10/release-information

the new build has a lot of fixes that block the malware getting into your graphcis code.

-----------------------




------------
I think you should change the memory dump type to kernel, then run cmd.exe or powershell as an admin then run
verifier.exe /standard /all
and reboot.

be sure you know how to get into safe mode in case the system bugchecks on boot.
use
verifier.exe /reset
to turn off verifier, you have to do this after testing or your system will run slowly until you do.

with a kernel memory dump the file will be saved as c:\windows\memory.dmp and will be much larger
it will contain all of the driver data and internal error logs.

the system bugchecked because of a access violation. I think it was in steam in a memory mapped file
(file that steam makes and runs in memory and is not on the disk)

I can not tell why the steam calls used a bad memory address.

debugger does not like your bios interface, many commands not working

This morning when my PC was booting, it bsod'd http://s000.tinyupload.com/?file_id=28664261497799911094

Edit: and 2 more later http://s000.tinyupload.com/?file_id=87624594594122890405

 

[andris.loiv]

Alright, I was away from home for a couple of days. https://ufile.io/thasa here you go, had to change site because of the file size

 

[johnbl]

down load service did not complete .
------------
your download service is throttling the download so it will take a hour rather then 20 seconds.

Alright, I was away from home for a couple of days. https://ufile.io/thasa here you go, had to change site because of the file size