Windows 7: BSOD on Dell Vostro 1500

Jonathan_King · 02 Sep 2010

If you get more BSODs, try disabling the card in Device Manager, and just using the Wireless card.

If the BSODs stop, it's time to investigate purchasing a new Ethernet card.

mac173 · 02 Sep 2010

Oh boy, I think the ethernet is integrated. I can't use the wireless, I don't have access to any wireless networks. I use wired at home and neither work nor home are in range of Optimum WiFi.

Did the info in the two latest minidumps also relate to that driver?

Jonathan_King · 02 Sep 2010

Unfortunately, the latest dump didn't point to any useful cause:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_performance monitor(2).zip\Windows_NT6_BSOD_jcgriff2\082610-29281-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
Debug session time: Thu Aug 26 10:05:19.946 2010 (UTC - 4:00)
System Uptime: 0 days 1:07:10.006
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 0, fffff8a009974010}

GetPointerFromAddress: unable to read from fffff80002cae0e0
GetUlongFromAddress: unable to read from fffff80002c1c1b0
GetUlongFromAddress: unable to read from fffff80002c1c1b0
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+35c )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a009974010, Address of the block of pool being deallocated

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

GetUlongFromAddress: unable to read from fffff80002c1c1b0
GetUlongFromAddress: unable to read from fffff80002c1c1b0

POOL_ADDRESS:  fffff8a009974010 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ba960e to fffff80002a76740

STACK_TEXT:  
fffff880`02f9d8d8 fffff800`02ba960e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f9d8e0 fffff800`02a60a20 : fffffa80`02b19440 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x11eb
fffff880`02f9d990 fffff800`02d6760f : fffffa80`02b19440 00000000`00000011 00000000`0008c081 fffff8a0`0008c081 : nt!MiDeleteSegmentPages+0x35c
fffff880`02f9da40 fffff800`02a7b8b4 : 00000000`00000000 00000000`00000002 fffffa80`0189d7b0 fffffa80`0189d7b0 : nt!MiSegmentDelete+0x7b
fffff880`02f9da80 fffff800`02a662f0 : 00000000`00000002 fffffa80`028d7820 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`02f9dae0 fffff800`02a69d1c : fffffa80`0287e670 fffffa80`030d0330 fffffa80`0287e670 fffffa80`018aeb00 : nt!CcDeleteSharedCacheMap+0x1bc
fffff880`02f9db50 fffff800`02a6a520 : fffff880`02f9dc00 fffff880`02f9dc58 00000000`00000000 fffffa80`00000000 : nt!CcWriteBehind+0x5bc
fffff880`02f9dc00 fffff800`02a83961 : fffffa80`018af580 fffff880`0128a230 fffff800`02c7d140 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`02f9dcb0 fffff800`02d1ac06 : 00000000`00000000 fffffa80`018aeb60 00000000`00000080 fffffa80`0182f890 : nt!ExpWorkerThread+0x111
fffff880`02f9dd40 fffff800`02a54c26 : fffff880`009e7180 fffffa80`018aeb60 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f9dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDeleteSegmentPages+35c
fffff800`02a60a20 488b5b10        mov     rbx,qword ptr [rbx+10h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiDeleteSegmentPages+35c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xc2_7_nt!MiDeleteSegmentPages+35c

BUCKET_ID:  X64_0xc2_7_nt!MiDeleteSegmentPages+35c

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

mac173 · 02 Sep 2010

Thanks, I will have to "hope" for more BSOD's (what a strange thing to say....) and maybe it will point something out.

I am beginning to consider disassembling the machine to check for bad capacitors.

**cluberti** · 03 Sep 2010

You might want to consider configuring your machine for a complete dump at this point - minidumps aren't necessarily the best choice when we're actually doing some heavy-duty analysis. It'll make for large .dmp files, but at least we'll have better data in the dump itself to go on.

mac173 · 03 Sep 2010

Ok, I'm game. How do I do a complete dump? (don't tell me to take Ex Lax........)

Jonathan_King · 03 Sep 2010

Go to Advanced System Settings>Advanced tab>Startup and Recovery>Settings, and in the "Write debugging info", select "Kernel memory dump". That will create both a full dump, and minidumps.

mac173 · 03 Sep 2010

Ok, it was already set to Kernel Memory Dump. Did you mean "Complete Memory Dump"?

<Edit> There was a box marked "Overwrite existing file" which I unchecked.

Jonathan_King · 03 Sep 2010

You will want that box checked; otherwise, every time you get a BSOD, another 300MB file will be saved. That adds up quickly!

I'm not on my Windows 7 machine now, but if there is an option for a Complete Memory Dump, select it.

mac173 · 03 Sep 2010

Ok, I will do both those things. At home now, and brought the laptop with me, I will get it running after dinner and make those changes.

Windows 7: BSOD on Dell Vostro 1500

BSOD on Dell Vostro 1500 problems?