Win 7 Home Premiumx64: NO MORE IRP STACK LOCATIONS

[sevenwired]

Hello All,

In just the last month, my Sony Vaio laptop has crashed with the exact same error : NO MORE IRP STACK LOCATIONS

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	4105

Additional information about the problem:
  BCCode:	35
  BCP1:	FFFFFA800B5A07D0
  BCP2:	0000000000000000
  BCP3:	0000000000000000
  BCP4:	0000000000000000
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	768_1

Unfortunately, the information above is from a crash that occurred on May 9. I say "unfortunately" as I would like to have captured today's crash details. I'm 99% sure it's the same, as the message is identical to the BSOD screen I had then (I have attached an image: 2011-06-11 15.19.26.jpg)

I've also attached all my dmp files from that date (3 of them in a zipped archive) and I'm hoping someone can provide some insight into what's causing this issue.

I've also included a text file (BSOD_May9.txt) that contains the full Problem Signature and additional details.

As for my system, here's what I'm using:
Sony Vaio VPCCW23FD
Win 7 Home Premium 64 bit, SP 1
4 GB RAM

av: Avast! Free
Spyware: Webroot Spy Sweeper v6.x

I also have MalwareBytes and Spybot S&D, but these are not running in the background.

The only thing I can imagine is that I upgraded my SQL Server from 2005 to 2008, which was incredibly difficult (don't remember the error), but I had to modify a few registry settings that I had found online.

Would the dump files indicate where the problem might lie?

Any help would be much appreciated.

Cheers!

 

[zigzag3143]

Hello All,

In just the last month, my Sony Vaio laptop has crashed with the exact same error : NO MORE IRP STACK LOCATIONS

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    4105

Additional information about the problem:
  BCCode:    35
  BCP1:    FFFFFA800B5A07D0
  BCP2:    0000000000000000
  BCP3:    0000000000000000
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Unfortunately, the information above is from a crash that occurred on May 9. I say "unfortunately" as I would like to have captured today's crash details. I'm 99% sure it's the same, as the message is identical to the BSOD screen I had then (I have attached an image: 2011-06-11 15.19.26.jpg)

I've also attached all my dmp files from that date (3 of them in a zipped archive) and I'm hoping someone can provide some insight into what's causing this issue.

I've also included a text file (BSOD_May9.txt) that contains the full Problem Signature and additional details.

As for my system, here's what I'm using:
Sony Vaio VPCCW23FD
Win 7 Home Premium 64 bit, SP 1
4 GB RAM

av: Avast! Free
Spyware: Webroot Spy Sweeper v6.x

I also have MalwareBytes and Spybot S&D, but these are not running in the background.

The only thing I can imagine is that I upgraded my SQL Server from 2005 to 2008, which was incredibly difficult (don't remember the error), but I had to modify a few registry settings that I had found online.

Would the dump files indicate where the problem might lie?

Any help would be much appreciated.

Cheers!

ALl of these were related to srv2.sys (smb 2.0 server driver). I would remove or disable to test. I would also remove Avast and replace with Microsoft security essentials

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials

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


Loading Dump File [C:\Users\K\Desktop\061111-46285-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ace90
Debug session time: Sat Jun 11 15:18:22.446 2011 (GMT-4)
System Uptime: 5 days 16:16:57.960
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 35, {fffffa80040cd4f0, 0, 0, 0}

Probably caused by : srv2.sys ( srv2!StartIoAndWait+32 )

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

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

NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it.  This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet.  This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: fffffa80040cd4f0, Address of the IRP
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x35

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030e7632 to fffff800030e7640

STACK_TEXT:  
fffff880`0ca60a28 fffff800`030e7632 : 00000000`00000035 fffffa80`040cd4f0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ca60a30 fffff800`03090057 : 00000000`00000000 fffff8a0`1623f0d0 fffffa80`08c91a78 00000000`01dfe243 : nt!KiBugCheck3+0x12
fffff880`0ca60a60 fffff880`09982132 : fffff880`0ca60b08 fffff880`0ca60b18 fffff880`0ca60b08 fffffa80`0a3f7850 : nt! ?? ::FNODOBFM::`string'+0x42a8b
fffff880`0ca60a90 fffff880`09985ac1 : ffffffff`80009c64 00000000`00530050 fffff880`0ca60b88 fffff880`0996d348 : srv2!StartIoAndWait+0x32
fffff880`0ca60ad0 fffff880`09986e95 : fffff880`0ca60bf0 fffff880`0ca60c80 00000000`00000000 fffff8a0`03546020 : srv2!SrvSnapIssueIoctl+0xa1
fffff880`0ca60b40 fffff880`09987c20 : fffffa80`08c91a78 fffffa80`0a0abb00 fffff880`00000004 fffffa80`08c91a78 : srv2!SrvShareGetEpicForVolume+0x25
fffff880`0ca60b70 fffff880`09987e8d : fffffa80`03cb2ce0 00000000`00000000 fffffa80`0a0abbd0 fffff880`09967a44 : srv2!SrvShareRefreshSnapShots+0x70
fffff880`0ca60bf0 fffff880`0997e569 : fffffa80`03cb2ce0 fffff880`09960110 fffffa80`087bf5a0 fffffa80`08c91a00 : srv2!SrvShareEnumerateSnapShots+0x4d
fffff880`0ca60c30 fffff880`099675d0 : fffffa80`00000010 fffffa80`087bf5a0 fffff880`09960110 fffff880`09960110 : srv2! ?? ::NNGAKEGL::`string'+0xbead
fffff880`0ca60c80 fffff880`0996723a : 00000000`00000008 fffffa80`08c91a00 fffffa80`08c91a00 fffffa80`03cb2a40 : srv2!SrvProcessPacket+0xa0
fffff880`0ca60cc0 fffff800`03384cce : 00000000`00000000 fffffa80`0a12c4b0 00000000`00000080 fffffa80`0390c040 : srv2!SrvProcWorkerThread+0x15a
fffff880`0ca60d40 fffff800`030d8fe6 : fffff880`009e8180 fffffa80`0a12c4b0 fffffa80`03a43420 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0ca60d80 00000000`00000000 : fffff880`0ca61000 fffff880`0ca5b000 fffff880`0ca609b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
srv2!StartIoAndWait+32
fffff880`09982132 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  srv2!StartIoAndWait+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: srv2

IMAGE_NAME:  srv2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7948f

FAILURE_BUCKET_ID:  X64_0x35_srv2!StartIoAndWait+32

BUCKET_ID:  X64_0x35_srv2!StartIoAndWait+32

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