Intermittent BSOD on Samsung NP900X3A

[Posthuman1]

Greetings everyone,

This laptop is fairly new and has top notch specs. Sadly, it crashes randomly with BSOD or reboots since the time I’ve bought it. To make the story short I’ve tried many diagnostic tools including the memtest86 utility overnight. I even made an image of the partition trying to isolate the problem by removing unnecessary applications and bloatware, Windows updates or with no updates, but nothing worked. Every other day or so I leave it idle come back after a while to find out it had a BSOD. Also, on a daily bases I keep the “Application X stopped responding…Close” dialog box and it’s always a different application not a specific one sometimes it’s Explorer or Word it’s random. It is so frustrating.
Attached is my SF diagnostic logs.

Thanks in advance for your help,

 

[Arc]

Hello Posthuman1.

All your BSODs are stop 0x7A, and the dumps are not giving any more info about the probable cause.
As per Carrona.org, STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

Service pack is not missing here, so overlooking that part.

As it is a branded laptop, keeping the points like Cabling, Improperly seated cards, BIOS, and Bad motherboard for the time being.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Seatool for dos: SeaTools | Seagate download

• Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
• You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Rebuild Pagefile.sys

1. Press Win +Pause/Break simultaneously on the keyboard.
2. In the resulting window, click on "Advanced System Settings". It will open as "advanced" tab selected.
3. Under "Performance", click on "Settings" It will Open the Performance Options Dialog.
4. Click on "Advanced". Under Virtual Memory, Click on "Change"
5. Uncheck "Automatically Manage Page File size" then click on "No Page File" > Set > Ok
6. Rebuild and delete Pagefile.sys. It is usually in C:\Windows.
7. Enable page file ... do upto step 5 anain and check "Automatically Manage Page File size", Click on "System Managed Size"> Set > OK.
8. Rebuild the computer.

Let us know how it all goes.
__________________________________________________________________________________
BSOD ANALYSIS:

...............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc50012c60, ffffffffc0000185, 11fa9b880, fffff8a00258c058}

Probably caused by : CI.dll ( CI!CiValidateImageData+2f )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50012c60, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000011fa9b880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00258c058, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800822c420 -- (.trap 0xfffff8800822c420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff000008f274f0 rbx=0000000000000000 rcx=fffff8a00258c000
rdx=fffff8800a8a8000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000d11263 rsp=fffff8800822c5b0 rbp=fffffa8001f89f60
 r8=000000000010ae00  r9=fffff88000d11234 r10=0000000000000000
r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
CI!CiValidateImageData+0x2f:
fffff880`00d11263 8b4958          mov     ecx,dword ptr [rcx+58h] ds:fffff8a0`0258c058=47005f00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f43742 to fffff80002ed0c00

STACK_TEXT:  
fffff880`0822c108 fffff800`02f43742 : 00000000`0000007a fffff6fc`50012c60 ffffffff`c0000185 00000001`1fa9b880 : nt!KeBugCheckEx
fffff880`0822c110 fffff800`02ef791f : fffffa80`04416910 fffff880`0822c280 fffff800`0310b600 fffffa80`04416910 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`0822c1f0 fffff800`02ede1b9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`02f01306 : nt!MiIssueHardFault+0x28b
fffff880`0822c2c0 fffff800`02eced2e : 00000000`00000000 fffff8a0`0258c058 00000000`00002400 fffff8a0`0258c000 : nt!MmAccessFault+0x1399
fffff880`0822c420 fffff880`00d11263 : fffffa80`00000025 fffff800`00000040 00000000`0010ae00 fffffa80`083cb000 : nt!KiPageFault+0x16e
fffff880`0822c5b0 fffff800`0316b95d : fffffa80`04a54510 fffffa80`04a54510 fffff8a0`0258c000 fffffa80`01f89f60 : CI!CiValidateImageData+0x2f
fffff880`0822c790 fffff800`0316ba1d : 00000000`00000000 fffffa80`0000a8a8 fffff880`00000000 fffffa80`0000fe00 : nt!SeValidateImageData+0x21
fffff880`0822c7c0 fffff800`02effb7b : fffffa80`01f89f60 fffffa80`05a07470 00000000`00000000 ffffffff`ffffffff : nt!MiValidateImagePfn+0xb5
fffff880`0822c810 fffff800`02ef791f : fffffa80`05a073b0 fffff880`0822c940 fffffa80`080b7ec8 00006000`00000b60 : nt!MiWaitForInPageComplete+0xa0f
fffff880`0822c8f0 fffff800`02ede28a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0822c980 fffff800`02eced2e : 00000000`00000000 00000000`76f1d2d8 fffffa80`080c1301 00000000`0001652d : nt!MmAccessFault+0x146a
fffff880`0822cae0 00000000`76f59c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`022dea30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f59c12


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CI!CiValidateImageData+2f
fffff880`00d11263 8b4958          mov     ecx,dword ptr [rcx+58h]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  CI!CiValidateImageData+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CI

IMAGE_NAME:  CI.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7c944

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_CI!CiValidateImageData+2f

BUCKET_ID:  X64_0x7a_c0000185_CI!CiValidateImageData+2f

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

2: kd> lmvm CI
start             end                 module name
fffff880`00d06000 fffff880`00dc6000   CI         (pdb symbols)          c:\symbols\ci.pdb\1DF98E11C0874281949A1AB1B1E104851\ci.pdb
    Loaded symbol image file: CI.dll
    Mapped memory image file: c:\symbols\CI.dll\4CE7C944c0000\CI.dll
    Image path: \SystemRoot\system32\CI.dll
    Image name: CI.dll
    Timestamp:        Sat Nov 20 18:42:36 2010 (4CE7C944)
    CheckSum:         000CB0F6
    ImageSize:        000C0000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ci.dll
    OriginalFilename: ci.dll
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  Code Integrity Module
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[Posthuman1]

Thanks Arc for your quick reply. regarding the memory test, viruses, rootkits, faulty hardware etc, I've done my part.
I even took it back to Samsung repair and they've tested the hardware. They re-installed a fresh new image. Personally I believe there is an incompatibility between the hardware and the OS somehow. They never complete anything. Ironically few years back I had a similar issue with a Sony VAIO Z series. It was during the infamous Vista period. They just cut drivers updates. So If I want to point a finger I'll blame Microsoft.
I was just hoping to get more details on the coredump, to pinpoint the problem. I'll dig more for another month before initiating auto destruct sequence on this unit.

 

[Arc]

OK, for any further trouble, let us know.