Blue screen of death BSOD

[leandropich]

Comecou a dar isso últimos dias aqui e hoje esta acontecendo mais vezes seguidas alguém sabe como resolver?
Foto mais anexo de relatório com erros.

------------------------------------------------------------------------------------------

Began to give this last days here and today is going more times in a row does anyone know how to solve?
Photo more attached report with errors.


View attachment 66886

 

[lifetec]

All your dumpfiles are:

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, fffff880040cd5c0, fffff880040cd518, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff880040cd5c0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff880040cd518, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

The dumpfiles give no direct clues.
But 2 times the procesname Photoshop.exe was named.
I also found this unloaded module RtsPStor.sys

Driver Description: Realtek PCIE CardReader Driver
Driver Update Site: select PCIe NOT USB http://www.realtek.com.tw/downloads...=25&Level=4&Conn=3&DownTypeID=3&GetDown=false

Are you using the cardreader for uploading fotos and use photoshop.
Cardreaders sometimes are known for causing BSOD.

Please update to a compatible windows 8 driver.
If there are no compatible windows 8 driver, please uninstall the Cardreader+ drivers and see if this stops the BSOD.

 

[Mysers Briggs]

Could we have a larger dump from C:\Windows\MEMORY.dmp?

2: kd> knL # Child-SP          RetAddr           Call Site
00 fffff880`1d6174b8 fffff803`25ee2569 nt!KeBugCheckEx
01 fffff880`1d6174c0 fffff803`25ee2890 nt!KiBugCheckDispatch+0x69
02 fffff880`1d617600 fffff803`25ee1af4 nt!KiFastFailDispatch+0xd0
03 fffff880`1d6177e0 fffff803`25f42c99 nt!KiRaiseSecurityCheckFailure+0xf4
04 fffff880`1d617970 fffff880`01b12e60 nt!ExInitializeResourceLite+0x108
05 fffff880`1d6179a0 fffff880`01bea1dc Ntfs!NtfsAllocateNonpagedFcb+0x54
06 fffff880`1d6179d0 fffff880`01c0334d Ntfs!NtfsCreateFcb+0x2ec
07 fffff880`1d617ad0 fffff880`01bd2e4d Ntfs!NtfsOpenFile+0x1dd
08 fffff880`1d617d00 fffff880`01be496d Ntfs!NtfsCommonCreate+0x1114
09 fffff880`1d617f50 fffff803`25edd8e7 Ntfs!NtfsCommonCreateCallout+0x1d
0a fffff880`1d617f80 fffff803`25edd8ad nt!KxSwitchKernelStackCallout+0x27
0b fffff880`1c638110 00000000`00000000 nt!KiSwitchKernelStackContinue

2: kd> .exr 0xfffff8801d617738ExceptionAddress: fffff80325f42c99 (nt!ExInitializeResourceLite+0x0000000000000108)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

There isn't much in this dump file that is particularly helpful.
The exception appears to be raised from the disk subsystem, when the resource was passed as an argument by it.
So at the moment, my guess is that:
A. The actual resource was corrupt.
B. The pointer was wrong and tried to modify a different resource.

In this scenario, I'm leaning towards A.