View Single Post
05 Jan 2013  
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0e40b8900, 0, fffff88009756020, 5}

*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS

Could not read faulting driver name
Probably caused by : SRTSP64.SYS ( SRTSP64+8e020 )

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

4: 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: fffff8a0e40b8900, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88009756020, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f05100
GetUlongFromAddress: unable to read from fffff80002f051c0
 fffff8a0e40b8900 Paged pool

FAULTING_IP: 
SRTSP64+8e020
fffff880`09756020 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a71e020 -- (.trap 0xfffff8800a71e020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a009be3060
rdx=0554518c2edda8be rsi=0000000000000000 rdi=0000000000000000
rip=fffff88009756020 rsp=fffff8800a71e1b0 rbp=fffff8800a71e250
 r8=fffff8a0044bc7d0  r9=0000000000000100 r10=0000000000000000
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
SRTSP64+0x8e020:
fffff880`09756020 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7c8af to fffff80002cd5fc0

STACK_TEXT:  
fffff880`0a71deb8 fffff800`02c7c8af : 00000000`00000050 fffff8a0`e40b8900 00000000`00000000 fffff880`0a71e020 : nt!KeBugCheckEx
fffff880`0a71dec0 fffff800`02cd40ee : 00000000`00000000 fffff8a0`e40b8900 00000000`00000000 fffff8a0`e40b88f0 : nt! ?? ::FNODOBFM::`string'+0x437c1
fffff880`0a71e020 fffff880`09756020 : fffffa80`1648dc10 00000000`00000000 00000000`00000002 fffff8a0`287af5b0 : nt!KiPageFault+0x16e
fffff880`0a71e1b0 fffffa80`1648dc10 : 00000000`00000000 00000000`00000002 fffff8a0`287af5b0 fffff8a0`02c340e0 : SRTSP64+0x8e020
fffff880`0a71e1b8 00000000`00000000 : 00000000`00000002 fffff8a0`287af5b0 fffff8a0`02c340e0 fffff880`0973a063 : 0xfffffa80`1648dc10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SRTSP64+8e020
fffff880`09756020 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  SRTSP64+8e020

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SRTSP64

IMAGE_NAME:  SRTSP64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  506b70fa

FAILURE_BUCKET_ID:  X64_0x50_SRTSP64+8e020

BUCKET_ID:  X64_0x50_SRTSP64+8e020

Followup: MachineOwner
---------
Hmm. It seems Norton is there again. But we'll have to rule out one more thing:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
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   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

If RAM test comes out clean and doubts remain at Norton, you can get in touch with the Norton Community - Norton Community. Probably their new version will not be having these issues.

Anyway, good luck and let us know how it goes.
My System SpecsSystem Spec