Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: djactivator on June 06, 2017, 04:18:15 am
-
Good day my computer geeks/pros! PlEASE HELP ME!
I've purchased BRAND NEW computer components about 2 years ago and just recently about 6 months ago put together the system, specs are as follows:
Microsoft Windows 10 Professional (x64) Build 15063.332 (RS2)
ASRock 970 Performance Bios P1.30
CPU: AMD FX-8350
Video: GIGABYTE Radeon R9 280 WindForce 3X OC
Memory GSKILL - 14900CL10-8GBXL x2
I also have 2x brand new 4TB Seagate ST4000DM005-2DP166 SATA HDs
and one Samsung SSD 850 EVO 250GB for my windows 10 & apps installs!
My system keeps giving me BSODS & random freezes, tried tons of the online solutions and nothing seems to work. I need to figure out which hardware if hardware is causing the issue so I can replace it.
I have had this issue ever since I build this system about 6 months ago, removed my old drives, put in the new ones described above did a clean install of windows 10 pro and still same issues.
Any ideas???
-
I'm not really into hardware as I use laptops but you could start by removing the two Seagate drives, see how it runs and then add each one back alternatively to see if either is the cause of the BSODs.
So that your machine will run, if it does with just leaving it with the SSD, download BlueScreenView which will diagnose the Memory Dump Files, but were you able to make a note of the Stop Error Codes.
http://www.nirsoft.net/utils/blue_screen_view.html
I'll contact another member who is more used to dealing with BSODs but will need the info I've asked for, although he'll probably ask you to upload the Memory Dump files if BlueScreenView doesn't give him all of the info he needs.
-
This has nothing to do with the drives, I was having the exact same issues with my older drives, the only drives in the machine now are all brand new, all of hte old drives have been removed, CMOS has been reset, latest version of BIOS is installed and windows has been FRESH installed.
-
Hi, guys.
The main list output from BlueScreenView with the BSOD codes from all the dumps in the top pane should prove useful to begin with.
I'd leave the temporary removal/disconnection of all non-essential hardware until after we've gained some idea of where the problem lies, commonly it's software - 3rd party drivers/filters or security software (whether currently installed or remnants of any previously removed).
Details of the PSU, make/model/wattage, etc., as well please :)
Is it all at stock speeds/voltages?
-
Everything is at stock voltages yes, no OC anywhere here.. just defaults including even the BIOS settings.. the PSU is a coolermaster 650 GX
http://www.coolermaster.com/powersupply/gx-series/gx-650w/
-
What about BlueScreenView ?
-
just had my first BSOD since just installing BlueScreenview about half hour ago, not sure what I am looking for but I have Bluescreenview up with the DUMP file loaded into it..
-
I did a generate HTML thing and this is what it gave me
060617-7343-01.dmp 2017-06-06 9:52:47 AM 0x00000139 00000000`00000003 ffffd881`a36ab080 ffffd881`a36aafd8 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c310 x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\060617-7343-01.dmp 8 15 15063 789,508 2017-06-06 9:53:30 AM
-
Not sure which GX you have, there are 2 models, one certified 80Plus, the other 80Plus Bronze, different makers for each. The older 'white' 80Plus spec. model is pretty poor, from what I can tell. The later Bronze model should be better on most counts, if you have a good sample it might be adequate or better, a poor sample wouldn't be something I'd fit in a build like yours.
Was it bought new for the build or is it older? If it's older, it might be time to retire it. Can you borrow a good quality PSU that you can use for testing?
Can you explain what happens in the seconds before a crash, what programs/games are running, what screen resolution you use?
Yes, a screenshot of the main BlueScreenView output is needed :) You need to set Windows so that it collects minidumps and that it doesn't overwrite older dumps (waiting for a crash isn't required, start BSV and it will auto-load any dumps found).
Or use the collection routine/program here (https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html) and attach the need logs/zipped folder.
A 0x139 crash as yours is can be very tricky to sort out but it initially looks more like a possible software/driver problem, more info/data needed.
-
The GX is older, took it from another system that I built maybe 5 or more years ago, when I took the PC into the repair shop the guy said he did a diagnosis on it, he said it was fine, this was about 2 months ago, he said it was fine but if I need to replace something asap it would be the PSU, no, there is nobody I can borrow a PSU from for testing.
Unfortunatey I cannot pinpoint why and when it crashes as it freezes/BSOD at total random times. Sometimes I am just browsing hte web, sometimes I am playing mp3s in winamp... other times watching a video on youtube.. sometimes just putting some notes into notepad, complete random freezeups and BSODS..
I have attached a screenshot of BluescreenView as well.
-
Hmm, doesn't really sound like a power issue, unless there's *something* happening in the background that adds some extra pressure occasionally. That doesn't mean I'd trust that PSU though ;)
Can you copy that minidump to your Desktop then zip it and attach the zip, please? You might have to enable viewing of hidden files and folders to get to it.
-
How do i enable viewing of hidden files and folders, it let me copy it to the desktop but is giving me some security message when trying to rar it to attach it
-
If you can see it to copy/paste it to your Desktop, it's not a hidden files/folders issue, it's probably Permissions - try moving the copy on your Desktop to your Documents folder, you should have Permissions to do (almost) anything there. Or try compressing it from the normal right-click options.
-
ok, here it is the dump
-
There are some possibly buggy software/drivers installed that I'd like you to uninstall:
ASRock V Drive (driver=AsrVDrive.sys), shouldn't be necessary, you're on x64 and have UEFI:
"The fantastic 3TB+ Unlocker tool offers a tweak-friendly feature, breaking the limitation of 32-bit operation system that could only detect the hard disk within 2048GB. It also allows ASRock motherboards without UEFI Technology to take advantage of the hidden storage space on 3TB and larger HDDs, helping to fully utilize the wasted spaces." Same goes for any other ASRock utilities, uninstall them during troubleshooting.
HWiNFO64, fine in my experience but we need to rule out as many 3rd party drivers/filters as possible, can be reinstalled once troubleshooting is over.
uTorrent was the active process during the crash, it's possible that it's involved somehow, maybe Defender/SmartScreen picked up a 'suspicious' data string being received. Uninstall it during testing.
Ensure that you don't have any excess AMD/ATI dross loaded with CCC/Crimson, drivers only (without CCC/Crimson, if that's still possible!) if you can.
Make sure that CCleaner (or any other cleanup tool) isn't set to start or to remove minidumps, we need all the data/logs that we can - best to uninstall it/them during testing.
Basically, you need to run the System as slim as possible, if it isn't vital for the work/games that you use - uninstall it, or at least, make sure that it doesn't load on startup.
-
ok, how do I remove the ASRock V Drive driver?? unless u are speaking of the fantastic 3+ TB unlocker tool which has now been removed, i also uninstalled HWINFO64, utorrent has also been uninstalled. how do I ensure that I don't have any excess AMD/ATI dross loaded with CCC/Crimson and its the drivers only without CC/Crimson, I also made sure CCleaner will not delete any of hte dumps and i also selected the dumps to be saved (all) instead of overwritten but for now I will just uninstall CCleaner too..
-
Good work :)
Yes, I was referring to the Unlocker: "The fantastic 3TB+ Unlocker... " but all I have for data is the dump, which lists the driver, AsrVDrive.sys.
Start up CCC/Crimson and uninstall everything there that isn't required - most users only really need the drivers.
Okay, next step: run MSiNFO32 and click on each section/subsection to make sure they're all fully populated with data (there will probably one or two subsections that won't contain anything). The Windows Error Reporting at the end is one of the slowest, click your way down through the list and wait on WER until it's populated then Save As the default .ARN type, zip that and attach it, please.
-
so I went to add/remove, went to modify of AMD Software and clicked on Clean uninstall on everything except for the video driver
-
Hmm, doesn't quite read like the terminology I was expecting but I've not had an ATI/AMD card in use here since late last year, so I can't check. See how it looks after a reboot.
-
So I did that, restarted the computer and my system went to the desktop but I had no mouse, I than hard turned off and back on again, now I am back in the OS with working mouse...
-
Ah yes, you're also battling the vagaries of Creator's Update, keep notes on anything unexpected/unusual.
Can I have the MSinfo32.arn data next?
-
How do i generate and send you the msinfo32.arn next?
-
Search for it - System Information or msinfo32 - and run it (as Administrator, maybe), it's likely to be in Windows/System32.
-
Here we go,
it generated a txt file
-
No, it would take me forever to make sense of that, I'd probably give up first.
Can you save it as the default .ARN type and zip/attach that, please.
-
I cannot figure out how to save it as ARN.. default is NFO
-
default save is NFO, export default is txt
-
Sorry, my bad, NFO it is. I was on autopilot, .ARN would be a possible follow up step using Autoruns.
-
here is the NFO
-
Thanks, core details (hardware drivers, loaded System drivers, Services) look good :) Nothing there jumping out at me, seems to be a solid base.
Running software:
Reimage - I'd not use this, my experience/testing of it showed it using scareware tactics, I belive it's unreliable and could easily cause more issues than it claims to be able to 'fix'. If you can revert any changes already made by this, please do so and then uninstall it completely.
Chrome: just be aware that running Chrome in the background might cause issues whilst gaming, I rarely use it and it's hardly ever installed here but I did have some *interference* from somewhere during a gaming session several months ago. Chrome was the only 'different' software running, with just four tabs open. I've not had those issues before or since and my default browser (Pale Moon) is almost always running with 50+ tabs and 1.6-3+GB memory in use over sessions that might have very long (4-19+ days) uptimes.
Other than the BSOD issues, WER (Windows Error Reporting) has only logged issues with your torrent software (uninstall and try a different software?) and Chrome, so far ;).
So, apart from Reimage, it looks pretty good to me.
EDIT:
I've delved deeper into the WER for the BSOD types and checked those against John Carrona's (usasma) database (http://carrona.org/bsodindx.html#Example) to check for any causes that might be common to all the BSOD's. Apart from the latest 0x139 (which might be a torrent client using too many connections), all the others listed in the WER could be down to the same 'bad' driver:
0x139:
???? but might be torrent software here, see https://support.microsoft.com/en-us/help/2883658/-0x00000139-stop-error-on-a-windows-server-2012-based-computer-that-has-many-tcp-connections
0x7f:
Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
0x3b:
System service, Device driver, graphics driver, ?memory
0xa:
Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
0x1e:
Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
0xd1:
Device driver
Use the PC normally for the next few days/week or so, if you do have another BSOD, collect and attach the new dump(s) and fresh MSInfo data and attach them to a reply. Then read and follow carefully the steps here for using Driver Verifier (https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-blue-screen-death-related.html), we need to stress the loaded drivers to see if there's still a bad/suspect one loading.
-
I once inadvertently installed Reimage and it was a sod to fully uninstall even after using the free version of IObit Uninstaller - I still found bits of it in the registry afterwards.
If you still get the BSODs then first try it in Safe Mode with Networking and if they continue, then just in Safe Mode.
I don't think the AMD Crimson Beta was for that GPU - I know I got it for my Radeon HD6310 and it adds Quickstream and Raptr.
It also adds AppEx Networks Accelerator to the Properties of the Network adapters which result in reduced download speeds.
I got rid of all of those.
I was unable to read the memory dump file as I don't have anything on here to read .rar files and have never been able to get 7zip to work on this machine.
-
Here's the same dump zipped.
-
Thanks, Andy, but couldn't get that to open with IE either on a Win 10 or Win 7 machine.
-
IE? No messages from SmartScreen that would account for it, Tom?
(I think SmartScreen on Creator's edition goes a step further than just 'protecting' IE/Edge and tries to cover other browsers as well. Not sure though and I'm not going to install it anytime soon to test ;) .)
-
How do I get rid of AppEx Networks Accelerator ????
-
Well Shane had emailed me a .zip for the beta version of v4.0 of his Windows repair program and SmartScreen didn't show its face then either.
I did however get the usual UAC to run it.
Your zip did extract and Win 10 gave me the option to open it but initially all I got was a blank window and later I just got the manage downloads window to either open or save and I only got the manage downloads window when I tried it on a Win 7 machine.
-
How do I get rid of AppEx Networks Accelerator ????
Go Start - type ncpa.cpl and press enter when it comes up.
Right click on whichever adapter you are using and select Properties where you will see it listed and uncheck its box - OK
I think I also uninstalled Quickstream which it was part of for me.
I'm using an Intel based laptop at the moment so will have to open the AMD one to check if it's still there but unchecked.
EDIT - Just checked and it's no longer listed so I assume it was fully removed when I uninstalled Quickstream but unchecking it will disable it.
-
Ok, so... my computer just gave me IRQL_NOT_LESS_OR_EQUAL 2x in the last like 20 minutes.. both times with utorrent running in the background, running one test now without running utorrent..
-
Was it still the same Stop Error Code ?
µTorrent can be prone to having infections in it - not sure if that is the cause of the BSODs.
Performing a clean boot may ID what could be the cause if it's software related.
Which antivirus program are you using ?
-
Here is a new DUMP
-
So, here is a brand new BSOD never seen this error message yet..
ATTEMPTED EXECUTE OF NOEXECUTE MEMORY Error
I have a feeling its the memory, i have 2x8 gig sticks installed. wondering if they are configured properly will insert them to A1 slot one by one to see if its just one or both that are faulty..
sorry, no dump was created...
-
0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Usual causes: Device driver
Have you uninstalled your torrent client(s) yet? If not, please do so now.
Time for Driver Verifier (https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-blue-screen-death-related.html), this is designed to stress the drivers and BSOD with a verified dump when it finds a suspicious one. Setting up DV can cause a PC to be unbootable so you need to read and follow the instructions carefully.
-
Yes I have uninstalled the torrent client and installed another, system has been stable all morning so far.. how do i use driver verifier?
-
Explained in the post here (https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista-post87.html#post87).
Based on MS' details here (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/verifier-command-line).
-
Okay, so I have followed the explained post below, I have since had a BSOD.. where are the files I can attach to this?
-
The crash minidump should be in the usual folder, C:\Windows\Minidump.
If it isn't, run MSInfo32 again and attach the NFO file.
-
okay so, I am trying to generate a new minidump for you guy and but it seems the BSODs have stopped as of this morning, however... my computer froze up 2x in the last 4 hours and no minidump was generated
-
here is a new NFO file from msinfo32
-
When I've had a look at the msinfo32 Components/Problem Devices I see a blank entry as if something should be there - mine just has a pure blank window.
What do you see when you expand Components/Problem Devices ?
There's another program that may list those and that is MiniToolBox - http://www.majorgeeks.com/files/details/farbar_minitoolbox.html
If your antivirus program complains about it, you may have an option to let it continue.
Just checking the box for problem devices may do but you can check all of them if you wish.
It produces a MTB.txt file which you can either upload as it is or copy & paste by right clicking in the text area - click on Select all - right click again and select Copy to right click in the Reply box and select Paste.
-
here is the full with everything
-
Did your msinfo32 list anything in Components/Problem Devices ?
Did you leave just the button checked so that it listed only problem devices in MTB ?
Satrow may be able to make more sense out of those Event Errors but you can resolve the CldFlt one by going Start - type regedit - press enter and accept the UAC.
Then navigate HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001\Services\CldFlt
When you click on CldFlt look in the right pane and right click on Start and select Modify then change the value from 2 to 4 - OK
Close up the sections then click on File/Exit and the next reboot will not have that error listed in Event Viewer.
-
Ok, so I have 3 drives in this system.. 2x4 terrrabytes for data/games etc... and 1x250 SSD installed for OS / Apps .. i noticed that when it ry to copy files between the 2 brand new 4 TB drives my system crashes... any ideas????
last BSOD I got was trying to install a game onto the drives gave me a MEMORY_MANAGEMENT BSOD.. its not the drives, i was h aving the same issue with my older drives as well that are not longer in the system, is this a memory issue? Motherboard busted??
-
If you are still running Driver Verifier, open a Command Prompt (Admin) and enter verifier /reset followed by shutdown /r /t 00 to effect an immediate reboot.
Satrow isn't too well at the moment but I've been in contact with him and he agrees now that you should disconnect the two 4TB Seagate drives so as to concentrate on just the OS.
You have said that you were getting the same problem with the older drives as well, so they could be the common denominator.
You can test the memory by using a bootable disk or USB of Memtest86+
Here are a couple of tutorials but run the test on just one RAM stick at a time for at least 8 passes.
http://www.techfleece.com/2013/07/01/how-to-test-your-ram-sticks-using-memtest86/
https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html
Did you get the right memory for the motherboard ?
As for MiniToolBox can you run it again but with just the box for List Devices checked and only the default button for Only Problems checked.
Leave those two Seagate drives connected when you run MTB so that it can check all devices.
In Device Manager/View/Show hidden devices expand System Devices and check for any yellow alerts, but you can check to see if there are any updated drivers for the Chipset ones and any other by right clicking on them and selecting Update Driver.
-
i swapped out the memory, still having issues, BSOD/Freeze when moving larger files from one drive to another
-
Can you run MiniToolBox as I've asked with just List devices and only the Problem devices button default checked.
-
just did that and here is what I got:
MiniToolBox by Farbar Version: 17-06-2016
Ran by djste (administrator) on 11-06-2017 at 07:05:04
Running from "G:\Downloads"
Microsoft Windows 10 Pro (X64)
Model: To Be Filled By O.E.M. Manufacturer: To Be Filled By O.E.M.
Boot Mode: Normal
***************************************************************************
========================= Devices: ================================
**** End of log ****
-
Thanks - that tells us a lot :thinking:
While you say you are getting the BSODs/freezes when trying to transfer data, can you check to see if you get BSOds etc. with those two HDDs disconnected.
Normally when you get problems with a new build you would strip down to just the basics for the computer to run and then add one bit back at a time.
Has Event Viewer anything recorded for the freezes ?
I can't read the memory dump files when you use .rar to zip them up.
-
How do I check event viewer?? Does it generate a log too that would help us narrow this down?
-
It's possible.
Right click on the Start button and select Event Viewer and when it opens, ensure Event Viewer (Local) is highlighted.
When it has read the data, click on Errors and then on View All Instances of This Event in the lower right pane and then look for events with a time stamp for when the BSODs or freezes occurred.
Clicking on each will display more info in the scrollable window below.
You can copy & paste any by then clicking on Copy/Copy details as text in the lower right pane then right click in the reply box and select Paste.
-
I think the BSODs could be listed under Critical.