Toshiba Satellite S55t-A5377 BSOD

Welcome to the forum.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb40014e630b, 0, fffff80002ab68b5, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffb40014e630b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ab68b5, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d04100
GetUlongFromAddress: unable to read from fffff80002d041c0
 fffffb40014e630b Nonpaged pool

FAULTING_IP: 
nt!MiAgeWorkingSet+52b
fffff800`02ab68b5 410fb6461b      movzx   eax,byte ptr [r14+1Bh]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  NisSrv.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003316680 -- (.trap 0xfffff88003316680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff680009fe970
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ab68b5 rsp=fffff88003316810 rbp=0000000000000000
 r8=0000000000000001  r9=fffffa8006f42ae8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!MiAgeWorkingSet+0x52b:
fffff800`02ab68b5 410fb6461b      movzx   eax,byte ptr [r14+1Bh] ds:00000000`0000001b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b4953b to fffff80002accbc0

STACK_TEXT:  
fffff880`03316518 fffff800`02b4953b : 00000000`00000050 fffffb40`014e630b 00000000`00000000 fffff880`03316680 : nt!KeBugCheckEx
fffff880`03316520 fffff800`02acacee : 00000000`00000000 fffffb40`014e630b 00000000`00001000 12904000`6f765025 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`03316680 fffff800`02ab68b5 : 00000003`00000000 12800000`72d60025 00000000`00000000 00000000`00000128 : nt!KiPageFault+0x16e
fffff880`03316810 fffff800`02b4df25 : fffffa80`06f42ae8 fffff880`00000001 00000000`00000001 fffff880`03316a70 : nt!MiAgeWorkingSet+0x52b
fffff880`033169c0 fffff800`02ab6b06 : 00000000`000069a3 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`03316a40 fffff800`02ab6fb3 : 00000000`00000008 fffff880`03316ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316a90 fffff800`02d6873a : fffffa80`036aeb50 00000000`00000080 fffffa80`0369d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316c00 fffff800`02abd8e6 : fffff880`02f65180 fffffa80`036aeb50 fffff880`02f6ffc0 e74d1ab8`593b2a48 : nt!PspSystemThreadStartup+0x5a
fffff880`03316c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+52b
fffff800`02ab68b5 410fb6461b      movzx   eax,byte ptr [r14+1Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+52b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+52b

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

Any new BSOD?

Update logs.

Well this dump is pretty straight forward.

Caused by Norton Symantec.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\PAT-Fri_11_07_2014_134002_81\110714-30373-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`034a2890
Debug session time: Fri Nov  7 21:44:28.966 2014 (UTC + 6:00)
System Uptime: 0 days 1:03:09.825
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800032ddc3f}

*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )

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

2: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800032ddc3f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
GetUlongFromAddress: unable to read from fffff8000350c1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+4f
fffff800`032ddc3f 488713          xchg    rdx,qword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  nis.exe

TRAP_FRAME:  fffff88009042f30 -- (.trap 0xfffff88009042f30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009df1b50 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88009043130 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032ddc3f rsp=fffff880090430c0 rbp=0000000000000008
 r8=fffff88009043130  r9=fffff88001b89cb0 r10=0000000000000000
r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f:
fffff800`032ddc3f 488713          xchg    rdx,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d4169 to fffff800032d4bc0

STACK_TEXT:  
fffff880`09042de8 fffff800`032d4169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09042df0 fffff800`032d2de0 : 00000000`00000010 fffff880`09043120 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09042f30 fffff800`032ddc3f : 00000000`00000003 00000000`00000002 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
fffff880`090430c0 fffff880`019889c7 : 00000000`00000008 fffff880`090433a0 00000000`00006c07 fffffa80`0c1df7c8 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f
fffff880`09043110 fffff880`01ae508d : fffffa80`0d7b4af0 fffffa80`0c1e1940 fffff880`090433a0 00000000`00006c07 : NETIO!WfpExpireEntryLru+0x17
fffff880`09043160 fffff880`01aac7b7 : 00000000`00000004 fffff8a0`075b0030 fffff880`090433d0 fffffa80`00000001 : tcpip!WfpAleCloseRemoteEndpointConnection+0x2d
fffff880`09043190 fffff880`01b24e5b : fffffa80`0d7b4af0 fffffa80`0d96b70a 00000000`00000001 fffffa80`0d7b4af0 : tcpip! ?? ::FNODOBFM::`string'+0x20f72
fffff880`090432e0 fffff880`01b251e2 : 0000076c`00000000 fffffa80`0d96b640 fffffa80`06e19c20 00000000`00000001 : tcpip!WfpAleHandleSendCompletion+0xeb
fffff880`09043400 fffff880`01b2f6b2 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0702c4c8 : tcpip!WfpAlepAuthorizeSendCompletion+0x32
fffff880`09043450 fffff880`01805af2 : 00000000`0000cbdd 00000000`0000076c fffffa80`0cc42440 00000000`00000001 : tcpip!WfpAleCompleteOperation+0x162
fffff880`090434f0 fffff880`0d0887bb : 00000000`00000000 00000000`00000000 fffffa80`0cf759a0 00000000`00000030 : fwpkclnt!FwpsCompleteOperation0+0x1e
fffff880`09043520 00000000`00000000 : 00000000`00000000 fffffa80`0cf759a0 00000000`00000030 00000000`0000cbdd : SYMNETS+0x1e7bb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!WfpExpireEntryLru+17
fffff880`019889c7 488b4310        mov     rax,qword ptr [rbx+10h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!WfpExpireEntryLru+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5294760d

FAILURE_BUCKET_ID:  X64_0xA_NETIO!WfpExpireEntryLru+17

BUCKET_ID:  X64_0xA_NETIO!WfpExpireEntryLru+17

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

Remove Norton from the system and replace with MSE.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Perform a Clean boot:

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Good news. :)

Post if you have any other problems.