Computer is off in the morning

For the last few days my computer has shut down overnight. I haven't installed any new software. ]

I get this error upon booting in the morning:

"windows has recovered from an unexpected shutdown."
Program signature: Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Additional Information about the problem: BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800AB3AA10
BCP3: FFFFF80000B9C518
BCP4: FFFFFA800F31B440
OS Version:6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
c:\Windows\Minidump\032711-55208-01.dmp
C:\Users\Paul\AppData\Local\Temp\WER-78671-0.sysdata.xml

I cannot find the two files listed above on my system.

Attached is a HiJack This file.

Any help would be greatly appreciated.

 

Was unable to edit my original question due to a 10 min. limit on revisions.
Wanted top include my system data:

Dell XPS9100
Windows 7
Service Pack 1
12GB RAM
64-bit
Intel(R) Core(TM) i7 CPU \960@3.20GHz 3.2-GHz

 

Greetings, yahnis.

Please perform the following: copy the C:\Windows\Minidump\032711-55208-01.dmp to your Desktop, then zip it (right-click it > send to > compressed folder) - attach that .zip file to your next reply, and one of the gurus here may be able to help you.

 

Thank you for that info. I've attached the C:\Windows\Minidump\032711-55208-01.dmp file to this reply.

 

This is another minidump file that occurred this morning.

 

I hope you're not going to be too disappointed, guru I'm not just trying to help out in a difficult area.

Code:

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800ab1b060, Physical Device Object of the stack
Arg3: fffff80004ad7518, Functional Device Object of the stack
Arg4: fffffa800eb80c10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000fb4000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`04ad74c8 fffff800`02f05b52 : 00000000`0000009f 00000000`00000003 fffffa80`0ab1b060 fffff800`04ad7518 : nt!KeBugCheckEx
fffff800`04ad74d0 fffff800`02ea5062 : fffff800`04ad7600 fffff800`04ad7600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`04ad7570 fffff800`02ea4f06 : fffff800`03041740 00000000`0014be2b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`04ad75e0 fffff800`02ea4dee : 00000031`6041077d fffff800`04ad7c58 00000000`0014be2b fffff800`0300e7e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04ad7c30 fffff800`02ea4bd7 : 0000000f`6e2e69c1 0000000f`0014be2b 0000000f`6e2e6932 00000000`0000002b : nt!KiTimerExpiration+0x1be
fffff800`04ad7cd0 fffff800`02e9136a : fffff800`0300be80 fffff800`03019cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04ad7d80 00000000`00000000 : fffff800`04ad8000 fffff800`04ad2000 fffff800`04ad7d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

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

Code:

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82905f9c, The address that the exception occurred at
Arg3: a28c2c40, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
nt!MiGetNextNode+b
82905f9c 394804          cmp     dword ptr [eax+4],ecx

TRAP_FRAME:  a28c2c40 -- (.trap 0xffffffffa28c2c40)
ErrCode = 00000000
eax=00000000 ebx=894e6a50 ecx=85629748 edx=00000000 esi=89cdded0 edi=0573eab4
eip=82905f9c esp=a28c2cb4 ebp=a28c2d44 iopl=0         nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010217
nt!MiGetNextNode+0xb:
82905f9c 394804          cmp     dword ptr [eax+4],ecx ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SearchProtocolH

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82a51cf4 to 82905f9c

STACK_TEXT:  
a28c2cb0 82a51cf4 e0d7b7c7 00000834 0573ea90 nt!MiGetNextNode+0xb
a28c2d44 8289ac7a 00000834 02b20000 00000000 nt!NtQueryVirtualMemory+0x2f8
a28c2d44 77345ca4 00000834 02b20000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0573ea90 00000000 00000000 00000000 00000000 0x77345ca4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetNextNode+b
82905f9c 394804          cmp     dword ptr [eax+4],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiGetNextNode+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb710d6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x8E_nt!MiGetNextNode+b

BUCKET_ID:  0x8E_nt!MiGetNextNode+b

Followup: MachineOwner

The upper analysis, which is the latest BSOD, seems to point to the Realtek NDIS networking driver, try downloading and installing the latest version. I think it's this one. The lower analysis points to what's normally a software bug, it could well be the same issue.

 

Thanks for info. I went to the Reakltek site but it was not apparent to me which driver would be the appropriate one. I don't know which of the three displayed drivers is the correct one for me.

I tried to find my type of network adapter by looking in the device manager where the network driver is listed as: Realtek PCIe GBE Family Controller.
Hmn, no help there--the driver details didn't provide any clues that I could match to the available drivers at the Realtek site.

I did see the nb-driver-M1005-LAN-7.27.920.2010.zip driver on the site you suggested but it wanted me to download using RadarSync PC Updater....and I don't want an "updater" to contend with right in the middle of troubleshooting...

Not sure what to do next - I'm still researching leans Googling this and that, hoping you or someone may have more clues for me to pursue!

 

Hi, you can wait for satrow to clarify but I think he is linking to the driver below.

I think it is this version 7.041 (Driver_Win7_7041_03212011.zip) from that link [Go has a box around it in the screenshot]. Or you could try the auto-installation version below it.

It seems to match up with the driver from Dell only a slightly higher revision/version number.

 

Check That's the driver I'd use but the auto-installer will be easier for some people.

It's pretty rare for the likes of Dell to actually keep their drivers updated to within 4-6 months of the better, bugfixed versions available from Intel, Realtek, etc.

 

OK, I'm going to go for it!
I'll let you and satrow know how it goes!