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

Been getting 1-10 BSODS a day. Seemingly impossible to fix unless I buy a new pc


  • Please log in to reply
21 replies to this topic

#1 PraiseMars

PraiseMars

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 19 November 2016 - 08:47 PM

Let me start off with my specs.

 

My specs are:

Mobo: MSI 970 GAMING 

CPU: AMD FX-8350

PSU: 500w EVGA 80+ Silver

GPU: EVGA GeForce GTX 960

RAM: 8gb 1600mhz DDR3

HDD: Western Digital 1TB 

 

This all began about 9 months ago when out of nowhere I started getting an immense amount of BSODS. I've been on a few different forums and none have been able to help me solve this issue so far. The BSODS are almost never the same. They consist of IRQL stuff, BAD_POOL_HEADER stuff, CRITICAL_PROCESS_DIED stuff, and countless others I've seen over the course of this. After awhile, I narrowed it down to memory corruption caused by the driver "amd_xata.sys". It was linked to my hard drive that at the time was 5 years old. I solved this completely by buying a brand new hard drive and I thought it fixed my problem. Sadly, it did not. Now, there is no specific cause for these BSODS.

 

I have been told to run "Driver Verifier" countless times. It does not work. Why? When verifier is launched and I restart my computer, my computer will instantly BSOD before I can load into windows. I have to run safe mode to turn it off and thus no .dmp file is saved.

 

I primarily use my computer for gaming. BSODS aren't the only errors that occur. I constantly deal with my games crashing at the very least 5 times per game per day. I get alot of errors from the games about something like "file missing KERNELBASE32" and slot of random stuff like "Memory could not be read 0x0000000012345" I also have recurring errors like my screen going black and flashing. This leads to my display divers being unable to start thus making me have to restart my pc. Sometimes, my game will crash and when I hit exit, it will induce an instant blue screen. Other times, Google Chrome will crash and refuse to open again until I restart my computer (this also happens with games too).

 

Extra info and stuff I've tried:

 

I've concluded that Windows is up to date, my Nvidia drivers are up to date, my bios is up to date, my audio drivers and ethernet drivers are up to date, and that there are no yellow triangles or question marks in device manager. Also, I have run memtest86 and my ram got 11 passes so it's good. My pc is not overheating either. I've ran DISM and SFC countless times, reinstalled windows, and wiped my hard drive multiple times as well.. nothing is working. I am currently running everything at stock speeds and just restating that memtest has passed before with 11 passes so my ram is not the problem. I have also disabled "nVidia Streaming Kernel service" and that stuff like others have told me to. Nothing came out of it. The BSODS will occur in any situation given. Whether I'm browsing the web, on the desktop with nothing open, or playing a video game. I have malwarebytes and scans conclude that I do not have any viruses.

 

I have attached a .dmp file from about 20 minutes prior to writing this. Not sure if it will work though, It keeps telling me I can't upload it because I don't have permission to upload that type of file or something. 

 

It's in my best interest to get this resolved so a quick reply would be great, thanks!



BC AdBot (Login to Remove)

 


#2 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 20 November 2016 - 02:22 AM

 

Let me start off with my specs.

 

My specs are:

Mobo: MSI 970 GAMING 

CPU: AMD FX-8350

PSU: 500w EVGA 80+ Silver

GPU: EVGA GeForce GTX 960

RAM: 8gb 1600mhz DDR3

HDD: Western Digital 1TB 

 

This all began about 9 months ago when out of nowhere I started getting an immense amount of BSODS. I've been on a few different forums and none have been able to help me solve this issue so far. The BSODS are almost never the same. They consist of IRQL stuff, BAD_POOL_HEADER stuff, CRITICAL_PROCESS_DIED stuff, and countless others I've seen over the course of this. After awhile, I narrowed it down to memory corruption caused by the driver "amd_xata.sys". It was linked to my hard drive that at the time was 5 years old. I solved this completely by buying a brand new hard drive and I thought it fixed my problem. Sadly, it did not. Now, there is no specific cause for these BSODS.

 

I have been told to run "Driver Verifier" countless times. It does not work. Why? When verifier is launched and I restart my computer, my computer will instantly BSOD before I can load into windows. I have to run safe mode to turn it off and thus no .dmp file is saved.

 

I primarily use my computer for gaming. BSODS aren't the only errors that occur. I constantly deal with my games crashing at the very least 5 times per game per day. I get alot of errors from the games about something like "file missing KERNELBASE32" and slot of random stuff like "Memory could not be read 0x0000000012345" I also have recurring errors like my screen going black and flashing. This leads to my display divers being unable to start thus making me have to restart my pc. Sometimes, my game will crash and when I hit exit, it will induce an instant blue screen. Other times, Google Chrome will crash and refuse to open again until I restart my computer (this also happens with games too).

 

Extra info and stuff I've tried:

 

I've concluded that Windows is up to date, my Nvidia drivers are up to date, my bios is up to date, my audio drivers and ethernet drivers are up to date, and that there are no yellow triangles or question marks in device manager. Also, I have run memtest86 and my ram got 11 passes so it's good. My pc is not overheating either. I've ran DISM and SFC countless times, reinstalled windows, and wiped my hard drive multiple times as well.. nothing is working. I am currently running everything at stock speeds and just restating that memtest has passed before with 11 passes so my ram is not the problem. I have also disabled "nVidia Streaming Kernel service" and that stuff like others have told me to. Nothing came out of it. The BSODS will occur in any situation given. Whether I'm browsing the web, on the desktop with nothing open, or playing a video game. I have malwarebytes and scans conclude that I do not have any viruses.

 

I have attached a .dmp file from about 20 minutes prior to writing this. Not sure if it will work though, It keeps telling me I can't upload it because I don't have permission to upload that type of file or something. 

 

It's in my best interest to get this resolved so a quick reply would be great, thanks!

 

Hi Praise,

You might want to try extract the dmp file from your windows folder to the desktop and try to upload again?

P.S Do you have any overclocking software?

Please advise.

Thanks.

 



#3 PraiseMars

PraiseMars
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 20 November 2016 - 11:27 AM

Thanks for the quick reply!

That's exactly what I had to done to the .dmp file. I took it out of my minidump folder and put it on my desktop. I then gave my self full access to the folder so it would allow me to upload it to the Internet. I'm not home right now but I'll try again when I get back.

I do have MSI Afterburner but I only used it once to see my gpu and cpu temperatures.

 

 

 

Update: I'm now home and I can't find the upload button that was previously here so I uploaded the .dmp to onedrive and it worked.

 

Here's the link: https://1drv.ms/u/s!AoZ9Od5vFyzhgdRh8o2aDVl7JWSr1g


Edited by PraiseMars, 20 November 2016 - 12:50 PM.


#4 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 20 November 2016 - 06:53 PM

Thanks for the quick reply!

That's exactly what I had to done to the .dmp file. I took it out of my minidump folder and put it on my desktop. I then gave my self full access to the folder so it would allow me to upload it to the Internet. I'm not home right now but I'll try again when I get back.

I do have MSI Afterburner but I only used it once to see my gpu and cpu temperatures.
 
 
 
Update: I'm now home and I can't find the upload button that was previously here so I uploaded the .dmp to onedrive and it worked.
 
Here's the link: https://1drv.ms/u/s!AoZ9Od5vFyzhgdRh8o2aDVl7JWSr1g


Hi,

Noted. I will analyse the dump when Im home. Currently at work now, sorry for the inconvenience.

Thanks.

#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:03:31 AM

Posted 21 November 2016 - 06:01 AM

Did you zip up the dump files before trying to upload them?  The system won't accept files with the .dmp extension - you have to zip them up.

 

Does Driver Verifier leave a BSOD that you can see?  If so, does it name a driver (a filename ending in .sys)?

 

From your description it seems that you've done most of the troubleshooting that I would suggest.

And, because of it, the most likely cause (IMO) is a hardware problem

I can suggest these free hardware diagnostics (but you've done most of them already):  http://www.carrona.org/hwdiag.html

Please try those that you haven't run already and let us know the results.

If it's a hardware problem and the diagnostics don't find anything - then I suggest this procedure to rule out the rest of the hardware:  http://www.carrona.org/strpdown.html

 

I wonder about the xhunter1.sys, as it's associated with BSOD's - usually when it detects a hacked game.

If that's the case, then remove the hacked game to fix it.

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Nov 19 20:03:23.482 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111916-13578-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 8:13:24.217
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
Probably caused by :volsnap.sys ( volsnap+5162 )
BugCheck D1, {80, 2, 0, fffff80ace3e5162}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80ace3e5162, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  BlackDesert64.exe
FAILURE_BUCKET_ID: AV_volsnap!unknown_function
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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:

**************************Sat Nov 19 20:03:23.482 2016 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
e22w10x64.sys               Fri Aug 28 17:05:38 2015 (55E0CD22)
bwcW10x64.sys               Fri Jan 22 17:08:51 2016 (56A2A873)
RTKVHD64.sys                Tue Jul 19 06:56:25 2016 (578E0759)
xhunter1.sys                Mon Aug 22 03:21:52 2016 (57BAA810)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvlddmkm.sys                Wed Nov 16 19:26:04 2016 (582CF91C)


http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
e22w10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=xhunter1.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
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 PraiseMars

PraiseMars
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 21 November 2016 - 03:37 PM

 

Did you zip up the dump files before trying to upload them?  The system won't accept files with the .dmp extension - you have to zip them up.

 

Does Driver Verifier leave a BSOD that you can see?  If so, does it name a driver (a filename ending in .sys)?

 

From your description it seems that you've done most of the troubleshooting that I would suggest.

And, because of it, the most likely cause (IMO) is a hardware problem

I can suggest these free hardware diagnostics (but you've done most of them already):  http://www.carrona.org/hwdiag.html

Please try those that you haven't run already and let us know the results.

If it's a hardware problem and the diagnostics don't find anything - then I suggest this procedure to rule out the rest of the hardware:  http://www.carrona.org/strpdown.html

 

I wonder about the xhunter1.sys, as it's associated with BSOD's - usually when it detects a hacked game.

If that's the case, then remove the hacked game to fix it.

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Nov 19 20:03:23.482 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\111916-13578-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 8:13:24.217
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
Probably caused by :volsnap.sys ( volsnap+5162 )
BugCheck D1, {80, 2, 0, fffff80ace3e5162}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80ace3e5162, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  BlackDesert64.exe
FAILURE_BUCKET_ID: AV_volsnap!unknown_function
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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:

**************************Sat Nov 19 20:03:23.482 2016 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
e22w10x64.sys               Fri Aug 28 17:05:38 2015 (55E0CD22)
bwcW10x64.sys               Fri Jan 22 17:08:51 2016 (56A2A873)
RTKVHD64.sys                Tue Jul 19 06:56:25 2016 (578E0759)
xhunter1.sys                Mon Aug 22 03:21:52 2016 (57BAA810)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvlddmkm.sys                Wed Nov 16 19:26:04 2016 (582CF91C)

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
e22w10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=xhunter1.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 

 

Sorry, I forgot to mention something. Before I bought my new hard drive, verifier would tell me "DRIVER_VERIFIER_DETECTED_VIOLATION (amd_xata.sys)" but now, I get the same error but with no driver shown. Basically, It doesn't tell me the driver that caused it.

 

I'm not exactly sure what you mean by "hacked game".. Is it a pirated game or a game that I've injected hacks into? Either way, this is ruled out because before I even downloaded any new games, I got a blue screen while I was downloading google chrome right when I got my new hard drive.

 

I attatched the SysnativeFileCollectionApp.zip file but when I ran prefmon, it said " collecting resources for 60 seconds". This took place for over an hour until my computer blue screened and it never completed.

 

 

 

 

Attached Files



#7 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 21 November 2016 - 06:42 PM

Hi

DRIVER_VERIFIER_DETECTED_VIOLATION. Is usually caused by faulty, corrupted or incompatible drivers, or a registry fault.

Did you done a memtest? You might wanna start to check from the RAM.

Thanks

#8 PraiseMars

PraiseMars
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 21 November 2016 - 06:46 PM

Hi

DRIVER_VERIFIER_DETECTED_VIOLATION. Is usually caused by faulty, corrupted or incompatible drivers, or a registry fault.

Did you done a memtest? You might wanna start to check from the RAM.

Thanks

 

Hi, I stated in my first post that I had successfully ran memtest86 for 11 passes so I don't think that my ram is the problem.



#9 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:03:31 AM

Posted 22 November 2016 - 09:11 AM

MemTest86/86+ are very good programs and detect MOST problems with RAM.

At work we occasionally find RAM that passes MemTest, but fails Prime95's Blend test - so I suggest running both when testing your RAM

 

A Driver Verifier detected violation is a problem that occurs when Driver Verifier is stressing a driver(s).

This is not necessarily a problem with the driver in real life (developers use it to stress test their drivers before releasing them).
We usually suggest running Driver Verifier after seeing reports that can blame 3rd party drivers - but we can't tell which driver it is.


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.

#10 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 22 November 2016 - 09:17 AM

MemTest86/86+ are very good programs and detect MOST problems with RAM.

At work we occasionally find RAM that passes MemTest, but fails Prime95's Blend test - so I suggest running both when testing your RAM

 

A Driver Verifier detected violation is a problem that occurs when Driver Verifier is stressing a driver(s).

This is not necessarily a problem with the driver in real life (developers use it to stress test their drivers before releasing them).
We usually suggest running Driver Verifier after seeing reports that can blame 3rd party drivers - but we can't tell which driver it is.

He have stated he had done the RAM test. Hang on. Im diagnosing the BSOD report.
 

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\JinXiang\Downloads\PraiseMars\112116-11593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
WARNING: Whitespace at end of path element
Error: Empty Path.
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 8 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff802`6e87c000 PsLoadedModuleList = 0xfffff802`6eb81060
Debug session time: Mon Nov 21 21:41:48.415 2016 (UTC + 8:00)
System Uptime: 0 days 7:36:36.150
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
 
************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified
 
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 10E, {2a, ffffc10d7418d000, ffffc10d750a8ee0, 80}

Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+251e8 )
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002a, The subtype of the bugcheck:
Arg2: ffffc10d7418d000
Arg3: ffffc10d750a8ee0
Arg4: 0000000000000080
 
Debugging Details:
 
ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
 
MODULE_NAME: dxgmms2
 
FAULTING_MODULE: fffff8026e87c000 nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5801a824
 
BUGCHECK_STR:  0x10e_2a
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff80449d734ae to fffff8026e9c6510
 
STACK_TEXT:  
ffffac01`f23066a8 fffff804`49d734ae : 00000000`0000010e 00000000`0000002a ffffc10d`7418d000 ffffc10d`750a8ee0 : nt+0x14a510
ffffac01`f23066b0 fffff804`4d6aebe8 : 00000000`00000080 ffffc10d`750a8ee0 ffffac01`f0f7acc0 fffff802`6e87c000 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffac01`f23066f0 fffff804`4d69d3f5 : ffffc10d`7418d000 00000000`00000001 ffffc10d`74196bd8 ffffc10d`750a8ee0 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x251e8
ffffac01`f2306960 fffff802`6e87e729 : ffffac01`f0f6e180 ffffc10d`7410e800 fffff804`4d69c540 ffff850d`4dcb4380 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xea5
ffffac01`f2306c10 ffffac01`f0f6e180 : ffffc10d`7410e800 fffff804`4d69c540 ffff850d`4dcb4380 ffffac01`f0f7acc0 : nt+0x2729
ffffac01`f2306c18 ffffc10d`7410e800 : fffff804`4d69c540 ffff850d`4dcb4380 ffffac01`f0f7acc0 00000000`00000281 : 0xffffac01`f0f6e180
ffffac01`f2306c20 fffff804`4d69c540 : ffff850d`4dcb4380 ffffac01`f0f7acc0 00000000`00000281 00000000`00000000 : 0xffffc10d`7410e800
ffffac01`f2306c28 ffff850d`4dcb4380 : ffffac01`f0f7acc0 00000000`00000281 00000000`00000000 00000000`00000001 : dxgmms2!VidMmWorkerThreadProc
ffffac01`f2306c30 ffffac01`f0f7acc0 : 00000000`00000281 00000000`00000000 00000000`00000001 ffffac01`f0f7acc0 : 0xffff850d`4dcb4380
ffffac01`f2306c38 00000000`00000281 : 00000000`00000000 00000000`00000001 ffffac01`f0f7acc0 fffff802`6e9cb9d6 : 0xffffac01`f0f7acc0
ffffac01`f2306c40 00000000`00000000 : 00000000`00000001 ffffac01`f0f7acc0 fffff802`6e9cb9d6 ffffac01`f0f6e180 : 0x281
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+251e8
fffff804`4d6aebe8 83cbff          or      ebx,0FFFFFFFFh
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+251e8
 
FOLLOWUP_NAME:  MachineOwner
 
IMAGE_NAME:  dxgmms2.sys
 
IMAGE_VERSION:  10.0.14393.351
 
BUCKET_ID:  WRONG_SYMBOLS
 
FAILURE_BUCKET_ID:  WRONG_SYMBOLS
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:wrong_symbols
 
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
 
Followup: MachineOwner
---------
 

Edited by JinXiang91, 22 November 2016 - 09:26 AM.


#11 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:03:31 AM

Posted 22 November 2016 - 09:39 AM

I have some vision problems, so occasionally I miss things.

I also have seen issues with MemTest not finding all problems - so I suggested Prime95's Blend test.

 

If you noticed, there are 41 memory dumps in the uploaded report.  My system is still chugging away trying to analyze all of them.
Analyzing only one may/may not give valid results (depending on the type of error).

In this case a Video Memory Manager error can mean either hardware or software problems.
Let's see what a full analysis reveals once my system finishes the memory dumps..............


Edited by usasma, 22 November 2016 - 09:41 AM.

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.

#12 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:03:31 AM

Posted 22 November 2016 - 10:10 AM

And, here's my analysis:

 

Your UEFI/BIOS (version V22.4) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
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 that 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.

MSI Afterburner(along with EVGA Precision and Riva Tuner) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

Out of 41 memory dumps there were 14 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):  One of them actually blames hardware for the BSOD.
- 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 run ALL of the tests and let us know the results.  We'll move on from there.

 

Finally, the presence of the xhunter1.sys driver makes me wonder about hacking/pirated software.
Read more here:  http://www.carrona.org/drivers/driver.php?id=xhunter1.sys

Hacked/pirated software doesn't behave like normal software (due to the hacks that make it work), so it may not be fixable here (and we do not work on hacked/pirated software - it's against the forums rules)

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Nov 21 08:41:48.415 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112116-11593-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 7:36:36.150
Probably caused by :dxgmms2.sys ( dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+251e8 )
BugCheck 10E, {2a, ffffc10d7418d000, ffffc10d750a8ee0, 80}
BugCheck Info: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
Arguments:
Arg1: 000000000000002a, The subtype of the bugcheck:
Arg2: ffffc10d7418d000
Arg3: ffffc10d750a8ee0
Arg4: 0000000000000080
BUGCHECK_STR:  0x10e_2a
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x10e_2a_dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 20 21:13:42.672 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112016-12578-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 3:03:16.407
Probably caused by :ntkrnlmp.exe ( nt!PspCatchCriticalBreak+d6 )
BugCheck EF, {ffffd6824f1ef800, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffd6824f1ef800, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_4f254800_KERNELBASE.dll!unknown_nt!PspCatchCriticalBreak
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 20 13:09:07.909 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112016-12187-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 1:31:18.644
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 1A, {41793, ffff98bfff416f68, 118, 117}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: ffff98bfff416f68
Arg3: 0000000000000118
Arg4: 0000000000000117
BUGCHECK_STR:  0x1a_41793
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 20 11:37:04.408 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112016-13156-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 13:03:06.143
*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 50, {ffffacd640000000, 0, 0, 6}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: ffffacd640000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000006, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
  BIOS Version                  V22.4
  BIOS Release Date             12/21/2015
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Mon Nov 21 08:41:48.415 2016 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
e22w10x64.sys               Fri Aug 28 17:05:38 2015 (55E0CD22)
bwcW10x64.sys               Fri Jan 22 17:08:51 2016 (56A2A873)
RTKVHD64.sys                Tue Jul 19 06:56:25 2016 (578E0759)
xhunter1.sys                Mon Aug 22 03:21:52 2016 (57BAA810)
nvvad64v.sys                Thu Sep 22 12:46:30 2016 (57E40AE6)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
nvlddmkm.sys                Wed Nov 16 19:26:04 2016 (582CF91C)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov 18 12:04:39.547 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Thu Nov 10 17:01:49 2016 (5824EE4D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Nov 16 17:04:51.287 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Tue Oct 25 15:38:31 2016 (580FB4B7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 28 19:40:42.168 2016 (UTC - 5:00)**************************
nvvad64v.sys                Fri Jul  1 09:12:29 2016 (57766C3D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct 27 18:12:11.229 2016 (UTC - 5:00)**************************
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys                Sat Oct  1 15:08:52 2016 (57F009C4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  6 21:11:44.548 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Fri Sep 16 18:21:27 2016 (57DC7067)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 26 18:50:21.371 2016 (UTC - 5:00)**************************
netr28x.sys                 Fri Jun 13 07:50:31 2014 (539AE587)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)
xhunter1.sys                Tue Jun 28 22:39:15 2016 (577334D3)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 17 15:35:45.470 2016 (UTC - 5:00)**************************
nvlddmkm.sys                Thu Aug 25 16:31:18 2016 (57BF5596)


http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
e22w10x64.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=bwcW10x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=xhunter1.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=netr28x.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=xhunter1.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys


 
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.

#13 PraiseMars

PraiseMars
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 22 November 2016 - 03:29 PM

Hello, I checked my motherboard manufacturer's website. Everything is currently up to date.

 

I looked up the latest updates for windows 10 and I am up to date.

 

MSI Afterburner has been uninstalled along with any pirated software on my computer.

 

Currently, I am not overclocking anything.

 

I noticed that my RAM is running in dual channel mode even though I only have one stick shown here: https://gyazo.com/cdaecae3a6183a30dc6fc39470c8d200

 

Could this be affecting anything? If so, how do I fix it?

 

Sorry for not noticing you recommended a different test, some idiots on a different forum kept telling me the same stuff over and over again so I just assumed. Just in case I get a bsod while using prime95, I'm posting this reply now and will edit it when I'm done.

 

Thanks for all of the help so far.

 

Edit: Prime95 has finished. I ran 8 tests; 1 for each cpu and did I chose the blend test. I'm not sure if there are any uploadable results or anything of the sort but everything went fine


Edited by PraiseMars, 22 November 2016 - 04:31 PM.


#14 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:03:31 AM

Posted 23 November 2016 - 08:03 AM

I'm not real certain about RAM settings - most of my work relies upon using default settings, so I don't get much experience with the settings.
Post over in the Internal Hardware forums for an expert opinion:    http://www.bleepingcomputer.com/forums/f/7/internal-hardware/ 

 

Most helpers on the forums use similar tests, but some of us have different viewpoints on them.

Do you have a link to the other forum post so we can have a look at it?

 

How long did you run Prime95 for?  In most cases, if it errors out, you'll either see errors in the Prime95 window, or there will be problems with the system.

If you had none of them (as long as you ran it for a decent amount of time), then it's OK.
There is a results.txt file saved in the Prime95 folder if you'd care to have a look at it.

FYI - a "decent amount of time" is that time needed to stress the system adequately - and it's different for every system, so I generally suggest 24 hours (but at work I only leave it for a couple of hours).


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.

#15 PraiseMars

PraiseMars
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  

Posted 23 November 2016 - 08:17 AM

Oh, well, I let it run for awhile and it randomly stopped and I did not see any errors so I assumed it was done.

I'm not home right now but, I will be in a few hours. I'll be able to tell you the forum link and check the results.txt file when I get back.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users