Register Now!

To Get More Info and Daily Reward.

Please login or register.
Pages: [1]   Go Down

Author Topic: X370 SLI PLUS and probably memory problem  (Read 378 times)

0 Members and 1 Guest are viewing this topic.

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
X370 SLI PLUS and probably memory problem
« on: 16-April-17, 08:26:44 »

Hi all, 

As in topic I have probably problem with memory stability, system is quite unpredictable, gives BSOD's regardless of what is going on.

What I've done already:
Lowered RAM sped from XMP rated 2666 to 2133
Rised RAM voltage by 0.05
Raised timings a bit
Fresh Windows 10 install
Memtest +20h no errors
Changed PSU
Tried different memmory slots
Bios update to 3.1

My Specs:
MSI x370 SLI PLUS
Ryzen 5 1600
AMD Rx480 8gb
PSU: Thermaltake 520W - > Chieftec GPS-600A8
RAM: Corsair Vengeance LPX 8GB 2666 CL16 = CMK8GX4M1A2666C16

BSOD's are randomly these:
KERNEL_DATA_INPAGE_ERROR
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
FAULTY_HARDWARE_CORRUPTED_PAGE
MEMORY_MANAGEMENT

And I'm out of ideas what to do next, system is running at stock.
Logged

darkhawk

  • Global Moderator
  • *****
  • Offline Offline
  • Posts: 8848
« Reply #1 on: 16-April-17, 13:33:15 »

What hard drive/SSD are you using?
What other drives do you have?

See : >>Posting Guide<<
Please list as MUCH hardware connected to the computer as possible. All PCIe and PCI cards, all USB devices, etc....the more information you can provide, the easier it is to troubleshoot the problems.

My current guess, going by the errors you listed, is that your HDD/SSD with your OS is corrupt/going bad.
If you can, possibly try installing Windows on another drive and seeing how it operates.
Logged
System #1 :
MSI Z97 SLI Plus
Intel i7 4770k @ 4.5 GHz @ 1.28VCore
16 GB DDR3 @ 2400 MHz
480 GB Intel DC S3500
2TB WD Black Edition
2TB Seagate HDD
MSI GTX1080 Armor Edition
Asus Xonar XTX

System #2 :
MSI B350 Gaming Plus
Ryzen 5 1500 X (stock speeds for now)
16 GB DDR4 @ 2400 MHz (Adata memory)
128 GB PNY SSD
320 GB Seagate HDD
MSI R9 280X

System #3 : 
MSI Z270 Tomahawk Arctic
Intel i5 7400T
16 GB DDR4 @ 2400 MHz (Adata memory)
128 GB PNY SSD
2TB Seagate HDD

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #2 on: 16-April-17, 19:39:55 »

Storage:
SAMSUNG 843T 240GB SSD DRIVE -> SYSTEM DRIVE
SAMSUNG ST200LM003 -> DATA DRIVE
No ODD drive

Other things connected atm are Mouse and Keyboard and Display via HDMI cable, nothing else.

Will try to reinstall on HDD without SSD and I'll post if it resolves anything. SSD/HDD combo worked fine in AM3 config but I'll try it anyway.

CPU cooling is Scythe Fuma + 4 case fans via PWM connectors on board.
Logged

Svet

  • T9246ED, Бивша комета
  • Administrator
  • *****
  • Offline Offline
  • Posts: 67216
« Reply #3 on: 16-April-17, 20:41:28 »

what are the BSOD error codes?
and when they comes while doing what?
Logged

lowrider87

  • CAPTAIN
  • ****
  • Offline Offline
  • Posts: 633
« Reply #4 on: 16-April-17, 21:56:59 »

Svet, he had these as some of the BSOD errors.

BSOD's are randomly these:
KERNEL_DATA_INPAGE_ERROR
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
FAULTY_HARDWARE_CORRUPTED_PAGE
MEMORY_MANAGEMENT
Logged
Thermaltake Level 10 Gaming Case
AMD Ryzen 7 1700 CPU
MSI X370 Carbon Gaming Pro Motherboard
PNY Anarchy Memory 32 gigs (P/N-MD16GK2D4213315AB)
Corsair H100i v2 Hydro CLC
XFX Radeon RX 480 8GB Graphics
EVGA 850W BQ PSU
Drive #1 - WD 1T
Drive #2 - WD 1T
Drive #3 Samsung EVO 250G SSD (disconnected)
Razer Black Widow Ultimate keyboard
Corsair 65 Rgb mouse

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #5 on: 17-April-17, 06:03:40 »

Same behavior on HDD drive, even tried it on different sata cable.

These are last BSOD's, they appear randomly, sometimes on Windows login page, sometimes while browsing and always in games, on OCCT GPU test no BSOD, Prime95 also no BSOD.

Code: [Select]
On Sun 16.04.2017 11:47:48
your computer crashed
crash dump file:
C:\WINDOWS\Minidump\041617-7234-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x1A
(0x41792, 0xFFFFFC813925E198, 0x10000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules. This problem might also be caused because of overheating
(thermal issue).
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.

On
Sun 16.04.2017 11:47:48 your computer crashed
crash dump file:
C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x1A (0x41792, 0xFFFFFC813925E198, 0x10000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This
indicates that a severe memory management error occurred.
This might be a
case of memory corruption. More often memory corruption happens because of
software errors in buggy drivers, not because of faulty RAM modules. This
problem might also be caused because of overheating (thermal issue).
The
crash took place in the Windows kernel. Possibly this problem is caused by
another driver that cannot be identified at this time.

On
Sun 16.04.2017 10:10:25 your computer crashed
crash dump file:
C:\WINDOWS\Minidump\041617-7515-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x7A
(0x1, 0xFFFFFFFFC0000005, 0xFFFF8D86BFE0E7C0, 0xFFFFF5FADF7B8000)
Error:
KERNEL_DATA_INPAGE_ERROR
file path:
C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This bug check indicates that the requested
page of kernel data from the paging file could not be read into memory.
The
crash took place in the Windows kernel. Possibly this problem is caused by
another driver that cannot be identified at this time.

On
Sun 16.04.2017 10:09:09 your computer crashed
crash dump file:
C:\WINDOWS\Minidump\041617-7375-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xFC
(0xFFFFCD8B47ABA990, 0x8A00000070E39963, 0xFFFFCD8B4AC6B1E0, 0x2)
Error:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to
execute non-executable memory.
This might be a case of memory corruption.
More often memory corruption happens because of software errors in buggy
drivers, not because of faulty RAM modules. There is a possibility this problem
was caused by a virus or other malware.
The crash took place in the Windows
kernel. Possibly this problem is caused by another driver that cannot be
identified at this time.

And BSOD's from old Windows 10 installation:
Code: [Select]
On Sat 15.04.2017 18:13:01
your computer crashed
crash dump file:
C:\WINDOWS\Minidump\041517-7390-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x12B
(0xFFFFFFFFC00002C4, 0xAA7, 0x10C8C1F0, 0xFFFFBC01896DF000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path:
C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This bug check indicates that a single-bit
error was found in this page. This is a hardware memory error.
This is likely
to be caused by a hardware problem problem. This error suggests a case of memory
corruption because of a hardware problem. It is suggested you do a test on your
RAM modules (memory test).
The crash took place in the Windows kernel.
Possibly this problem is caused by another driver that cannot be identified at
this time.

On Sat 15.04.2017 10:29:36 your computer
crashed
crash dump file: C:\WINDOWS\Minidump\041517-7078-01.dmp
This
was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x1A
(0x41793, 0xFFFFA70000815C28, 0x9, 0x8)
Error: MEMORY_MANAGEMENT
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 severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules. This problem might also be caused because of overheating
(thermal issue).
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.

On
Sat 15.04.2017 09:45:58 your computer crashed
crash dump file:
C:\WINDOWS\Minidump\041517-7218-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x1A
(0x41793, 0xFFFFED00000C5558, 0x9, 0x8)
Error: MEMORY_MANAGEMENT
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 severe memory management
error occurred.
This might be a case of memory corruption. More often memory
corruption happens because of software errors in buggy drivers, not because of
faulty RAM modules. This problem might also be caused because of overheating
(thermal issue).
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
Logged

Svet

  • T9246ED, Бивша комета
  • Administrator
  • *****
  • Offline Offline
  • Posts: 67216
« Reply #6 on: 17-April-17, 15:22:39 »

Quote
Prime95 also no BSOD.

which test from Prime95 you have ran and for how long?


Quote
RAM: Corsair Vengeance LPX 8GB 2666 CL16 = CMK8GX4M1A2666C16

can you borrow another one to try?


Quote
Changed PSU
PSU: Thermaltake 520W - > Chieftec GPS-600A8

both are not good or trusted..
Logged

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #7 on: 19-April-17, 18:57:24 »

Quote
which test from Prime95 you have ran and for how long?
In-place large FFTs ~ 20h
Also OCCT Linpack ~ 8h

Quote
can you borrow another one to try?
Sadly RAM is only one thing that i cannot borrow from anyone (no one has PC with DDR4).

As for PSU borrowed from a friend:
Be quiet! Pure Power 9 500W
But same results

Mix of BSODS can be triggered by 100% accurate HAVEN Benchmark (about 3 passes) or OCCT PSU test (about 10 minutes), sometimes at logon, or last one when opening thunderbird.
My old R9-380 VGA gives the same results as those tests pointed me towards GPU.
Also tried fresh Windows 10 installation with Creators Update = same result.

I'll probably buy some new stick from QVL as I'm out of ideas and with bit  useless new PC atm ;)
Logged

Svet

  • T9246ED, Бивша комета
  • Administrator
  • *****
  • Offline Offline
  • Posts: 67216
« Reply #8 on: 19-April-17, 20:43:52 »

Quote
In-place large FFTs ~ 20h
Also OCCT Linpack ~ 8h

Try also Blend test from Prime95 for at least 12 hours
Logged

dflippink

  • PRIVATE FIRST CLASS
  • ***
  • Offline Offline
  • Posts: 9
« Reply #9 on: 20-April-17, 05:05:33 »

I noticed you stated that you di the bios update to 3.1 after some of your other adjustments.. I'm not sure if it would help get your system stable again, but I would probably do a complete reinstall in this order.
1. Completely wipe your boot drive to one gigantic unallocated space..
2. Make sure all settings in bios are stock settings.
3. Make sure bios is 3.1
4.Make sure boot priority is set to UEFI and not Legacy+UEFI
5.Clean Install OS disconnected from any network and disallow any OS updates or Microsoft Account Logins... (not time yet)
6.Once in OS, install Factory MSI drivers first. (reboot if prompted)
7.Next install Factory MSI Utilities...(I only recommend Command Center, Mytstic Light, and Live Update at this point.)(reboot if prompted)
8.Next, connect to your network and open MSI's Live Update Utility..
9.At this point, automatically scan for updates, and only select the ones relative to chipset and hardware drivers.. (DO NOT select any utilities or application updates yet.) Select the Total installer option and reboot when prompted.
10.Now update the Live Update Utility alone as it can interfere with other utility update progress. (reboot when prompted.)
11. Now you can open Live update and update the rest of your utilities..
12.Install any other hardware Drivers or Utilities you have.(GPU's)
13.Reboot.
14.Log in to OS and Check windows for windows updates.
15.Enjoy!!

This should provide smooth sailing unless you are absolutely having a hardware issue.. I don't think our board are up to date with the latest AGESA code yet, so if and when you run Ryzen Master Utility, you will have to enable HPET.. just make ABSOLUTELY sure to disable it again when you are done with Ryzen Master Utility because it will severely cripple your performance. Good Luck
Logged

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #10 on: 20-April-17, 17:15:07 »

@Svet

Only about 11h but I  cannot run it longer atm:


@dflippink
I've done it literally yesterday, only thing was that I didn't install any app from MSI only Live Update
Logged

Svet

  • T9246ED, Бивша комета
  • Administrator
  • *****
  • Offline Offline
  • Posts: 67216
« Reply #11 on: 20-April-17, 23:27:21 »

oki, the system seems stable for this kind of tasks,
when you play games and its crashes,
this points to the video card or the PSU [or both]


Quote
Mix of BSODS can be triggered by 100% accurate HAVEN Benchmark (about 3 passes)

have you tried a different benchnmarks like 3dmarks or other games?
and have you tried to change the VGA drivers too?
Logged

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #12 on: 21-April-17, 09:32:14 »

So my problem has been resolved probably, friend of mine bought Intel platform with goodram memory that is on x370 qvl and everything worked like it suposed to, swapped back to my stick and problem came back, so as MSI cannot tell when or even if my stick will be on QVL I probably sell my stick and buy something that will most likely work.
Logged

darkhawk

  • Global Moderator
  • *****
  • Offline Offline
  • Posts: 8848
« Reply #13 on: 21-April-17, 10:57:25 »

So my problem has been resolved probably, friend of mine bought Intel platform with goodram memory that is on x370 qvl and everything worked like it suposed to, swapped back to my stick and problem came back, so as MSI cannot tell when or even if my stick will be on QVL I probably sell my stick and buy something that will most likely work.

Did you try your sticks in his system to see if they worked OK in his? It's still possible your ram may not be good...
Logged
System #1 :
MSI Z97 SLI Plus
Intel i7 4770k @ 4.5 GHz @ 1.28VCore
16 GB DDR3 @ 2400 MHz
480 GB Intel DC S3500
2TB WD Black Edition
2TB Seagate HDD
MSI GTX1080 Armor Edition
Asus Xonar XTX

System #2 :
MSI B350 Gaming Plus
Ryzen 5 1500 X (stock speeds for now)
16 GB DDR4 @ 2400 MHz (Adata memory)
128 GB PNY SSD
320 GB Seagate HDD
MSI R9 280X

System #3 : 
MSI Z270 Tomahawk Arctic
Intel i5 7400T
16 GB DDR4 @ 2400 MHz (Adata memory)
128 GB PNY SSD
2TB Seagate HDD

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #14 on: 21-April-17, 11:40:22 »

He is using it right now, will give me info on coupe od hours.
Logged

scapiTopic starter

  • CORPORAL
  • ****
  • Offline Offline
  • Posts: 12
« Reply #15 on: 21-April-17, 19:00:11 »

And...... they work, at least while gaming.
Logged
Pages: [1]   Go Up