blue screen errors "NTFS file system / system service exception

Hello, receiving random different BSODs:

NTFS_FILE_SYSTEM
SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGEMENT
CRITICAL_STRUCTURE_CORRUPTION



Details:

Sony Vaio VPC-EH3J1E

Intel Core i3 2350M @ 2.30 GHz

4.00 GB RAM

Windows 7 Home Premium x64

So far I have tested the HDD with 3 different testing tools (CrystalDisk, SamsungHDDTool, and ToolstarHDD Test. All passed. RAM Test has also passed on a 5 pass run. Mainboard was changed in the Notebook last week under Guarantee. What else could this be? Any help is appreciated.

Thanks.




Laptop, only the power suppy connected. RAM tested with Memtest86+ (7pass) and it passed. Mainboard replaced, Hard drive tested with CHKDSK, SamsungHDDTool, and Toolstar HDD Test. Recovery of the system is not possible because the device is a guarantee case and the customer does not want to lose his data. I am able to boot to the desktop. The bluescreens are sporadic. No new software or hardware has been added to this laptop in the last 24 hours. The customer says that he does not add any external hardware devices to the laptop when he uses it. The laptop is only 3 months old.

I have downloaded and installed ALL drivers from the Sony Vaio support site. After the first restart, I was thrown another 2 BSODs: SYSTEM_SERVICE_EXCEPTION (0x0000003B) and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (0x1000007E). So far the following work has been done on this notebook:

1. Mainboard replaced
2. RAM Test with Memtest86+ passed
3. Test RAM used: passed
4. Drivers updated (all)
5. Hard Drive tested with 3 different tools: all passed
6. Test Hard Drive used: passed
7. Drivers updated (all) again

It's still throwing BSODs. There are no open service/problem report bulletins on the Sony Vaio support site about this make and model notebook. Recovery is not possible. We are not authorized to format the hard drive from the customer.

Hello PartyFerret.

According to Carrona.org, STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

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.

Let us know the results.

Code:

crash dump file: E:\Debug4\010213-17908-01.dmp
uptime: 00:05:58
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A039D895F035F9, 0xB3B7465EE86D054F, 0xFFFFF80002F0FEA0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Driver verifier is then your next step, as suggested by Arc.

A verifier enabled minidump is also silent about the drivers.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff9800c294ba8, 2, 0, fffff8000376f2b9}

Probably caused by : ntkrnlmp.exe ( nt!ViPendingCompleteAfterWait+49 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff9800c294ba8, 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: fffff8000376f2b9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fd100
GetUlongFromAddress: unable to read from fffff800034fd1c0
 fffff9800c294ba8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ViPendingCompleteAfterWait+49
fffff800`0376f2b9 488baeb8000000  mov     rbp,qword ptr [rsi+0B8h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880035249f0 -- (.trap 0xfffff880035249f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007e72c10
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000376f2b9 rsp=fffff88003524b80 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffffa8003cbafe2 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ViPendingCompleteAfterWait+0x49:
fffff800`0376f2b9 488baeb8000000  mov     rbp,qword ptr [rsi+0B8h] ds:00000000`000000b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032cd569 to fffff800032cdfc0

STACK_TEXT:  
fffff880`035248a8 fffff800`032cd569 : 00000000`0000000a fffff980`0c294ba8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`035248b0 fffff800`032cc1e0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07e72c10 : nt!KiBugCheckDispatch+0x69
fffff880`035249f0 fffff800`0376f2b9 : 00000000`00000000 fffffa80`07e72c10 00000000`00000080 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03524b80 fffff800`0376f36c : fffff800`03473d60 00000000`00000080 fffffa80`03cf6740 59eadb49`00000000 : nt!ViPendingCompleteAfterWait+0x49
fffff880`03524bc0 fffff800`03564e5a : 00000000`ffffffff cd21544c`00000004 fffff8a0`00021c10 fffff8a0`00021c10 : nt!ViPendingWorkerThread+0x2c
fffff880`03524c00 fffff800`032bed26 : fffff880`009ea180 fffffa80`03d21660 fffff880`009f4fc0 fffff8a0`03d79420 : nt!PspSystemThreadStartup+0x5a
fffff880`03524c40 00000000`00000000 : fffff880`03525000 fffff880`0351f000 fffff880`035248d0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ViPendingCompleteAfterWait+49
fffff800`0376f2b9 488baeb8000000  mov     rbp,qword ptr [rsi+0B8h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!ViPendingCompleteAfterWait+49

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!ViPendingCompleteAfterWait+49

BUCKET_ID:  X64_0xA_VRF_nt!ViPendingCompleteAfterWait+49

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

Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

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. We need the report that it is clean. Also I am asking the hardware experts to see if your hardware is compatible are not. Fill up your system specs.
See your system specs and fill it up here.

Run SFC /SCANNOW Command - System File Checker

Let us know the results.

I'm taking a guess here, but could this be CPU - related???

Have you tried stress testing the CPU?
CPU - Stress Test Using IntelBurnTest