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

Notebook Keeps Crashing, BSOD, MiniDump


  • Please log in to reply
16 replies to this topic

#1 george144

george144

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 07:15 AM

Hi Group, I hope you can help me.  I have a Samsung Notebook 9, WIN10, 250g SSD, 8g mem.

 

This thing crashes 5 times a day.  I have deleted all superfluous programs, and have reloaded WIN10 from scratch, 3 times.  After each reload, I add Samsung updates to make sure all the drivers are updated.  This was recommended by INTEL because of potential changes Samsung made to their 520 display driver.  Device Manager shows no device driver problems.  

 

I now let it run with CNN/videos running continuously.  Sometimes it runs 5 minutes, other times 5 hours, but it always crashes with BSOD.  

 

I feel my only prayer is to get a dump that might lead to the culprit. I CAN"T GET THE DAMN COMPUTER TO CREATE A MINIDUMP.  I have researched the topic and found several referendes to MS procedure.  (sysdm.cpl, RECOVERY, ADVANCED, turn off auto start, create 256k minidump, etc. )  I have also enlarged the page size to 9500 as suggested, as it is supposed to be larger than RAM, which is 8 GB.  There IS a Minidump folder in the c:Windows folder but it remains empty.

 

I would appreciate any and all thoughts on how to pursue the crashes, and/or the creation on dumps.

 

Thank you.



BC AdBot (Login to Remove)

 


#2 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 08:45 AM

Hi Group, I hope you can help me.  I have a Samsung Notebook 9, WIN10, 250g SSD, 8g mem.

 

This thing crashes 5 times a day.  I have deleted all superfluous programs, and have reloaded WIN10 from scratch, 3 times.  After each reload, I add Samsung updates to make sure all the drivers are updated.  This was recommended by INTEL because of potential changes Samsung made to their 520 display driver.  Device Manager shows no device driver problems.  

 

I now let it run with CNN/videos running continuously.  Sometimes it runs 5 minutes, other times 5 hours, but it always crashes with BSOD.  

 

I feel my only prayer is to get a dump that might lead to the culprit. I CAN"T GET THE DAMN COMPUTER TO CREATE A MINIDUMP.  I have researched the topic and found several referendes to MS procedure.  (sysdm.cpl, RECOVERY, ADVANCED, turn off auto start, create 256k minidump, etc. )  I have also enlarged the page size to 9500 as suggested, as it is supposed to be larger than RAM, which is 8 GB.  There IS a Minidump folder in the c:Windows folder but it remains empty.

 

I would appreciate any and all thoughts on how to pursue the crashes, and/or the creation on dumps.

 

Thank you.

 

EDIT  I noticed the pinned topic about about not getting Kernel Dump Files and have following its suggestions.

 

EDIT  SysNative output attached.    Attached File  SysnativeFileCollectionApp.zip   497.48KB   1 downloads

 

EDIT  Speccy output ....    http://speccy.piriform.com/results/hWVx7OKplV6E40tvz0wI2PX


Edited by george144, 27 January 2018 - 09:33 AM.


#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 09:27 AM

Do you have a MEMORY.dmp file in the C:\Windows directory?

 

Did you have problems after installing Windows - but before installing the Samsung drivers?

 

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/
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, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 


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 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 09:40 AM

Thanks for reply.

 

NO, there is no Memory.dmp folder, nor is there a Memory.dmp file.   There IS a MiniDump.dmp folder.  (but it is empty)

 

There were no apparent Windows load problems.

 

I believe the other programs you suggested have been run and their output is attached to my original post.  This that ok?

 

Is there anything else I can do?

 

 

Thank you.


Edited by george144, 27 January 2018 - 09:58 AM.


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 10:14 AM

Please contact a moderator/admin and ask them to merge your topics into 1.

This one here:  https://www.bleepingcomputer.com/forums/t/669270/notebook-keeps-crashing-bsod-minidump/#entry4432283

And this one here:  https://www.bleepingcomputer.com/forums/t/669263/win10-notebook-crashes/#entry4432233

It's twice the work to analyze these reports in 2 separate topics - and I don't have much time free.

I haven't checked what I wrote in the other topic - so this stuff is suggested without regard to that.

 

You can run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
Please run ALL of the tests and let us know the results.
FYI - These are the tests and what we usually see for the reports:

1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
  - A - simtek.org memtest
  - B - Video memory stress test
  - C - Artifact Locator
  - D - OCCT - 4 built in tests for CPU, GPU, PSU
  - E - Video Memory Stress Test
7 - CPU tests:  run at least one test on your CPU and let us know the result.


A quick look at the MSINFO32 report shows some BSOD's with no definite cause.
As such, you may also want to try:

1)  A clean boot (to see if it crashes when the clean boot is running): 

Perform a Clean Boot:  http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

If that stops the problem, then re-enable things a few at a time until you figure out what's causing it.
Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there).

 

2) running Driver Verifier to see if that can force the system to create a memory dump:  http://www.carrona.org/verifier.html

 

The Sysnative report here shows a memory dump (mindump) that was generated today (27 Jan).

The analysis follows:

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan 27 09:15:23.965 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012718-45765-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
System Uptime:0 days 2:23:45.688
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  ACOrigins.exe
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  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 Jan 27 09:15:23.965 2018 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
xusb22.sys                  Tue Mar 18 04:18:41 2014 (53280161)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
Phosgene.sys                Wed Sep  2 03:28:10 2015 (55E6A50A)
e2xw8x64.sys                Tue Jan 26 18:57:45 2016 (56A807F9)
RTCore64.sys                Fri Sep 30 08:03:17 2016 (57EE5485)
rzendpt.sys                 Wed Oct 26 04:12:17 2016 (58106561)
rzudd.sys                   Wed Oct 26 04:12:19 2016 (58106563)
RTKVHD64.sys                Wed Jun 14 01:58:31 2017 (5940D087)
rzpnk.sys                   Sun Jul 16 15:12:07 2017 (596BBA87)
rzpmgrk.sys                 Tue Jul 18 17:15:21 2017 (596E7A69)
avgbuniva.sys               Mon Dec  4 10:04:10 2017 (5A2563EA)
avgbdiska.sys               Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbidsdrivera.sys          Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbidsha.sys               Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbloga.sys                Mon Dec  4 10:04:14 2017 (5A2563EE)
nvvad64v.sys                Thu Dec 14 00:40:29 2017 (5A320ECD)
nvhda64v.sys                Fri Dec 15 03:17:43 2017 (5A338527)
avgRvrt.sys                 Tue Dec 19 13:09:14 2017 (5A3955CA)
avgArPot.sys                Tue Dec 19 13:09:16 2017 (5A3955CC)
avgSnx.sys                  Tue Dec 19 13:09:41 2017 (5A3955E5)
avgRdr2.sys                 Tue Dec 19 13:09:50 2017 (5A3955EE)
avgVmm.sys                  Tue Dec 19 13:21:43 2017 (5A3958B7)
avgStm.sys                  Tue Dec 19 13:30:47 2017 (5A395AD7)
nvlddmkm.sys                Wed Jan  3 18:39:48 2018 (5A4D69C4)
nvvadarm.sys                Wed Jan  3 18:56:49 2018 (5A4D6DC1)
avgMonFlt.sys               Tue Jan  9 15:21:28 2018 (5A552448)
avgSP.sys                   Tue Jan  9 15:21:48 2018 (5A55245C)


http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
Phosgene.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.
e2xw8x64.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=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
avgbuniva.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.
avgbdiska.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.
avgbidsdrivera.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.
avgbidsha.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.
avgbloga.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=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
avgRvrt.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.
avgArPot.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.
avgSnx.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.
avgRdr2.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.
avgVmm.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.
avgStm.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=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
avgMonFlt.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.
avgSP.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.

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 10:15 AM

I do recall making suggestions about the video in the other topic - so I suggest following those suggestions also (as the memory dump blames video).


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.

#7 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,460 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:02:14 PM

Posted 27 January 2018 - 10:26 AM

A BSOD will have a ***STOP: error code.  This stop error will look similar to the image below.

 

Click/tap on the image to enlarge it.

 

Attached File  bsod.PNG   184.67KB   0 downloads

 

Please post the error code in your topic.

 

 

Please download and install Speccy to provide us with information about your computer.  Clicking on this link will automatically initiate the download.

When Speccy opens you will see a screen similar to the one below.

 LUDoziL.png

Click on File which is outlined in red in the screen above, and then click on Publish Snapshot.

 speccy2.png

The following screen will appear, click on Yes.

 speccy3.png

The following screen will appear, click on Copy to Clipboard.

In your next post right click inside the Reply to Topic box, then click on Paste.  This will load a link to the Speccy log.

 

 

Please run System File Checker.

The sfc /scannow command scans all protected system files and replaces corrupted and incorrect versions with correct Microsoft versions.

Important:  There will be a short message at the end of the scan informing you of the results.  If you receive the message "no integrity violations were found" you don't need to do anything else, no corrupt files were found.  You should watch the scan to see the results at the end of the scan.

This needs to be run using an Administrator account.  

Click/tap on the Taskbar Search icon (magnifing glass) and type cdm.

PLrbrFc.png

You will see Command Prompt under Best match, right click on Command Prompt and select Run as administrator.

Copy and paste the command below in the Command Prompt, then press Enter.

sfc /scannow

This scan will take a while to run, please do not abort the scan as this can result in damage to the operating system.

If integrity issues are found in the scan please post the CBS log using the instructions below.

To find sfc /scannow log open the Command Prompt, copy and paste the command below, then press Enter.

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

This will place the log on your desktop.  Copy and paste the log at the host website I've suggested below.

This log usually is very large, for this reason you should use a host website like Dropbox to post the log.  You can start a free 30 day trial.  Once you have loaded the log at Dropbox post a link to the website.

 


Edited by dc3, 27 January 2018 - 10:27 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#8 quietman7

quietman7

    Bleepin' Janitor


  • Global Moderator
  • 51,388 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 10:49 AM

Please contact a moderator/admin and ask them to merge your topics into 1.
This one here:  https://www.bleepingcomputer.com/forums/t/669270/notebook-keeps-crashing-bsod-minidump/#entry4432283
And this one here:  https://www.bleepingcomputer.com/forums/t/669263/win10-notebook-crashes/#entry4432233

The topics have been merged.
.
.
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif

#9 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 12:28 PM

I am now on a different computer, for reasons I will explain below.

 

Well, in going through the list of things to do for analysis: I have run memTEST86 for 24 hours, repeatedly.  Not only did it not show any errors, the system did not crash once while testing.  (Leads me to think it is a software problem ??_   I have run malwarebytes, just now again, and nothing shows.  I ran GSmart, passed.  I was going the Driver Verify, and when I rebooted, it IMMEDIATELY crashed, BSOD, with the stop code "DRIVER VERIFICATION DETECTED VIOLATION".  It wouldn't reboot; kept crashing with the same error code.  Here's where I probably goofed.  Win10 offered to 'fix it', and without thinking I said sure, and it immediately restore the machine to a prior point, probably after a clean install of WIN10.

 

So I assume this means all the data from any dumps that were collected were just erased!  So I am currently reloading Samsung Updates it to the point where we started this morning.  I will then wait for it to crash again, and then upload SysNative, etc.

 

Or should I just go to the Driver Verify portion of the testing, and do that again.  If so, assuming it crashes with the same Driver Verification Violation, how do I get it to boot again, without restoring and losing all the crash data ?????

 

Additional information:  Twice earlier this morning before coming here and initially posting my problem, there were 2 BSOD; 2 had stop codes of Critical Process Dies 0%, and the other 2 were Unexpected Store Exception 0%.

 

Your suggestions please, and THANK YOU !!

 

JOHN:  earlier you mentioned there was a Minidump file that you looked it.  Where was it?


Edited by george144, 27 January 2018 - 12:45 PM.


#10 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 12:43 PM

http://speccy.piriform.com/results/URpMbpcL2LVugDV63znXkEU

 



#11 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 01:27 PM

The Driver Verifier link shows different ways to recover from this.  The easiest is to disable Driver Verifier in Safe Mode.

http://www.carrona.org/verifier.html

Post the Sysnative stuff now - if we need more, we'll ask for you to run it.

 

The previous Sysnative report upload contained the minidump - it collects them automatically.

I also found records of at least 2 BSOD's in the WER section of the MSINFO32 report.

 

Most often we see this sort of thing with a hardware problem - so please be sure to run the hardware diagnostics:

 

Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
Please run ALL of the tests and let us know the results.
FYI - These are the tests and what we usually see for the reports:

 

1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
  - A - simtek.org memtest
  - B - Video memory stress test
  - C - Artifact Locator
  - D - OCCT - 4 built in tests for CPU, GPU, PSU
  - E - Video Memory Stress Test
7 - CPU tests:  run at least one test on your CPU and let us know the result.

 

Edited by usasma, 27 January 2018 - 01:31 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.

#12 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 01:41 PM

Attached File  SysnativeFileCollectionApp.zip   858.06KB   1 downloads

 

Speccy is just above.

 

I have already run diag on memory and Gsmart of the SSD.

 

I will continue with the hardware diagnostics.   Please advise if you want the Driver Verification run again.  

Furmark ran 20 minutes, maxed at 75C, stabilied about 62-64C.

Running Prime95.  "passed self-test 400k"?  What is BLEND test?

VMT Virtual Memory Test  0 errors found

INTEL CPU Test + Temp Moniter   up to 90C, no problems noted.  All section PASS.

 

Thank you.Driver Verification test again.  It wreaked havoc before.


Edited by george144, 27 January 2018 - 02:58 PM.


#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 27 January 2018 - 03:39 PM

Continue with the diagnostics.  IMO this is most likely a hardware problem.

No need for verifier again - we got a Driver Verifier enabled memory dump in the uploaded reports.

 

Blend test is a combination of tests.  If you read the documentation, it's heavily slanted to stressing RAM - so it's a great, alternate test for RAM (and sometimes finds RAM problems when MemTest can't)

 

CPU got to 90ºC?  That's a bit hot.  Please check the cooling solution for your CPU.

- Hot air not being pushed towards the cooler from other devices

- Cooler fan working and blowing air INTO the cooler

- cooler is free of dust/dirt/hairballs/etc

- cooler is firmly attached to CPU

- thermal paste is adequate (not too much, not too little - just enough to make it just right).

 

Temporarily uninstall MalwareBytes.  Feel free to reinstall it once we've finished troubleshooting.

 

Update Intel stuff (particular Dynamic Platform and Thermal Framework) to the latest, W10 compatible version from the Gigabyte support site for your system.

 

Beyond that, the Driver Verifier dump didn't show a 3rd party driver (which the instructions told it to look for).
As such, it's either a Windows problem or a hardware problem.
Continue with the diagnostics, the next step(s) are:

 

My suggested way to diagnose a hardware problem (3 steps):

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [:(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

 

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan 27 12:02:25.787 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012718-4406-01.dmp]
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:08:30.526
Probably caused by :memory_corruption
BugCheck EF, {ffffbb0bddb04080, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffbb0bddb04080, 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:  csrss.exe
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6200U CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2400
  BIOS Version                  P09AFN.043.170601.KS
  BIOS Release Date             06/01/2017
  Manufacturer                  SAMSUNG ELECTRONICS CO., LTD.
  Product Name                  900X3L
  Baseboard Product             SAMSUNG_NP_900X3L
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 27 11:37:20.124 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012718-5812-01.dmp]
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:00:05.923
Probably caused by :ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+df )
BugCheck C4, {2006, ffff9701cbbaa4e8, fffff802d04401b0, ffff8281008075c8}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments:
Arg1: 0000000000002006, subclass of driver violation.
Arg2: ffff9701cbbaa4e8
Arg3: fffff802d04401b0
Arg4: ffff8281008075c8
BUGCHECK_STR:  0xc4_2006
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0xc4_2006_VRF_nt!VerifierBugCheckIfAppropriate
CPUID:        "Intel® Core™ i5-6200U CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Jan 27 12:02:25.787 2018 (UTC - 5:00)**************************
intelppm.sys                                  Thu Sep 22 06:43:11 2011 (4E7B113F)
rt640x64.sys                                  Fri Mar 11 00:57:50 2016 (56E25E5E)
iaStorA.sys                                   Thu Mar 17 06:10:27 2016 (56EA8293)
dptf_acpi.sys                                 Fri May 13 14:00:22 2016 (57361636)
dptf_cpu.sys                                  Fri May 13 14:00:26 2016 (5736163A)
esif_lf.sys                                   Fri May 13 14:00:40 2016 (57361648)
PTPFilter.sys                                 Mon Nov 21 01:33:55 2016 (58329553)
iaLPSS2i_I2C.sys                              Wed Jun 14 00:00:59 2017 (5940B4FB)
iaLPSS2i_GPIO2.sys                            Wed Jun 14 00:01:22 2017 (5940B512)
SamsungEventController.sys                    Wed Aug  9 21:19:20 2017 (598BB498)
TeeDriverW8x64.sys                            Tue Oct  3 02:21:38 2017 (59D32C72)
RTKVHD64.sys                                  Tue Oct 17 09:20:46 2017 (59E603AE)
IntcDAud.sys                                  Thu Oct 26 14:10:57 2017 (59F22531)
igdkmd64.sys                                  Fri Oct 27 14:25:47 2017 (59F37A2B)
Netwtw06.sys                                  Thu Nov  2 12:24:18 2017 (59FB46B2)
ibtusb.sys                                    Tue Dec  5 23:54:06 2017 (5A2777EE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 27 11:37:20.124 2018 (UTC - 5:00)**************************
mbae64.sys                                    Wed Jan 11 12:08:00 2017 (58766670)


http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=dptf_acpi.sys
http://www.carrona.org/drivers/driver.php?id=dptf_cpu.sys
http://www.carrona.org/drivers/driver.php?id=esif_lf.sys
PTPFilter.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=iaLPSS2i_I2C.sys
iaLPSS2i_GPIO2.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.
SamsungEventController.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=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
Netwtw06.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=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.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.

#14 george144

george144
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:14 PM

Posted 27 January 2018 - 11:33 PM

Attached File  SysnativeFileCollectionApp.zip   578.91KB   2 downloads

 

Attached File  SysnativeFileCollectionApp.zip   578.91KB   2 downloadsI had HWMoniter (CPUID) running for for about an hour with no problems, then went out to dinner.  When I returned,  the system had shut down.  While taking a SysNativel, system crashed again with BSOD, 'CRITICAL PROCESS FAILED'.  Ran sysNative again, and it is attached.

 

 



#15 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:14 PM

Posted 28 January 2018 - 01:44 PM

No new BSOD info in the Sysnative upload.
I suggest completing the hardware diagnostics that I suggested previously:

 

My suggested way to diagnose a hardware problem (3 steps):

Step #1)  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
    Please run ALL of the tests and let us know the results.  (If you can't run all the tests, then at least run these free, bootable diagnostics:  http://www.carrona.org/initdiag.html )
    FYI - These are the tests and what we usually see for the reports:

        1 - Antivirus/antimalware scans:  In short, if there are Trojans or other serious malware - start over in the Am I Infected forums
        2 - Memory diagnostics:  Run MemTest86+ for at least 3 passes.  If booting from UEFI, run MemTest86 instead.  Let us know if there were any errors reported
        3 - Hard Drive diagnostics:  Don't sweat the details here.  In short, run the Seagate Seatools Long/Extended test from a bootable disk.  If unable to run it from a bootable disk (UEFI and some others), then run the Seagate Seatools for Windows from within Windows.  There are no diagnostics for SSD's, just run the Crystal Mark tests and let us know if there were any failures
        4 - Furmark:  run the test until the temperature stabilizes.  Don't let it get much over 90ºC.  Let us know the temp it stabilizes at and if there were any problems running the test (other than slowness).
        5 - Prime95:  run the Blend test for 24 hours (this may not be possible, but run it as long as you can.  Look for errors in the output, or for problems running the test (freezes/crashes)
        6 - Video 2 (other video tests):  there's several tests here.  Run all of them.  I'm especially interested in the Video Memory Test.  Let us know the results of the test(s)
          - A - simtek.org memtest
          - B - Video memory stress test
          - C - Artifact Locator
          - D - OCCT - 4 built in tests for CPU, GPU, PSU
          - E - Video Memory Stress Test
        7 - CPU tests:  run at least one test on your CPU and let us know the result.


Step #2)  If all the tests pass, then try to perform a clean install of Windows:

A clean install is:
        - Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
        - The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
        - Windows is fully updated after it's installed.  That's ALL updates - none excepted.
        - NO 3rd party software is installed.
        - There are no errors in Device Manager (if you find any, post back for suggestions).
         - The BIOS/UEFI is updated to the latest available version (this presumes that the system is compatible w/Windows 10 also).

        This will wipe everything off of the computer, so it's advisable to backup your stuff first.
        Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

        If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
        One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them [:(]
        Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
        But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
        The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
        You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

        The point of doing this (the clean install) is to:
        - rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
        - rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
        - so, if the problem continues, it must be a hardware problem.

        OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


Step #3)  Then, if the clean install confirms the hardware problem, try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users