Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Several BSODs with Different Stop Messages


10 Nov 2011   #1

Win 7 Home 64
 
 
Several BSODs with Different Stop Messages

Newly built computer, I'll update my specs in the profile shortly (done).
Probably crashed 5 or 6 times.

Crashed while gaming, crashed while not gaming, crashed while I was at the store.
Could possibly blame xSplit for the crashes, as I can't remember if it's crashed while it isn't running.
Different errors each time: DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA (x2), UNEXPECTED_KERNEL_MODE_TRAP, KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT.

I removed one stick of RAM recently to test if it was bad, even though memory test didn't show any issues. All the crashes so far have been with both sticks.

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
x64 - the original installed OS on the system? I installed it, newly built computer.
- an OEM or full retail version? It's an OEM version from one of my Dell computers.
- OEM = came pre-installed on system

- Full Retail = you purchased it from retailer

- What is the age of system (hardware)?
A few days, it's newly built.
- What is the age of OS installation
(have you re-installed the OS?) A few days.

-

Edit: One dump didn't get included. It was at C:\Windows\MEMORY.DMP. It's roughly 500MB in size. Here is the results of running a WinDBG on it:

Quote:
0: kd> !analyze -v
Unable to get program counter
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e8df83, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007f8eb90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Page 9586dc3 too large to be in the dump file.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+0
3a06:df83 ?? ???

CONTEXT: fffff88007f8eb90 -- (.cxr 0xfffff88007f8eb90)
rax=0000000000000002 rbx=0000000000000000 rcx=23cf5fe230f80000
rdx=0000000000000100 rsi=0000000000000000 rdi=fffff9802330ee10
rip=fffff80002e8df83 rsp=fffff88007f8f570 rbp=00000000a000000c
r8=fffff880009ea180 r9=fffff880009ea180 r10=0000000000000100
r11=0000000000000000 r12=00000000a0000003 r13=0000000000000000
r14=0000000000000000 r15=fffff9802330eed0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
fffff800`02e8df83 0000 add byte ptr [rax],al ds:002b:00000000`00000002=??
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

UNALIGNED_STACK_POINTER: 010101013acc39ee

LAST_CONTROL_TRANSFER: from fffffa80084e7900 to fffff80002e8df83

STACK_TEXT:
01010101`3acc39ee 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1010101`3a103bc9


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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



My System SpecsSystem Spec
.

10 Nov 2011   #2

Windows 7 Professional x64
 
 

Hi there,

It seems there may be multiple issues going on. The first is a hardware problem, as suggested by some of the dumps and by your report on the crashes being with only both RAM sticks.

The second is a simple driver issue. Install the latest Realtek ethernet drivers from here: Realtek

Code:
Rt64win7.sys  Wed Jan 26 08:34:03 2011 (4D4022CB)
Continue testing with only one stick of RAM installed. You might also run Prime95 on both sticks at the same time: Hardware - Stress Test With Prime95

Note: Prime95 passing the sticks does not prove that they are good. False negatives are common, but any positive (error) should be treated seriously.

...Summary of the dumps:
Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 22:00:19.630 2011 (UTC - 5:00)
System Uptime: 0 days 0:37:36.474
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+159a3 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_Rt64win7+159a3
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 22:37:32.248 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:25.091
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+330bc )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  XSplit.Core.ex
FAILURE_BUCKET_ID:  X64_0x1a_403_VRF_nt!_??_::FNODOBFM::_string_+330bc
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 19:02:20.751 2011 (UTC - 5:00)
System Uptime: 0 days 0:12:31.203
Probably caused by : fltmgr.sys ( fltmgr!FltpMoveIrpToCallbackData+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_fltmgr!FltpMoveIrpToCallbackData+17
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 04:00:47.418 2011 (UTC - 5:00)
System Uptime: 0 days 13:27:20.496
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for NETIO.SYS - 
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : NETIO.SYS ( NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+3e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+3e
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 18:23:26.044 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:22.121
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+56dcd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+56dcd
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 21:07:54.304 2011 (UTC - 5:00)
System Uptime: 0 days 1:19:44.662
Probably caused by : ndis.sys ( ndis!ndisParseReceivedNBL+da )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_ndis!ndisParseReceivedNBL+da
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
10 Nov 2011   #3

Win 7 Home 64
 
 

Hi,

Thanks for your response.
In trying to diagnose this issue myself, I did notice the Realtek LAN drivers already and updated them yesterday.
I've crashed since then (the MEMORY.DMP instance), but only once.

I ran Prime95 with just the one stick a couple of minutes ago for about 5-10 minutes with no issue. I'll restart and put the other stick in and give it a go again.

edit: Running the test now. I'll leave it on a while.
My System SpecsSystem Spec
.


10 Nov 2011   #4

Win 7 Home 64
 
 

Been running for an hour now. No issues, no crashing, and temperatures are stable.
That's with both sticks of RAM.
My System SpecsSystem Spec
10 Nov 2011   #5

Win 7 Home 64
 
 

Two hours. My movie is over, still no issues and still running on all four cores.
Any thoughts?

edit: I'm going to run and grab some food, but I'm going to load up xSplit while I'm gone.
I don't recall it crashing without xSplit. I also installed it on the 8th and started streaming a game for the first time that night. I also crashed for the first time that night. Could that be the cause?
My System SpecsSystem Spec
10 Nov 2011   #6

Win 7 Home 64
 
 

Stopped xSplit now.
Still no crashes.
My System SpecsSystem Spec
10 Nov 2011   #7

Win 7 Home 64
 
 

Any more suggestions on what I could do?
My System SpecsSystem Spec
11 Nov 2011   #8

Win 7 Home 64
 
 

No crashes at all tonight.
Both sticks of RAM. Played some Skyrim, streamed it too.

Also Prime95 for about 4.5 hours with no errors reported.
My System SpecsSystem Spec
11 Nov 2011   #9

Windows 7 Professional x64
 
 

It's possible that one of the sticks wasn't seated properly, and removing it and reinstalling it did some good.

Without crashes, there is nothing else we can do. Just keep an eye on the system, and if you get another crash, post back and we'll go from there.
My System SpecsSystem Spec
14 Nov 2011   #10

Win 7 Home 64
 
 

New crash. Seems to be referencing the same driver again, even though I already updated it.
I'll double check it, but let me know what you think.

Here is the WinDBG:

Quote:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880069c2470, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
+56ab952f033ddcc0
fffff880`069c2470 98 cwde

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880069c3398 -- (.exr 0xfffff880069c3398)
ExceptionAddress: fffff88001706fd3 (tcpip!TcpTcbFastDatagram+0x0000000000000483)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff880069c3440 -- (.trap 0xfffff880069c3440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=00000000000006aa
rdx=000000000004431a rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001706fd3 rsp=fffff880069c35d0 rbp=fffff880069c3870
r8=fffffa8009a9ecf0 r9=0000000000600000 r10=00000000000006aa
r11=0000000000059fbd r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
tcpip!TcpTcbFastDatagram+0x483:
fffff880`01706fd3 0f8501030000 jne tcpip!TcpTcbFastDatagram+0x78a (fffff880`017072da) [br=1]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002f164fb to fffff80002e8ac40

FAILED_INSTRUCTION_ADDRESS:
+56ab952f033ddcc0
fffff880`069c2470 98 cwde

STACK_TEXT:
fffff880`069c35d0 fffff880`017078b5 : 00000000`80000000 fffff800`033224a3 00000000`00000000 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x483
fffff880`069c3790 fffff880`0170667a : fffffa80`08223900 fffff880`016feb00 fffffa80`081ef101 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5
fffff880`069c3940 fffff880`017082ab : fffff880`04ceaea2 fffffa80`08342000 00000000`00000000 fffff880`0fcc3000 : tcpip!TcpMatchReceive+0x1fa
fffff880`069c3a90 fffff880`016ff1c7 : fffffa80`08223900 fffffa80`08220830 fffffa80`000096c6 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`069c3b60 fffff880`016fed3a : 00000000`00000000 fffff880`0181e9a0 fffff880`069c3d20 00001f80`00000200 : tcpip!IppDeliverListToProtocol+0x97
fffff880`069c3c20 fffff880`016fe339 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`069c3d10 : tcpip!IppProcessDeliverList+0x5a
fffff880`069c3cc0 fffff880`016fc0af : 00000000`00000000 fffffa80`08342000 fffff880`0181e9a0 00000000`0817a001 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`069c3da0 fffff880`016fb6a2 : fffffa80`087b7f70 00000000`00000000 fffffa80`0817a001 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`069c3fa0 fffff880`016fab3a : fffffa80`0817a010 fffff880`069c40d0 fffffa80`0817a010 fffff8a0`082e0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`069c4080 fffff800`02e97618 : fffff980`05b40e20 00000000`00004800 fffffa80`09ac9970 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`069c40d0 fffff880`016fb202 : fffff880`016faa60 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`069c41b0 fffff880`015170eb : fffff980`0a1ee8d0 00000000`00000000 fffffa80`087581a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`069c4220 fffff880`014e0ad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`069c4290 fffff880`01459cc1 : fffffa80`087581a0 00000000`00000002 00000000`00000001 00000000`00000001 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`069c4710 fffff880`03f34ce8 : fffffa80`087ce000 00000000`00000001 fffffa80`087ce618 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`069c4760 fffffa80`087ce000 : 00000000`00000001 fffffa80`087ce618 00000000`00000000 00000000`00000001 : Rt64win7+0x16ce8
fffff880`069c4768 00000000`00000001 : fffffa80`087ce618 00000000`00000000 00000000`00000001 fffff800`02e729cb : 0xfffffa80`087ce000
fffff880`069c4770 fffffa80`087ce618 : 00000000`00000000 00000000`00000001 fffff800`02e729cb 00000001`069c8000 : 0x1
fffff880`069c4778 00000000`00000000 : 00000000`00000001 fffff800`02e729cb 00000001`069c8000 ffff0000`00000001 : 0xfffffa80`087ce618


STACK_COMMAND: .trap 0xfffff880069c3440 ; kb

FOLLOWUP_IP:
Rt64win7+16ce8
fffff880`03f34ce8 ?? ???

SYMBOL_STACK_INDEX: f

SYMBOL_NAME: Rt64win7+16ce8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME: Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e53b15d

FAILURE_BUCKET_ID: X64_0x1E_VRF_BAD_IP_Rt64win7+16ce8

BUCKET_ID: X64_0x1E_VRF_BAD_IP_Rt64win7+16ce8

Followup: MachineOwner
My System SpecsSystem Spec
Reply

 Several BSODs with Different Stop Messages




Thread Tools



Similar help and support threads for2: Several BSODs with Different Stop Messages
Thread Forum
Constant BSODs, different error messages, win32.sys problem? BSOD Help and Support
Multiple crashes and BSODs with random messages and filenames in them. BSOD Help and Support
Random BSODs, multiple error messages, no clear cause BSOD Help and Support
Seemingly random BSODs, lots of different error messages BSOD Help and Support
BSODs with different error messages, problem recurring! BSOD Help and Support
BSODs while playing games, multiple different messages BSOD Help and Support
Repeating BSODS, different messages BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 11:26 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33