Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Frequent BSOD's


  • Please log in to reply
5 replies to this topic

#1 peter_de_bruijn

peter_de_bruijn

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:10:32 AM

Posted 14 July 2017 - 05:22 PM

Hi,
 
Sincs a couple of days I get frequest BSOD's. I have detached any device in and out of my computer, removed my vido card, disabled my sound card in Bios. Nothing helps. Can you please help me find the bad bits?
 
I have a Windows 10 64 bit OS (MSDN).
Intel I7-4790K processor
16Gb RAM
Asus Z97-A MB
2 Samsung Evo 850 pro SSD's running on RAID 0
Reinstalled windows 5 months ago (clean install)
Most hardware is under two years old
I have a cooler master G550M power supply
 
The dump files were to big to upload, so i posted them here:
 
Thanks in advance! This thing is killing me...
 
Peter

Edited by peter_de_bruijn, 14 July 2017 - 05:23 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:32 AM

Posted 14 July 2017 - 06:35 PM

Your UEFI/BIOS (version 2801) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and the outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Are you sure about your PSU?f  How old is it?
Have you tried disconnecting the extra hard drives and any non-essential hardware to see if that improves things?
FYI - this free program has a PSU test (I'm uncertain of how it works/how well it works, but it's better than nothing):  http://www.ocbase.com/

 

In the WER section of the MSINFO32 report, at least 4 of the BSOD's blame bad hardware specifically.  The rest seem to establish a pattern of "randomness" that's typical of hardware/compatibility/low-level driver issues.  I'll be more specific when the 50 memory dumps finish running through the debugger..........

Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please finish ALL of the tests and let us know the results - and we'll move on from there.

 

Please turn Driver Verifier off.
To do this, open up verifier.exe and select "Delete exisiting settings"
Then click on "Finish" and reboot for the changes to take effect.

 

Out of 50 memory dumps there were 12 different BSOD  (aka STOP or BugCheck) error codes.  The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- dirt/dust/hair/fur/crud inside the case.  Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

Please get a head start on the hardware diagnostics - they are located here:  http://www.carrona.org/hwdiag.html
Please finish ALL of them and let us know the results.

Quite a few of the memory dumps have traces of gzflt.sys in the stack trace.
This driver belongs to your BitDefender program.

I would strongly suggest:
- uninstalling the current copy of BitDefender

- then run this free uninstall tool to remove any leftover traces:  https://www.bitdefender.com/uninstall/

- ensure that Windows Defender is activated/updated/and working - then test to see if the system still BSOD's

Feel free to reinstall the latest, W10 compatible version of BitDefender AFTER we are finished troubleshooting.

 

Additionally, uninstall MalwareBytes, then download/install the latest version from the MalwareBytes website.
Older versions have issues with older versions of BitDefender.

 

Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers.  
If unable to find an update, please uninstall the program that is responsible for that driver.  

DO NOT manually delete/rename the driver as it may make the system unbootable!!!:

aabed2.sys                   Thu Mar 20 06:34:12 2008 (47E23DA4)
This is most likely the driver for a bank card reader by Todos Data System AB   This is a very old driver is is very likely one of the reasons that there are BSOD's on this system (although it may not be the only reason).
aabed2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
lvpopf64.sys                 Wed Oct  7 04:27:20 2009 (4ACC50E8)
Logitech POP Suppression Filter http://www.logitech.com/en-us/support-downloads
http://www.carrona.org/drivers/driver.php?id=lvpopf64.sys
 
lvrs64.sys                   Wed Oct  7 04:27:59 2009 (4ACC510F)
Logitech Camera driver http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
 
lvuvc64.sys                  Wed Oct  7 04:28:44 2009 (4ACC513C)
Logitech USB Video Class Driver (WebCam) http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
 
AsUpIO.sys                   Mon Aug  2 22:47:59 2010 (4C57835F)
ASUS hardware monitoring software related http://support.asus.com/download/download.aspx?SLanguage=en-us
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
 
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)
Asus PCProbe Utility http://support.asus.com/download/download.aspx
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
 
iaStorAV.sys                 Thu Feb 19 07:08:39 2015 (54E5D247)
Intel Rapid Storage Technology SATA RAID Controller driver https://downloadcenter.intel.com/default.aspx
http://www.carrona.org/drivers/driver.php?id=iaStorAV.sys
 
iqvw64e.sys                  Wed Apr 22 07:46:58 2015 (55378A32)
Intel Corporation [br]Network Adapter Diagnostic Driver  http://downloadcenter.intel.com/
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys

I will post the memory dump analysis in the next post (50 of them won't usually fit in one post)................


Edited by usasma, 14 July 2017 - 06:38 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:32 AM

Posted 14 July 2017 - 06:36 PM

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Fri Jul 14 16:34:13.161 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071417-6921-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:13:39.817
*** WARNING: Unable to verify timestamp for gzflt.sys
*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
Probably caused by :memory_corruption
BugCheck C1, {ffff9084aa39efc0, ffff9084aa39e611, f5c040, 32}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Arguments:
Arg1: ffff9084aa39efc0, address trying to free
Arg2: ffff9084aa39e611, address where one bit is corrupted
Arg3: 0000000000f5c040, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  vsserv.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 16:19:20.075 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071417-6328-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:06:05.733
Probably caused by :dxgmms2.sys ( dxgmms2!VidSchRegisterAsDwm+3ca5 )
BugCheck 139, {3, ffffdd01dc83e530, ffffdd01dc83e488, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffdd01dc83e530, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffdd01dc83e488, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x139_VRF_3_dxgmms2!VidSchRegisterAsDwm
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 3998
  BIOS Version                  2801
  BIOS Release Date             11/11/2015
  Manufacturer                  ASUS
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  All Series
  Baseboard Product             Z97-A
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 16:11:33.425 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071417-16265-01.dmp]
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:0 days 0:20:41.082
*** WARNING: Unable to verify timestamp for gzflt.sys
*** ERROR: Module load completed but symbols could not be loaded for gzflt.sys
Probably caused by :memory_corruption
BugCheck C1, {fffff408b4b98fb0, fffff408b4b98409, 454050, 23}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Arguments:
Arg1: fffff408b4b98fb0, address trying to free
Arg2: fffff408b4b98409, address where bits are corrupted
Arg3: 0000000000454050, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
BUGCHECK_STR:  0xC1_23
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Fri Jul 14 16:34:13.161 2017 (UTC - 4:00)**************************
AsUpIO.sys                   Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)
iaStorAV.sys                 Thu Feb 19 07:08:39 2015 (54E5D247)
dc3d.sys                     Fri Nov  6 14:14:22 2015 (563CFC0E)
e1i63x64.sys                 Fri Mar  4 16:46:29 2016 (56DA0235)
TeeDriverW8x64.sys           Mon Mar 28 14:59:41 2016 (56F97F1D)
mbae64.sys                   Fri Apr 29 06:10:09 2016 (57233301)
IntcDAud.sys                 Tue May 10 04:08:56 2016 (57319718)
trufos.sys                   Wed Jun 15 05:43:22 2016 (5761233A)
bdfwfpf.sys                  Wed Jun 15 07:17:44 2016 (57613958)
WirelessKeyboardFilter.sys   Sat Jun 25 03:13:14 2016 (576E2F0A)
gzflt.sys                    Fri Oct 28 05:28:18 2016 (58131A32)
IOMap64.sys                  Fri Jan  6 03:58:05 2017 (586F5C1D)
igdkmd64.sys                 Wed Mar  8 13:38:22 2017 (58C04F9E)
avc3.sys                     Tue Apr 18 05:02:07 2017 (58F5D60F)
avckf.sys                    Tue Apr 18 05:10:51 2017 (58F5D81B)
MBAMSwissArmy.sys            Fri Jun  2 16:46:01 2017 (5931CE89)
mbam.sys                     Wed Jun  7 10:26:58 2017 (59380D32)
farflt.sys                   Wed Jun 14 09:21:34 2017 (5941385E)
mwac.sys                     Tue Jun 20 13:53:19 2017 (5949610F)
MBAMChameleon.sys            Tue Jun 27 14:22:06 2017 (5952A24E)
SleepStudyHelper.sys         ***** Invalid 2036 Invalid 2036 Invalid
intelppm.sys                 ***** Invalid 2007 Invalid 2007 Invalid
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 12:17:08.395 2017 (UTC - 4:00)**************************
iqvw64e.sys                  Wed Apr 22 07:46:58 2015 (55378A32)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 09:02:19.329 2017 (UTC - 4:00)**************************
nvlddmkm.sys                 Wed Jun  7 19:03:57 2017 (5938865D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 07:54:02.097 2017 (UTC - 4:00)**************************
RTKVHD64.sys                 Tue Jun 14 06:51:52 2016 (575FE1C8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 07:47:26.510 2017 (UTC - 4:00)**************************
lvuvc64.sys                  Wed Oct  7 04:28:44 2009 (4ACC513C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 07:27:43.547 2017 (UTC - 4:00)**************************
lvpopf64.sys                 Wed Oct  7 04:27:20 2009 (4ACC50E8)
lvrs64.sys                   Wed Oct  7 04:27:59 2009 (4ACC510F)
point64.sys                  Fri Feb 10 03:14:51 2017 (589D767B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 06:35:08.806 2017 (UTC - 4:00)**************************
nvhda64v.sys                 Wed Mar 15 08:48:41 2017 (58C93829)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 14 06:10:02.537 2017 (UTC - 4:00)**************************
aabed2.sys                   Thu Mar 20 06:34:12 2008 (47E23DA4)


http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=iaStorAV.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=trufos.sys
http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys
WirelessKeyboardFilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=gzflt.sys
http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=avc3.sys
http://www.carrona.org/drivers/driver.php?id=avckf.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=farflt.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
SleepStudyHelper.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=lvpopf64.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=point64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
aabed2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 peter_de_bruijn

peter_de_bruijn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:10:32 AM

Posted 15 July 2017 - 03:23 PM

I have been running the memtest86 you explanation mentioned and there were red flags all over. Seems that I have corrupt memory...

However, when I tried to distinguish what bank was corrupt every test with every combination of two dimms passed successfully.

I'll try putting them in other banks, maybe the mobo itself is broken.
I will keep you posted.



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:32 AM

Posted 16 July 2017 - 08:35 AM

There's a couple of possibilities:

- the connection between the RAM (sticks/DIMMs) and the banks (the slots) have some crud in them and it made a bad connection.  Reseating them could have scraped enough crud off that the connection was improved.

- if all pass individually in one bank (or pair of banks) - then it's likely that all of the sticks are good and that one bank (or pair of banks) is good - which leads us to wonder if any of the other banks are bad.

To test this, run one of the good sticks in each bank (or pair of banks).  If the slot is bad, the errors should start showing up fairly quickly (as quickly as it did on the first test).


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 peter_de_bruijn

peter_de_bruijn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:10:32 AM

Posted 16 July 2017 - 01:29 PM

I ran a memory test today with all four dimms in place. No errors, even after 4 hours of testing.

It seems that your first option was the case. I still have odd problems with my computer, seems disc related, but no more BSOD's since.

THANKS! THANKS! THANKS!!!

I'll run some more diagnostics on my discs.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users