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

Desperate - Mulitple Win 10 BSODs with various bug check strings


  • Please log in to reply
5 replies to this topic

#1 Coridan75

Coridan75

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:41 AM

Posted 10 December 2016 - 10:48 PM

Hello guys,

 

I have been lurking here for a while sifting though the topics searching for a solution to my BSOD problem. As I did not find one, I now post for myself. Here is my story: In January 2016 I upgraded my self-built Desktop-PC with new hardware and progressed from Vista x64 to Win 10 x64 trough clean installation. My system now sports:

 

CPU:          Intel i5 Skylake 6600K (not overclocked)

RAM:          G.Skill RipJaws V DDR4-3200 CL16 Dual Kit 2 x 4 GB

MB:            MSI Z170A Gaming Pro

Graphics:   Asus HD 7950 DirectCU-II PCIe 3.0 x 16 3 GB

SSD:          Samsung 850 EVO 250 GB

HDD1:        Samsung HD103UJ 1 TB

HDD2:        Samsung HD103SJ 1 TB

Sound:       X-Fi Xtreme Gamer Soundcard

Power:       beQuiet 500W PSU

 

Here are some screencaps of system info from CPU-Z:

 

http://imgur.com/pRmOZEx

http://imgur.com/3eIo4KB

http://imgur.com/OvD93Uv

http://imgur.com/wgNY5Zf

 

A screencap of bluescreen viewer with all recent minidumps and bugcheck strings:

 

http://imgur.com/JsdclQ4

 

 

During the summer I encountered few bluescreens which only occurred after waking the system up from standby/sleep/hibernation mode. I suspected that this was caused by a driver which could not handle the power state and did not care too much.

 

Since the beginning of December, the frequency and severity of the crashes increased greatly. I sometimes got small bootloops, where the system would crash even after normal startup/cold boot after some time - a thing my PC never did before - and re-crash multiple times during the following boot-process. The system started working again after a few loops, but as I said I never witnessed this behaviour before. I did not install any new hard- or (significant) software in December. Right now, the system crashes randomly during day-to-day usage such as gaming, browsing the web and watching streams, I could not identify any specific trigger. Any help would be appreciated as I don't know what to do next to fix this nagging issue.

 

Here is what I already did:

 

  • Enable driver verfier: I used my PC with driver verfier for over 48 hours following the tutorial of jcgriff2. I don't think it detected any faulty driver/crash the system or throw a bluescreen.
  • Run Memtest86 V7.1 for over 9 hours (19 passes) with no errors reported
  • Updated all hardware drivers (including UEFI, graphics, audio, chipset)
  • Load-tested the system with Prime95/Furmark and surveilled the temperatures of graphics/CPU -> they were in acceptable range
  • Tried to analyze the Minidumps with WinDbgX64 to find the error. I couldn't identify anything as I am not knowledgeable enough. One common "string" in all of them was memory_corruption
  • Run    sfc /scannow    from an elevated command prompt (no errors found or corrected)
  • Run    chkdsk /r /f    at boot time for my system SSD (no errors found or corrrected)
  • Run a full system scan with Malwarebytes Anti-Malware (no threats found  |  I don't use another antivirus apart from Windows-internal tools)

I attached the relevant files according to the stickied BSOD posting tutorial.

 

Apart from completely reinstalling the system - my next and last resort measure - I am running out of options. I would greatly appreciate any help which could aid me on my journey towards a stable system.

 

With kind regards,

 

Coridan75

 

 

----------------- Major Edit 11. Dec:

 

During some load-testing with Prime95 blend test, I encountered another instance of these "small" bootloops I described above. After about ~ 1 minute of Prime95 the system halted. So now I can give detailed information about this error:

  • The system initially failed with an IRQL_NOT_LESS_OR_EQUAL BSOD during Prime95 and no other programs running
  • During following boot-up we got a KERNEL_SECURITY_CHECK_FAILURE bluescreen
  • While the following boot, the system threw a BAD_SYSTEM_CONFIG bluescreen stop and by (automatically) entering the Windows system recovery utility, we were able to start the system normally

Note that only the first BSOD produced a memory dump, which I attached at this post, too. The file for this specific crash bears the name "PrimeCrash Minidump.zip". Again, the common denominator of all this minidumps in WInDbg "!analyze -v" is the generic string "memory corruption", but please see for yourself. Again I thank you in advance for helping me getting a stable system again.

 

----- Small After-Edit:

 

I reran the Prime95 blend-test after I could reboot correctly. Right now it has been running perfectly for about sixty minutes, the temps are in an acceptable range. Screencap of the process delivered here:

 

http://imgur.com/3UZuwCx

 

It becomes clear that I still fail to find an "algorithm" to crash the system consistently!

 

--- Update:

 

After approx. 2 hours of consistent Prime95 blend-test (no other usage at point of stop error) the system crashed again with a new and unique bug check string:  DEVICE_QUEUE_NOT_BUSY (reported by BlueScreenViewer app). I uploaded the corresponding minidump zipped with the name "PrimeCrash_2HoursIn". Thanks for looking at it!

Attached Files


Edited by Coridan75, 11 December 2016 - 08:57 AM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


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

Posted 12 December 2016 - 05:09 AM

Memory corruption is the most common problem seen in BSOD's.

This does not mean that the physical RAM is corrupted, rather I believe that it refers to the structures held in virtual memory.

As such, it's possible for these corruptions to be in almost any part of the computer (for example, the pagefile stores some virtual memory on the hard drive).

 

Prime95 tests 3 things (primarily): 

- RAM

- CPU cache

- memory controller (on the CPU in the i5/i7 CPU's)

The Blend test tests mainly RAM, but does test a bit of the other things

It's possible to have bad RAM, to pass MemTest, and to have Prime95 find problems with the RAM.
I strongly suggest running the Intel Processor Diagnostic tool to help rule out CPU issues (it's at the bottom of this page:  http://www.carrona.org/hwdiag.html )

 

Your UEFI/BIOS (version 1.A0) dates from 2016.  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.

You have 3 hard drives.  What is the age of your Power Supply?

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

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

Please ensure that you turn Driver Verifier off. You can do this by opening up verifier.exe, selecting "Delete existing settings" then clicking on the "Finish" button

Reboot for changes to take effect.

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
[QUOTE]**************************Sun Dec 11 08:38:09.984 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121116-8890-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:0 days 2:34:25.683
*** ERROR: Module load completed but symbols could not be loaded for storahci.sys
Probably caused by :storahci.sys ( storahci+613d )
BugCheck 2, {8, 3436b3, ffffc401dc13f080, 4130000000000000}
BugCheck Info: DEVICE_QUEUE_NOT_BUSY (2)
Arguments:
Arg1: 0000000000000008
Arg2: 00000000003436b3
Arg3: ffffc401dc13f080
Arg4: 4130000000000000
BUGCHECK_STR:  0x2
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID: 0x2_VRF_storahci!unknown_function
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 11 06:01:34.428 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121116-8437-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:0 days 0:02:50.129
Probably caused by :memory_corruption
BugCheck A, {28, 2, 0, fffff802c1d1b04b}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802c1d1b04b, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 10 21:30:50.736 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121116-11343-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:1 days 9:35:14.548
*** WARNING: Unable to verify timestamp for win32kfull.sys
*** ERROR: Module load completed but symbols could not be loaded for win32kfull.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 139, {3, ffff9a0098f3f5f0, ffff9a0098f3f548, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff9a0098f3f5f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff9a0098f3f548, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec  9 10:19:31.504 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120916-8015-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
System Uptime:0 days 0:00:08.206
*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
Probably caused by :memory_corruption
BugCheck 7F, {8, fffff803aabbce70, ffff968001ba3fa0, fffff803a8fe3114}
BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP (7f)
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff803aabbce70
Arg3: ffff968001ba3fa0
Arg4: fffff803a8fe3114
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
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:

**************************Sun Dec 11 08:38:09.984 2016 (UTC - 5:00)**************************
ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)
iaLPSS2_UART2.sys           Mon May  4 08:41:32 2015 (554768FC)
AtihdWT6.sys                Tue Jul  7 21:28:10 2015 (559C7CAA)
emupia2k.sys                Fri Sep  4 07:50:07 2015 (55E9856F)
ctsfm2k.sys                 Fri Sep  4 07:50:34 2015 (55E9858A)
ctoss2k.sys                 Fri Sep  4 07:50:58 2015 (55E985A2)
ha20x2k.sys                 Fri Sep  4 07:52:19 2015 (55E985F3)
ctaud2k.sys                 Fri Sep  4 07:52:58 2015 (55E9861A)
ctprxy2k.sys                Fri Sep  4 07:53:03 2015 (55E9861F)
CTEXFIFX.SYS                Fri Sep  4 07:54:34 2015 (55E9867A)
CT20XUT.SYS                 Fri Sep  4 07:54:40 2015 (55E98680)
CTHWIUT.SYS                 Fri Sep  4 07:54:44 2015 (55E98684)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
iaLPSS2i_I2C.sys            Wed Mar  2 21:06:42 2016 (56D79C32)
iaLPSS2i_GPIO2.sys          Wed Mar  2 21:06:59 2016 (56D79C43)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
TeeDriverW8x64.sys          Wed Jul 13 12:52:17 2016 (578671C1)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
atikmpag.sys                Fri Sep 16 14:50:37 2016 (57DC3EFD)
atikmdag.sys                Fri Sep 16 15:12:45 2016 (57DC442D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 10 21:30:50.736 2016 (UTC - 5:00)**************************
BEDaisy.sys                 Sun Oct  2 03:06:55 2016 (57F0B20F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  4 07:11:56.550 2016 (UTC - 5:00)**************************
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
atikmpag.sys                Wed Nov 23 18:27:50 2016 (583625F6)
atikmdag.sys                Wed Nov 23 18:50:31 2016 (58362B47)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec  3 09:14:40.766 2016 (UTC - 5:00)**************************
asmtxhci.sys                Wed Jun  3 02:33:15 2015 (556E9FAB)
asmthub3.sys                Wed Jun  3 02:33:19 2015 (556E9FAF)
TeeDriverW8x64.sys          Mon Aug 31 15:49:07 2015 (55E4AFB3)
RTKVHD64.sys                Tue Apr 19 06:31:00 2016 (571608E4)


http://www.carrona.org/drivers/driver.php?id=ctac32k.sys
iaLPSS2_UART2.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=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=emupia2k.sys
http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys
http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys
http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys
http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys
http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys
http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS
http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS
http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS
cpuz139_x64.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=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
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.
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=BEDaisy.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.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.

#3 Coridan75

Coridan75
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:41 AM

Posted 12 December 2016 - 03:37 PM

Hello usasma and all future helpers/readers,

 

thank you for looking at my PC-related problems. I will answer your questions as best as I can and tried to complete the hardware check utilities.

 

  • I have one Samsung SSD (850 EVO 250 GB, since January 2016) and two 1 TB Samsung HDDs (1st since ~ 2010, 2nd since ~ 2012)
  • I have to correct me on my PSU, it is actually a beQuiet! BQT S6-SYS-UA-700W device       -> Link to photo of specifications:  http://imgur.com/0cZhXFC

The above mentioned PSU is from 2010, when I built my first system (Intel LGA775-socket Q9550 overclocked to 4 x 3.8 Ghz, 8 GB Mushkin DDR2-800 RAM, xfx 780i SLI Mainboard, ATi Radeon HD 4870 X2 graphics card, Creative X-Fi Xtreme Gamer soundcard, CoolerMaster HAF 932 Big Tower Case). The current system as specified in my initial post inherited the power supply, the two HDDs, the sound card, the computer case and the DVD optical drive from the former system.

 

Yesterday I uninstalled the PCI Xtreme Gamer soundcard (software and physical device) due to a gut feeling of incompatibility. Afterwards I ran a Prime95 Blend test overnight for 9 hours without errors or BSODs. The CPU temperatures were monitored with HWMonitor and did not exceed 74° Celsius.

 

Unfortunately, I had a system stop crash during a short (approximately after 30 to 40 minutes) P95 blend-test at 19.00 o'clock / 7 PM local time which I had started after using the PC through the day without problems. The given bug check string is "ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY". That was a huge blow to morale, as I hoped that the soundcard was the issue. :( I attached the corresponding memor dump to this post and named it "P95Crash_short". Thanks in advance for looking at it.

 

To rule out the CPU I completed the Intel Processor Diagnostic utility twice. The system passed without errors, I uploaded screencaps of the runs to imgur: http://imgur.com/a/F0AjO .

The results are compiled in a TXT-file I attached under the name IntelResults.TXT.

 

However, during my attempt to screenshot the results on the second run, my system hard-crashed yet again with the bug check string "MEMORY_MANAGEMENT". The respective minidump is also attached under the name "MiscellaneousCrash". This specific crash induced the "known" boot-crash-loop with the bug check string "BAD_SYSTEM_CONFIG_INFO" of which none produced any memory dump. After a few attempts, windows start repair kicked in and I was able to boot the system normally. An instant use of ->  sfc /scannow   and  ->   chkdsk    from an elevated command prompt did not unveil any errors.

 

Apart from that, I did some load-testing of the graphics card. I both ran Prime95 blend-test and FurMark in parallel, surveilling system temperatures. They were in acceptable ranges (below 74°C CPU, GPU temps stabilized below 65°C) and the system did not crash or show any signs of faulty behaviour. Screencap of FurMark: http://imgur.com/c0nvirE

 

Furthermore, I did analyze my HDDs and SSD with CrystalDiskX64. All storage devices were in good shape, I did upload screencaps of that here: http://imgur.com/a/UnOMU

With Samsung SSDMagician, I checked for firmware updates of the SSD and found none (state-of-the-art firmware with name: EMT02B6Q). The energy saving configuration of the system is set up following the guidelines by the Magician software for maximum performance. My virtual memory/pagefile is located on C:\, the system partition which is the Samsung SSD. The size of the pagefile is managed by the system. I rebuilt the pagefile yesterday by completely disabling (size zero) it for one restart and then re-setting it to system managed. My configuration is as follows: http://imgur.com/a/7Qazd

Translation help:  Auslagerungsdatei = Pagefile | Keine = No / None | Systemverwaltet = system-managed | Laufwerk = drive | Empfohlen = recommended | Zurzeit zugeteilt = currently allocated/reserved

 

Other steps I have done:

 

  1. Scan system for malware with Malwarebytes Anti-Malware (MBAM) (no threats found)
  2. Run the OCCT Tool Power supply test - no errors detected
  3. Disable driver verifier
  4. Opened case and checked for loose cables and RAM modules
  5. Search for Windows Updates manually
  6. Run DISM /Online /Cleanup-Image /RestoreHealth and ~ /ScanHealth  command-line tool from an elevated prompt, which found no errors to repair and/or finished without errors

Steps I plan to do:

  1. Clean system carefully with air compressor
  2. Run another overnight test with Memtest86 V7.1 Free
  3. Update mainboard UEFI to 1.C
  4. Last resort measure: Reinstall windows cleanly

A question in that regard would be if there is still a chance that these BSODs are "luckily only" software related so that a Windows reinstallation can fix this, or do you think that the undelying cause is most probably hardware failure. I am quite dependant on that system, should I slow-paced consider new hardware? :(

 

Many, many thanks for partaking on my journey to a stable system.

 

With kind regards,

 

Coridan 75

Attached Files


Edited by Coridan75, 12 December 2016 - 06:47 PM.


#4 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:05:41 AM

Posted 14 December 2016 - 07:44 AM

Fantastic troubleshooting!!!  If I understand correctly, you haven't run the hard drive diagnostics on the regular hard drives.

The SMART diagnostics are only "predictive" - they only let you know that a problem is likely or unlikely.  And, the SMART attributes aren't very good at some types of hard drive failurs (at work I frequently see dead/dying hard drives that have good SMART attributes)>

I would suggest running the Seagate Seatools or Western Digitak Data LifeGuard tests on the regular hard drives.

 

Please understand that diagnostics are just tests that lead us in a certain direction.

They are not 100% accurate - so the actual "test" is the replacing of a component.

We use the tests to decrease the amount of time spent hunting for bad component, and to avoid swapping parts around until you find a problem (and this'll save you money).

 

Have you run any of the other Prime95 tests (Small FFT's or Large FFT's)?

If so, does the system crash faster or slower than with the Blend test (or maybe not crash at all)?

What I'm trying to figure out here is if it's the RAM or the CPU (although things like the motherboard can still be involved).

 

Another thing that you can try is to run Prime95 on the individual memory sticks to see if they crash.

Start by testing them individually in the first slot.  Then move onto the other slots (with one that doesn't cause crashses, if possible) and test them.

 

I think this is a hardware problem, either RAM, CPU or motherboard.

You may want to try other CPU stress tests to see if that causes problems.

 

As I recall, GSkill RAM should have a lifetime warranty.

If so, you may want to contact GSkill and ask them what you can do to get replacement RAM.

http://www.gskill.com/en/warranty

 

If you get new RAM from GSkill and the problems continue - then we've ruled out the RAM as a problem.

If the problems don't continue - then it's fixed!!!

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 12 13:49:12.751 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121216-7140-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:0 days 0:38:28.449
Probably caused by :memory_corruption
BugCheck 1A, {5003, fffff96fc04471a0, 1e87, 23e20003d1e}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff96fc04471a0
Arg3: 0000000000001e87
Arg4: 0000023e20003d1e
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  SnippingTool.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 12 13:09:48.517 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121216-7296-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.479.amd64fre.rs1_release.161110-2025
System Uptime:0 days 6:52:42.227
Probably caused by :memory_corruption
BugCheck FC, {ffffbe05624d3650, 8000000251749963, ffffe6015c5074e0, 2}
BugCheck Info: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
Arguments:
Arg1: ffffbe05624d3650, Virtual address for the attempted execute.
Arg2: 8000000251749963, PTE contents.
Arg3: ffffe6015c5074e0, (reserved)
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  0xFC
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  prime95.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504
  BIOS Version                  1.A0
  BIOS Release Date             07/15/2016
  Manufacturer                  MSI
  Product Name                  MS-7984
  Baseboard Product             Z170A GAMING PRO (MS-7984)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



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 Dec 12 13:49:12.751 2016 (UTC - 5:00)**************************
iaLPSS2_UART2.sys           Mon May  4 08:41:32 2015 (554768FC)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
iaLPSS2i_I2C.sys            Wed Mar  2 21:06:42 2016 (56D79C32)
iaLPSS2i_GPIO2.sys          Wed Mar  2 21:06:59 2016 (56D79C43)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
TeeDriverW8x64.sys          Wed Jul 13 12:52:17 2016 (578671C1)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
atikmpag.sys                Fri Sep 16 14:50:37 2016 (57DC3EFD)
atikmdag.sys                Fri Sep 16 15:12:45 2016 (57DC442D)
AtihdWT6.sys                Tue Sep 20 19:17:24 2016 (57E1C384)
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 12 13:09:48.517 2016 (UTC - 5:00)**************************
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)

iaLPSS2_UART2.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=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
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.
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdWT6.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
cpuz139_x64.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.
 


Edited by usasma, 14 December 2016 - 07:45 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.

#5 Coridan75

Coridan75
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:09:41 AM

Posted 17 December 2016 - 09:46 AM

Hello usasma (and all readers),

 

thank you for your work on my PC problems. I will again try to do my best at answering your questions and troubleshooting the underlying cause of the stop errors.

 

Yes you were right in the assumption on my HDDs, I did only S.M.A.R.T. readings on CrystalDiskX64. I downloaded SeaTools for Windows and tested my two magnetic HDDs. All the results were positive/pass. I did the following tests (again all with screencaps of the process):

 

  1. SMART-Test           -> http://imgur.com/a/E7Dt5
  2. Short self test         -> http://imgur.com/a/Spil5
  3. Short generic test   -> http://imgur.com/a/ZFJ64

I might modify my post later and add the long test results for better troubleshooting.

 

As of now, I am inside of a "phase of stability" as it seems, my last known crashes were on December 14th. On that day I had the first crash during standard usage, e.g. Firefox and Explorer open. With BlueScreenViewer, I was able to determine the bug check string, which is "REFERENCE_BY_POINTER". I attached the corresponding minidump file under the name "StandardCrash". Thanks in advance for analyzing it! After that crash, I went to work and ran a Memtest86 V7.1 Free memory check on the RAM. Here it gets interesting: After coming back (test duration at that moment: ~ 7 hours 30 min) I for the first time ever saw errors on the log screen! Sadly, I failed at saving the HTML report due to wrong coordination of QWERTZ and QWERTY keyboard layout by Memtest. I, however, saved a screencap with my phone (sorry for the bad quality): -> http://imgur.com/a/S49pZ

My test configuration was: All tests 1 - 13, single CPU core #0. Note that while selecting multicore options, I sometimes have had freezes of Memtest86 V7.1Free. After some digging in their forums, it became clear that this might be a bug-induced behaviour, since they have to rely on the UEFI-programmers to supply the multicore support. 

 

I re-run the test immediately with the test number (#7) and the memory address (I basically retested everything with test #6 and #7) that exposed the error, but it failed to find another fault.

 

Afterwards, I went back to using the computer while running a Prime95 Large-FFT torture test in the background. On 23:33 h or 11:30 pm, the PC BSOD'd again during internet usage and said Prime95 test. The bug check string in in this case is called "UNEXPECTED_KERNEL_MODE_TRAP".  I enclosed the memory dump, it bears the name "P95_LargeFFT". After this event, the PC was not able to boot normally for a while and entered a state, which I would describe as "panting" - all LEDs/lights would light up, the fans would spin up like during normal startup, but then power off completely for a second and then restarting again (on-off-pattern without any interference of mine). This went on for about 5 to 10 seconds, then the PC booted normally as it was able to start the BIOS/UEFI. A short brainwave told me to get into Memtest, where I immediately started full testing.

 

I again run a full test only on CPU core #0, and about 11,500 errors showed up after only two minutes of testing! Screencap of that, again sorry for the bad quality: ->http://imgur.com/a/9uUFp

I then relaunched the test on core #3 and then again on core #0, where no errors were reported! Strange behaviour ...

 

Since then, I conducted two Prime95 LargeFFT torture tests with the durations (1)   2 h 15 min and (2)   9 h 45 min, both ran flawlessly and HWMonitor reported that the CPU-temperature did not exceed 75 ° C. Furthermore, I did multiple Memtest runs, of which all failed to report any errors like the ones earlier. The longest overnight run lasted approx. 11 hours,here is the screencap of the report: http://imgur.com/a/qqcIT

 

Note that this run was done on core # 3. Other, shorter runs on core # 0 did not unveil any new errors either.

 

I noticed the error with QWERTZ/QWERTY and am now able to save the Memtest HTML-reports succesfully :) However, the forum uploader does not allow me to upload them, hence I sceencapped them. On December 15th and 16th, there were no crashes.

 

It appears that the error shows up not that often, which aligns itself with my impression that I can still use the PC normally (gaming/working/surfing/streaming) for a quite a large percentage of time. I currently fail to crash the system frequently, so I can't really say whether LargeFFT or Blend crash faster and/or more often.

 

I am hopeful for your answer usasma and thankful that you help me. I will contact G.Skill for replacement and consider buying replacement sticks if your analysis of the recent crashes strongly hints at faulty RAM.

 

With kind regards,

 

Coridan75

 

 

--------------------------- Big Edit 18th December: --------------------

 

I additionally conducted the "Long generic drive test" in SeaTools for both my magnetic HDDs which both passed the test flawlessly despite their advanced age. I uploaded a screencap of the results on imgur here:   ->  http://imgur.com/a/YvSDm

 

To further investigate whether the CPU, RAM or motherboard is the origin of the stop errors, I ran a 4 hour Prime95 SmallFFT torture test which completed without errors. During that time the PC was not in use otherwise and the CPU temperature - monitored by HWMonitor - did not exceed 74°C.

 

Today, I attempted to run another overnight Prime95 blend test which unfortunately did not finish correctly. Upon returning to my PC this morning, I found it running (fans, motherboard LEDs, USB device were powered) but it did not react to any input as the screen stayed black even on hitting keys or moving the mouse. It looked like it had locked up/freeze during a state when the monitor was powered off for energy saving reasons.

 

Sadly this crash did not produce any new memory dump, I checked the folder manually. Even the Prime95 LogFile is inconclusive in that matter as logging simply stops at 4:35 AM local time (everything logged as "passed"), which might be about 90 to 120 minutes after starting the blend test (estimate on my part) and me going to sleep.

 

I had to do a hard reset/cut power to restart it. At this point the "known" panting - for the lack of a better word - set in again. This time I recorded a video of it for better troubleshooting, you can find it here:  -> https://youtu.be/1q_xuwX4UBw

 

Note the "EZ debug LEDs" of the MSI Z170A Gaming Pro Mainboard which are in the order (1) CPU (2) DRAM (3) VGA. It seems that RAM was not recognized correctly so that the motherboard restarted again, since the LEDs only advance up to DRAM and then switch to CPU again. I was unable to get the system to boot even after disconnecting all USB device and physically disconnecting it from the wall power line for a while, which helped during the last instances of this "panting".

 

To solve this issue, I removed the RAM stick at slot 4 which led to being able to boot normally. I instantly ran Memtest86 V7.1 on the remaining stick (reduced tests, no hammer & bit fade test, single core #0 used) which completed without error. Screencap of the report (note only 4GB of RAM):   -> http://imgur.com/a/rwYeA

 

To test whether the fault was permanent I reinstalled the stick in slot #4 and - to my surprise - was again able to boot normally. At the moment I am writing this on the system with 8GB/2 sticks installed. This again reinforces the observation that the error shows up infrequently.

 

With kind regards and many thanks,

 

Coridan75

Attached Files


Edited by Coridan75, 18 December 2016 - 07:41 AM.


#6 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:05:41 AM

Posted 20 December 2016 - 05:33 PM

My apologies for the delayed response - I've had a lot of personal things going on, and now I have a cast on my left arm/hand :(

 

You've done excellent troubleshooting once again!

It looks like it's time to try new RAM.  GSkill most likely has a lifetime warranty on your RAM, so you should be able to return it for new sticks after contacting them and describing the problems that you face.

As you've passed the Intel Processor diagnostics, the most likely culprit is the RAM.

Please remember that other problems can affect this (such as a problem with the motherboard or PSU) - but switching the RAM should narrow down the problem area(s).


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