Frequent BSOD's with ryzen 1700

[Suikero]

Hello,

few weeks ago i bought a used pc consisting of the following specs:

Ryzen 1700
Msi gtx 770 oc 2gb
G.skill trident z 2x8gb 3200mhz (Downclocked to 2133mhz)
Wd blue 1tb 7200rpm
Gigabyte ab350 gaming (not gaming 3!)
corsair vs 650
Silentiumpc case

During the first week of usage everything worked as expected. Shortly later i started getting frequently BSOD's with error messages such as IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED to name a few.

Another problem im getting is that my computer freezes and starts looping the specific sound playing at the moment. This seems to be appearing only when im gaming or watching videos/listening to music. Gpu crashing?

BSOD's occur mostly after 5-15 mins of usage, mainly when gaming. Gpu crashes seem to occur more randomly regardless if im gaming, watching vids, on fb or just afking without any softwares running.

Gpu temperatures hover between 60-70 degrees when in use, 40 when not in use. Same story goes for cpu's temperature are pretty much the same in usage and while afking. Gpu is running on stock factory overclocks and i have used cpu on both its stock speeds (3 ghz) and at 3.6 ghz, both with 1.1875 volts. Changing cpu clocks didn't have any effect on crashes.

When i got this computer, it came without a hard drive. I bought the hdd later. Meaning that i had to install everything, including os, from scratch.

I have all drivers up-to-date, tried between two different bios'es (f2 and f4) and the gpu is also running on newest drives. None of these helped me to get rid of any of my problems.

All of the parts are have warranty except for the gpu. Old owner also got these parts from multiple different locations. Cpu + mobo from place 1, ram from place 2 and psu from place 3, so its not as easy as returning the pc and telling them to fix it.

I have tried running stresstests for both cpu and gpu and they were both stable, so it shouldn't be the cause of this problem.

What should i do?

EDIT: 1.1875 cpu voltage, not 1.875

 

[Colif]

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

 

[Suikero]

I downloaded it and ran it. This was the response it gave me: https://gyazo.com/b1da21552192ae7baad5c7f8e6d92d78

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 21.4.2017 17.55.30 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF803F0E829E0)
Bugcheck code: 0xA (0x100118, 0x2, 0x0, 0xFFFFF803F0E829E0)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL



On Fri 21.4.2017 17.35.41 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042117-16437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800CFE79EB7, 0xFFFF90815B6D6E30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Paul NZ]

Upload the small dmp files to onedrive then post the link

 

[Suikero]

For some reason onedrive doesn't let me create a link for the files. It just says that "Link cant be created". When i tried uploading them to google drive, it said that i dont have the rights to upload it and that i need to ask adminstrators permissions to use it. Kinda weird since this pc only has one profile, and its labeled as adminstrator. I even checked from bios that i actually am admin on this pc.

Whats up with that?

 

[Paul NZ]

Have no idea. Try dropbox or mega nz

 

[Suikero]

Managed to upload them to google drive

https://drive.google.com/open?id=0B3GdXDQKlDXWUjJqOFBfbWNMWFU

 

[Calvin7]

Memory is for Intel Z170/Z270 Platform / Intel X99 Platform. It is way too fast for Ryzen 1700. SPD (Serial Presence Detect) speed of 2133MHz is for easy initial start up.
https://community.amd.com/servlet/JiveServlet/showImage/2-2784990-118085/sm_add-slide-2_800.png

 

[Suikero]

Could you simplify your answer a bit? im pretty noob in these things. So are you saying that downclock to 2133mhz is still too much for ryzen or am i missing something?

 

[Colif]

For some reason onedrive doesn't let me create a link for the files. It just says that "Link cant be created". When i tried uploading them to google drive, it said that i dont have the rights to upload it and that i need to ask adminstrators permissions to use it. Kinda weird since this pc only has one profile, and its labeled as adminstrator. I even checked from bios that i actually am admin on this pc.

Whats up with that?

the problem occurred because you don't have the right permissions from the minidumps folder but I have found if you copy the dump to another folder and then upload the copy it works fine. You seem to have got passed that now but if you ever need to do it again, just copy them to docuemnets first and upload the copy.

 

[johnbl]

could be a problem with the windows build, the motherboard or the new CPU
just can not tell because of the corruption of the memory dump.
(could even be a change in format for the debugger)

I will try to find some of the other 3 bad memory dumps and see if it on on one make of motherboard. I think they were all new gigabyte board withthe new CPU.


-------
something is wrong with the memory dump from your machine
the driver table is messed up.

new cpu and new motherboard, I would expect you have BIOS and driver problems related to the new hardware.

this is the 3rd or 4th machine to have this problem in the last few days.

all machines were running build
15063.0.amd64fre.rs2_release.170317-1834

this machine:
BIOS Version F2
BIOS Starting Address Segment f000
BIOS Release Date 02/20/2017
Manufacturer Gigabyte Technology Co., Ltd.
Manufacturer Gigabyte Technology Co., Ltd.
Product AB350-Gaming-CF
Processor Manufacturer Advanced Micro Devices, Inc.
Processor ID 110f8000fffb8b17
Processor Version AMD Ryzen 7 1700 Eight-Core Processor
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3000MHz
Current Speed 3000MHz

here is a example of the driver list that is bad:
\SystemRoot\System32\drivers\storahci.sys ***** Invalid (BFD6A9B0)
\SystemRoot\system32\drivers\tbs.sys Sat Jul 24 00:49:47 2027 (6C444C9B)
(clearly the wrong date)

but some are ok:
\SystemRoot\System32\DRIVERS\srvnet.sys Wed Oct 16 08:29:36 2013 (525EB0E0)

 

[Suikero]

So what do you suggest me to do johnbl?

 

[johnbl]

I installed the windows 10 creators update
the build number I got was build 15063.138
the build number shown for your build is 15063.0
I think you have a early build of the creators update
you might want to force a update to get to the current released build.
(just in case it is a problem/bug in your windows build)

I tried the new visual studio 2017 and it indicated it could not debug older .dmp formats.
the windbg.exe from march still shows corruption when reading your memory dump file.

it could be something like the system is not flushing the memory dump from cache memory. (maybe turn off lazy writes to the disk)
it should be found under the properties-> under the policies tab for your drive.
write caching policy
disable the selection called "enable write caching on the device"

also check the setting for "turn off windows write cache ah heck flushing on this device"
(you want to flush the buffers)


------------
I am installing the same windows build and all of the dev tools for that build. Just to see if it is a change that microsoft did with the debugger. Otherwise, I would be looking for bios and driver updates for your motherboard.
you might google "how to force a memory dump using a keyboard" then make the registry settings and force a memory dump right after you boot. Just to see if the memory dump is correctly formatted.
you might also make sure your pagefile.sys is of proper size, and that you have plenty of free space on your drive C:

also, what sata controller is your drive c: connected to? you might find that their is a bug in one controller driver and if you put the drive on a different controller the memory dump might work correctly.

So what do you suggest me to do johnbl?

 

[Suikero]

Hello,

i tried the fixes you pointed out. I'm still facing the same problem. Any ideas what to do?

New crash dumb analysis from whocrashed down below. Whocrashed says that my gpu drivers are causing most current crashes, gotta install a different one i guess. It still wont replace all my issues since i updated my drivers only few days ago...

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-M860A48
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: AB350-Gaming, Gigabyte Technology Co., Ltd., AB350-Gaming-CF
CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor AMD586, level: 23
8 logical processors, active mask: 255
RAM: 8539058176 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 10.5.2017 10.03.24 your computer crashed
crash dump file: C:\WINDOWS\Minidump\051017-25968-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x27904D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8064198904D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a2b0acab06663645\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 382.05
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 382.05
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.05 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED



On Wed 10.5.2017 10.03.24 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x27904D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8064198904D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a2b0acab06663645\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 382.05
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 382.05
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.05 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED



On Tue 9.5.2017 20.05.58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050917-18218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8017C2FF89E, 0x0, 0x3D0598A4)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8.5.2017 21.08.02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050817-16828-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x1AE138)
Bugcheck code: 0xBE (0xFFFFA05BC8BAE138, 0x810000012B02A021, 0xFFFFA2813A7FD4C0, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: Win32k-ytimen perusohjain
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 8.5.2017 13.54.29 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050817-18109-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.05 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[johnbl]

power problem to the GPU, I would make sure you do not have any overclock to the NVidia graphics card. you might even underclock the gpu memory to see if it is the problem.

0xFFFFFFFFC0000005 is a error code that means a bad memory address was used by a driver (in this case a NVidia driver)

the address looks like a valid kernel memory address rather than a clearly bogus one. This means you most likely have a timing/voltage/heating problem in your graphics hardware.
I would make sure you have updated your motherboard sound drivers, and your graphics drivers, then disable your high def audio devices that do not have speakers connected.

if you still have problems, you would check your power to your GPU connection, make sure your GPU fans are working. If your GPU is overclocked, set it to standard clock speeds for that GPU. if that fails see if you can lower your GPU memory clock speed by 100 or 200 MHZ and see if you get the same bugcheck.

note: make sure your bios is current or reset it to defaults and reconfigure after you have updated your motherboard drivers. It can fix hardware resource conflicts.