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

BSOD Every Few Days with Unknown Origin


  • Please log in to reply
13 replies to this topic

#1 hpspec

hpspec

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 05 September 2017 - 02:34 PM

Hello!

 

I have a machine that I have been diagnosing for months. It will randomly BSOD and reboot every few days. I have performed multiple bare metal installs of Windows 10 with the same results. Here is what I have checked:

  1. BIOS is up-to-date
  2. All drivers downloaded directly from manufacturer
  3. 100% of Windows Updates are installed
  4. No software installed after Windows except WinDbg and SeaTools
  5. Memtest86 UEFI completed its four passes with 0 errors
  6. Hard drive swapped with a brand new one, same errors occur

**I have not discovered what causes the BSOD - the computer is clean, has no extra apps installed, and is not in use, I just leave it running to monitor when it crashes**

 

Speccy: http://speccy.piriform.com/results/TeDVBeus3j5UOwfZdM5cd7x

 

Attached you will find:

  1. SysnativeFileCollectionApp.zip
  2. WinDbg Output for 9/3/17 Memory.dmp

Thank you for your assistance!

Attached Files



BC AdBot (Login to Remove)

 


#2 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:06:14 AM

Posted 06 September 2017 - 06:11 AM

Only 2 memory dumps included in this upload.

If using a disk cleaner (such as CCleaner), please stop while we're troubleshooting.

 

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

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

Have you run the Seagate Seatools for Windows tests?  In particular, have you run the Long/Extended test?  If so, what were the results?

 

As we only have 2 memory dumps, I'd suggest running these free diagnostics:  http://www.carrona.org/hwdiag.html 

The 2 dumps are different BSOD codes (0x7F and 0xEF), if this random pattern continues - then it may be a hardware problem

Feel free to skip those tests that you've run already, but be sure to run the video tests on the Intel graphics card (as one of the BSOD's blames it's drivers)

Be sure to run both the Furmark and Other video tests.

Let us know the results and we can move on from there.

 

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

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

rt640x64.sys                Tue May  5 12:21:03 2015 (5548EDEF)
Realtek NICDRV 8169 PCIe GBE Family Controller driver [br]  http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
 
RtsUer.sys                  Wed May 27 02:11:14 2015 (55656002)
Realtek USB 2.0 Card Reader driver http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownTypeID=3&GetDown=false
http://www.carrona.org/drivers/driver.php?id=RtsUer.sys
 
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
Intel Management Engine Interface (MEI) driver OEM or http://downloadcenter.intel.com[br][br]Installation instructions - http://www.sysnative.com/forums/windows-10-a/18573-windows-10-error-0x800f081f-source-file-not-found.html#post144391
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
 
 


Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sun Sep  3 11:11:51.691 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\090317-15359-01.dmp]
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:5 days 18:24:46.335
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck EF, {ffffac85a14437c0, 0, 0, 0}
BugCheck Info: CRITICAL_PROCESS_DIED (ef)
Arguments:
Arg1: ffffac85a14437c0, 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
BUGCHECK_STR:  0xEF
DEFAULT_BUCKET_ID:  ZEROED_STACK_0xEF
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: ZEROED_STACK_0xEF
CPUID:        "Intel® Core™ i5-4460  CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3193
  BIOS Version                  A08
  BIOS Release Date             06/29/2015
  Manufacturer                  Dell Inc.
  Product Name                  Inspiron 3847
  Baseboard Product             088DT1       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 28 16:46:24.574 2017 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\082817-13875-01.dmp]
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Built by: 15063.0.amd64fre.rs2_release.170317-1834
System Uptime:2 days 22:21:30.221
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 7F, {8, ffff9a01bfea8af0, c386fc40, fffff80def56c673}
BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP (7f)
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff9a01bfea8af0
Arg3: 00000000c386fc40
Arg4: fffff80def56c673
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: ZEROED_STACK_0x7f_8
CPUID:        "Intel® Core™ i5-4460  CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3193
  BIOS Version                  A08
  BIOS Release Date             06/29/2015
  Manufacturer                  Dell Inc.
  Product Name                  Inspiron 3847
  Baseboard Product             088DT1       
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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 Sep  3 11:11:51.691 2017 (UTC - 4:00)**************************
rt640x64.sys                Tue May  5 12:21:03 2015 (5548EDEF)
MpKslfd4de74c.sys           Tue May 19 21:50:37 2015 (555BE86D)
MpKslc6945b63.sys           Tue May 19 21:50:37 2015 (555BE86D)
RtsUer.sys                  Wed May 27 02:11:14 2015 (55656002)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
igdkmd64.sys                Wed Nov 18 14:28:29 2015 (564CD15D)
RTKVHD64.sys                Tue Feb  2 09:39:17 2016 (56B0BF95)
btfilter.sys                Wed Oct 19 03:39:19 2016 (58072327)
athw10x.sys                 Wed Oct 26 01:19:18 2016 (58103CD6)
intelppm.sys                ***** Invalid 2007 Invalid 2007 Invalid
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 28 16:46:24.574 2017 (UTC - 4:00)**************************
igdkmd64.sys                Thu Sep 29 10:43:27 2016 (57ED288F)


http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
MpKslfd4de74c.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.
MpKslc6945b63.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=RtsUer.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=btfilter.sys
http://www.carrona.org/drivers/driver.php?id=athw10x.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.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 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 06 September 2017 - 12:35 PM

Thank you for your response, John!
 
  1. The computer does not nor has it ever had CCleaner installed the last several clean installs
  2. BIOS version is the latest directly from Dell: http://www.dell.com/support/home/us/en/19/product-support/product/inspiron-3847-desktop/drivers/advanced?os=wt64a
  3. I actually have an OCD habit of checking for updates every 15 minutes on all devices. This device was not spared. No Windows Update errors, either.
  4. I started running SeaTools for Windows yesterday. When I came back this morning, the computer was hung at the blue Windows 10 icon with black background. Upon reboot, the Windows repair fails. Trying repair from Windows 10 x64 DVD yields same results. All Advanced Options yield same results. 
  5. SeaTools for DOS does not detect the drive, either using UEFI or forcing BIOS to go Legacy.
  6. I am going to reformat the drive, do a fresh install of Windows 10 from DVD, and then as soon as I get into Windows I will run SeaTools for Windows and report my findings here.


#4 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:06:14 AM

Posted 06 September 2017 - 03:05 PM

You mention other devices.  Can you connect the drive to one of the other devices and run Seatools for Windows (or for DOS) on it there?

If (as I suspect) the hard drive is failing - then you'll likely experience problems reinstalling W10.

 

The guess about it being video was based on the one memory dump that pointed at video drivers.
This is a long shot guess, as hardware issues tend to spit errors that will involve almost anything on the system.


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 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 06 September 2017 - 03:53 PM

Windows 10 reinstalled cleanly and successfully. I will explicitly *not* install any software or drivers by hand - anything installed is what Windows came with.

 

I will pull the drive out and run SeaTools for Windows and report my findings.



#6 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 06 September 2017 - 06:41 PM

Attached are the results of SeaTools for Windows. Passed Long Generic.

Attached Files



#7 softwaremaniac

softwaremaniac

  • Malware Study Hall Senior
  • 833 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:12:14 PM

Posted 06 September 2017 - 06:51 PM

Have you tried running hardware tests like Prime95 Blend?



#8 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 06 September 2017 - 06:59 PM

softwaremaniac,

 

Yes, I have run Prime95 in these configurations for a minimum of 12 hours each without a BSOD:

  1. Smal FFTs
  2. In-place large FFTs
  3. Blend


#9 softwaremaniac

softwaremaniac

  • Malware Study Hall Senior
  • 833 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:12:14 PM

Posted 06 September 2017 - 07:01 PM

Have you tried swapping out the PSU for another one?



#10 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:06:14 AM

Posted 07 September 2017 - 05:48 AM

I would wait 10 days before doing anything else with the system (that's double the interval between the last 2 BSOD's) and see what happens.

Good luck!


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.

#11 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 07 September 2017 - 11:52 AM

softwaremaniac - thank you for this suggestion. I have a PSU from an identical working machine I can try.

 

usasma - I am running Prime95 Blend on the newly reinstalled system. It has been going for 18+ hours at this point. Are you recommending that I let this run for up to 10 days to see if it BSODs again?

 

Thanks!



#12 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 07 September 2017 - 04:05 PM

Update:

Computer had another BSOD ~21 hours into the Prime95 Blend. Based on the dump (analyzed in WinDbg below), there could be a memory issue. Memtest86 did not reveal an issue after many hours, however. I will start by re-seating the memory sticks and running Memtest86 again.

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`fc283000 PsLoadedModuleList = 0xfffff800`fc5cf5c0
Debug session time: Thu Sep  7 13:34:25.941 2017 (UTC - 6:00)
System Uptime: 0 days 23:14:45.596
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000021`9b92e018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a006d987e8b6e8, b3b7135fda6cc20b, ffff862c302ef7a4, 1e}

Page 230c not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32kbase.sys ( win32kbase!DirectComposition::CScaleTransform3DMarshaler::EmitUpdateCommands+84 )

Followup:     MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a006d987e8b6e8, Reserved
Arg2: b3b7135fda6cc20b, Reserved
Arg3: ffff862c302ef7a4, Failure type dependent information
Arg4: 000000000000001e, Type of corrupted region, can be
	0   : A generic data region
	1   : Modification of a function or .pdata
	2   : A processor IDT
	3   : A processor GDT
	4   : Type 1 process list corruption
	5   : Type 2 process list corruption
	6   : Debug routine modification
	7   : Critical MSR modification
	8   : Object type
	9   : A processor IVT
	a   : Modification of a system service function
	b   : A generic session data region
	c   : Modification of a session function or .pdata
	d   : Modification of an import table
	e   : Modification of a session import table
	f   : Ps Win32 callout modification
	10  : Debug switch routine modification
	11  : IRP allocator modification
	12  : Driver call dispatcher modification
	13  : IRP completion dispatcher modification
	14  : IRP deallocator modification
	15  : A processor control register
	16  : Critical floating point control register modification
	17  : Local APIC modification
	18  : Kernel notification callout modification
	19  : Loaded module list modification
	1a  : Type 3 process list corruption
	1b  : Type 4 process list corruption
	1c  : Driver object corruption
	1d  : Executive callback object modification
	1e  : Modification of module padding
	1f  : Modification of a protected process
	20  : A generic data region
	21  : A page hash mismatch
	22  : A session page hash mismatch
	23  : Load config directory modification
	24  : Inverted function table modification
	25  : Session configuration modification
	26  : An extended processor control register
	27  : Type 1 pool corruption
	28  : Type 2 pool corruption
	29  : Type 3 pool corruption
	2a  : Type 4 pool corruption
	101 : General pool corruption
	102 : Modification of win32k.sys

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Inspiron 3847

SYSTEM_SKU:  0622                  

SYSTEM_VERSION:    

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A08

BIOS_DATE:  06/29/2015

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  088DT1       

BASEBOARD_VERSION:  A01

DUMP_TYPE:  1

BUGCHECK_P1: a3a006d987e8b6e8

BUGCHECK_P2: b3b7135fda6cc20b

BUGCHECK_P3: ffff862c302ef7a4

BUGCHECK_P4: 1e

PG_MISMATCH:  8

MEMORY_CORRUPTOR:  ONE_BIT

FAULTING_IP: 
win32kbase!DirectComposition::CScaleTransform3DMarshaler::EmitUpdateCommands+84
ffff862c`302ef7a4 cc              int     3

CPU_COUNT: 4

CPU_MHZ: c79

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x109

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  WOZNIAK

ANALYSIS_SESSION_TIME:  09-07-2017 15:00:00.0612

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT:  
ffffd781`ae90cd78 00000000`00000000 : 00000000`00000109 a3a006d9`87e8b6e8 b3b7135f`da6cc20b ffff862c`302ef7a4 : nt!KeBugCheckEx


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_IP: 
win32kbase!DirectComposition::CScaleTransform3DMarshaler::EmitUpdateCommands+84
ffff862c`302ef7a4 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_NAME:  win32kbase!DirectComposition::CScaleTransform3DMarshaler::EmitUpdateCommands+84

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  753e3609

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME:  2017-09-07T19:34:25.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-07-31 19:23:25

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  449

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     MachineOwner
---------



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

Posted 08 September 2017 - 01:52 PM

The blend test stresses mostly memory - but it's not a sure thing.

The next step would be to test each stick individually - but that's an awfully long time to test each stick

I'd balance that out against the procedure here:  http://www.carrona.org/strpdown.html

And see which is easier for you to try first.


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 hpspec

hpspec
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:14 AM

Posted 13 September 2017 - 10:38 AM

All-

 

Thank you for your support. I ended up running day-long memory scans per stick and found one to be faulty.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users