Overclock.net › Forums › AMD › AMD CPUs › BSOD Due to failing hardware or CPU?
New Posts  All Forums:Forum Nav:

BSOD Due to failing hardware or CPU?

post #1 of 7
Thread Starter 
Iv'e reinstalled Windows 7 about 3 times, and I still get the same old BSOD, same code, same error which is always pointing to "ntfs.sys"

Every dump file is the same.

The BSOD will still occur with CPU, Memory and Northbridge at stock settings, even with a increase in voltage.

Could it be my 2 year old OCZ Vertex 2 on it's way out? Or my RAM, CPU has degraded?

http://i1098.photobucket.com/albums/g379/RhysMcClean/ssd-1.png
ssd-1.png
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
post #2 of 7
First off, before I ask for the dump files to take a look, your overclock may be unstable. I would more than recommend bringing your system to default settings to ensure the system runs as it should at factory settings. If you do still crash after going back to defaults, follow the instructions below:

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.

If you cannot get into normal mode, please do this via Safe Mode.
post #3 of 7
Thread Starter 
Sorry I took a while replying back, I forgot to check, Here are the recent dump files.

dumps.zip 76k .zip file
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
post #4 of 7
Thread Starter 
Just had 2 more BSOD's since my last replied in the past 5 mins, here are the other 2 dumps.

All clock settings back to Stock.

I know when a BSOD is about to occur because whilst I'm broseing on IE, it starts to crash, become unresponsive, and Norton says it's corrupted tries to repair it self, then BSOD.

After power off from the wall and back on, everything is fine, it happens at random times, sometimes not for hours, or it can be jsut minutes.

dumps2.zip 51k .zip file
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
post #5 of 7
Quote:
Originally Posted by Atomfix View Post

Just had 2 more BSOD's since my last replied in the past 5 mins, here are the other 2 dumps.
All clock settings back to Stock.
I know when a BSOD is about to occur because whilst I'm broseing on IE, it starts to crash, become unresponsive, and Norton says it's corrupted tries to repair it self, then BSOD.
After power off from the wall and back on, everything is fine, it happens at random times, sometimes not for hours, or it can be jsut minutes.
dumps2.zip 51k .zip file

Try using one stick of memory. I had bad memory and things would be fine, then crash, then everything would start to crash, then BSOD. If it still happens, use the other stick. If you only have one stick then just follow everyone elses guides until you have ran out of ideas. Then get a 1 or 2 GB stick to test.
My PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 ASRock 970 Extreme3  MSI Radeon HD 7770 1GB Crucial Ballistix 8GB (4GB x 2) 1333 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate Barracuda 500GB  WD Blue 1TB ASUS 24x Hyper 212 EVO 
OSMonitorKeyboardPower
Microsoft Windows 10 64-Bit Acer AL1917W 1400x900 Logitech M275 EVGA 850w B2 
CaseMouseAudioAudio
Thermaltake V3 Black Edition Logitech M275 ATH-M50x Headphones Scarlett Focusrite 2i4 Audio Interface 
Audio
Mackie CR3 Monitors 
  hide details  
Reply
My PC
(17 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X4 965 ASRock 970 Extreme3  MSI Radeon HD 7770 1GB Crucial Ballistix 8GB (4GB x 2) 1333 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate Barracuda 500GB  WD Blue 1TB ASUS 24x Hyper 212 EVO 
OSMonitorKeyboardPower
Microsoft Windows 10 64-Bit Acer AL1917W 1400x900 Logitech M275 EVGA 850w B2 
CaseMouseAudioAudio
Thermaltake V3 Black Edition Logitech M275 ATH-M50x Headphones Scarlett Focusrite 2i4 Audio Interface 
Audio
Mackie CR3 Monitors 
  hide details  
Reply
post #6 of 7
Both latest dumps attached are x24 NTFS.sys culprits.

BSOD BUGCHECK SUMMARY
Code:
[code][font=lucida console]
Loading Dump File [C:\Users\BSOD\_jcgriff2_\dbug\__Kernel__\061612-10030-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun 16 07:09:30.041 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:51.102
BugCheck 24, {1904fb, fffff880021c2fa8, fffff880021c2800, fffff880014699c4}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFcb+54 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsReleaseFcb+54
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`021c2fa8 fffff880`021c2800 fffff880`014699c4
BiosVersion = 1402
BiosReleaseDate = 04/19/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\BSOD\_jcgriff2_\dbug\__Kernel__\061612-8096-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun 16 07:06:57.920 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:16.592
BugCheck 24, {1904fb, fffff8800c8a1198, fffff8800c8a09f0, fffff880014639c4}
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFcb+54 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sdclt.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsReleaseFcb+54
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0c8a1198 fffff880`0c8a09f0 fffff880`014639c4
BiosVersion = 1402
BiosReleaseDate = 04/19/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.

You have very many 3rd party drivers installed:
Code:
000.fcl                 Thu Nov 18 19:53:28 2010 (4CE5CA88)
AODDriver2.sys          Tue Mar 06 04:55:00 2012 (4F55DEF4)
ASUSFILTER.sys          Tue Sep 20 11:46:33 2011 (4E78B559)
AiChargerPlus.sys       Mon Nov 08 01:48:26 2010 (4CD79D3A)
AsIO.sys                Mon Aug 23 21:53:02 2010 (4C7325FE)
AsUpIO.sys              Mon Aug 02 22:47:59 2010 (4C57835F)
AtihdW76.sys            Thu Feb 23 07:30:12 2012 (4F463154)
BHDrvx64.sys            Tue Mar 13 16:02:37 2012 (4F5FA7DD)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
EraserUtilRebootDrv.sys Tue May 15 20:36:03 2012 (4FB2F673)
IDSvia64.sys            Fri Mar 09 16:57:02 2012 (4F5A7CAE)
Ironx64.SYS             Mon Nov 14 21:00:53 2011 (4EC1C7D5)
RTKVHD64.sys            Tue May 03 04:27:51 2011 (4DBFBC87)
SRTSP64.SYS             Thu Mar 15 14:09:13 2012 (4F623049)
SRTSPX64.SYS            Thu Mar 15 14:09:21 2012 (4F623051)
SYMDS64.SYS             Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMEFA64.SYS            Tue Nov 22 19:49:28 2011 (4ECC4318)
SYMEVENT64x86.SYS       Tue Nov 22 13:30:48 2011 (4ECBEA58)
SYMNETS.SYS             Sat Nov 12 16:11:53 2011 (4EBEE119)
ahcix64.sys             Thu Sep 23 05:48:46 2010 (4C9B227E)
amd_sata.sys            Fri Mar 04 15:45:41 2011 (4D714F75)
amd_xata.sys            Fri Mar 04 15:45:44 2011 (4D714F78)
amdiox64.sys            Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys             Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmthub3.sys            Wed Sep 14 03:36:19 2011 (4E705973)
asmtxhci.sys            Wed Sep 14 03:36:09 2011 (4E705969)
atikmdag.sys            Tue May 22 21:45:20 2012 (4FBC4130)
atikmpag.sys            Tue May 22 21:08:40 2012 (4FBC3898)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
dump_amd_sata.sys       Fri Mar 04 15:45:41 2011 (4D714F75)
eeCtrl64.sys            Tue May 15 20:36:03 2012 (4FB2F673)
mcdbus.sys              Tue Feb 24 05:34:07 2009 (49A3CD1F)
netr28x.sys             Tue May 19 09:48:40 2009 (4A12B8B8)
ntk_PowerDVD_64.sys     Tue Aug 03 05:04:12 2010 (4C57DB8C)
point64.sys             Wed May 18 04:07:20 2011 (4DD37E38)
usbfilter.sys           Wed Dec 15 05:34:49 2010 (4D0899C9)
xusb21.sys              Thu Aug 13 18:10:17 2009 (4A848F49)

Links to these drivers for updates / more info
Warning: Spoiler! (Click to show)
http://sysnative.com/drivers/driver.php?id=000.fcl
http://sysnative.com/drivers/driver.php?id=AODDriver2.sys
http://sysnative.com/drivers/driver.php?id=ASUSFILTER.sys
http://sysnative.com/drivers/driver.php?id=AiChargerPlus.sys
http://sysnative.com/drivers/driver.php?id=AsIO.sys
http://sysnative.com/drivers/driver.php?id=AsUpIO.sys
http://sysnative.com/drivers/driver.php?id=AtihdW76.sys
http://sysnative.com/drivers/driver.php?id=BHDrvx64.sys
http://sysnative.com/drivers/driver.php?id=ENG64.SYS
http://sysnative.com/drivers/driver.php?id=EX64.SYS
http://sysnative.com/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://sysnative.com/drivers/driver.php?id=IDSvia64.sys
http://sysnative.com/drivers/driver.php?id=Ironx64.SYS
http://sysnative.com/drivers/driver.php?id=RTKVHD64.sys
http://sysnative.com/drivers/driver.php?id=SRTSP64.SYS
http://sysnative.com/drivers/driver.php?id=SRTSPX64.SYS
http://sysnative.com/drivers/driver.php?id=SYMDS64.SYS
http://sysnative.com/drivers/driver.php?id=SYMEFA64.SYS
http://sysnative.com/drivers/driver.php?id=SYMEVENT64x86.SYS
http://sysnative.com/drivers/driver.php?id=SYMNETS.SYS
http://sysnative.com/drivers/driver.php?id=ahcix64.sys
http://sysnative.com/drivers/driver.php?id=amd_sata.sys
http://sysnative.com/drivers/driver.php?id=amd_xata.sys
http://sysnative.com/drivers/driver.php?id=amdiox64.sys
http://sysnative.com/drivers/driver.php?id=amdxata.sys
http://sysnative.com/drivers/driver.php?id=asmthub3.sys
http://sysnative.com/drivers/driver.php?id=asmtxhci.sys
http://sysnative.com/drivers/driver.php?id=atikmdag.sys
http://sysnative.com/drivers/driver.php?id=atikmpag.sys
http://sysnative.com/drivers/driver.php?id=ccSetx64.sys
http://sysnative.com/drivers/driver.php?id=dump_amd_sata.sys
http://sysnative.com/drivers/driver.php?id=eeCtrl64.sys
http://sysnative.com/drivers/driver.php?id=mcdbus.sys
http://sysnative.com/drivers/driver.php?id=netr28x.sys
http://sysnative.com/drivers/driver.php?id=ntk_PowerDVD_64.sys
http://sysnative.com/drivers/driver.php?id=point64.sys
http://sysnative.com/drivers/driver.php?id=usbfilter.sys
http://sysnative.com/drivers/driver.php?id=xusb21.sys

For now, to be sure this isn't software / 3rd party driver related, I'm going to recommend enabling Driver Verifier. Driver Verifier will carefully watch and stress all 3rd party unsigned-MS drivers and force a crash when it finds a fault in any one of those drivers and generate a detailed crash dump. If after enabling it you cannot get back into Windows because you're BSOD'ing upon startup (means it is finding a culprit driver that is called early or is on startup) then you'll have to disable it in safe mode. Also, if you do not crash within ~24 hours of enabling Driver Verifier, it's likely hardware and we'll move onto hardware diagnostics.
post #7 of 7
Thread Starter 
Update:

After installing new RAM, Iv'e been rid of all the BSOD problems Iv'e been having thumb.gif
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › BSOD Due to failing hardware or CPU?