Hello,
I am having trouble with random BSODs, the system will lock up unexpectedly (sometime while surfing the web and sometimes while nobody is using the system). I have opened the .dmp files and noticed all seem to point to ntoskrnl.exe. I do not know what this is or why it is causing problems. My system data is correct in my profile and I have attached a .zip file of the minidumps. Can someone please help me with this issue?
Thanks in advance!
Hi and welocome
Well I just took a quick look at the last 2 dumps. There are 2 probable causes. First Memory
Second cirrupt system files
Ok I would download ans run memtestx86 for hours (prefereably overnight)
I would alswo run a system file check to verify and repair any system files that are not right
It is going to take me a while to run the rest of those dumps so I suggest you not wait for the results
Hope this helps
Ken J+
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\111009-25116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02862000 PsLoadedModuleList = 0xfffff800`02a9fe50
Debug session time: Tue Nov 10 10:37:20.924 2009 (GMT-5)
System Uptime: 0 days 10:57:46.968
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa800260d000, fffffa800260d600, 4600000}
GetPointerFromAddress: unable to read from fffff80002b0a0e0
Probably caused by : memory_corruption ( nt!MiSegmentDelete+b1 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800260d000, The pool entry we were looking for within the page.
Arg3: fffffa800260d600, The next pool entry.
Arg4: 0000000004600000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa800260d000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002a056d3 to fffff800028d3f00
STACK_TEXT:
fffff880`02fffb08 fffff800`02a056d3 : 00000000`00000019 00000000`00000020 fffffa80`0260d000 fffffa80`0260d600 : nt!KeBugCheckEx
fffff880`02fffb10 fffff800`02bc1f49 : 00000000`00000001 00000000`0008c081 fffffa80`61436d4d fffffa80`0008c081 : nt!ExFreePool+0xda4
fffff880`02fffbc0 fffff800`029f9f6b : fffffa80`0260d018 00000000`00000001 00000000`00000000 001d0001`00000631 : nt!MiSegmentDelete+0xb1
fffff880`02fffc00 fffff800`029fa5dd : 00000000`00000000 00000000`00000080 fffffa80`02334990 00000001`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`02fffcc0 fffff800`02b77166 : 001d0001`00000000 526d6574`7379535c 74737973`5c746f6f 4952445c`32336d65 : nt!MiDereferenceSegmentThread+0x10d
fffff880`02fffd40 fffff800`028b2486 : fffff800`02a4ce80 fffffa80`02352040 fffff800`02a5ac40 00000000`c2526000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fffd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiSegmentDelete+b1
fffff800`02bc1f49 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiSegmentDelete+b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x19_20_nt!MiSegmentDelete+b1
BUCKET_ID: X64_0x19_20_nt!MiSegmentDelete+b1
Followup: MachineOwner
---------
Zigzag,
Thanks for the welcome and suggestions. I ran memtestx86 v3.5 overnight (about 9 hours completed just over 6 pases). No errors were found.
I also ran "sfc /scannow" from windows cmd run as administrator. Again no errors were found.
If you have any other suggestions I can try I would appreciate it.
Thanks again!
Out of frustration with this problem last night I did a clean install of Windows 7 Professional 64 bit. Before installing I ran killdisk to completely erase the destination drive.
Last night everything seemed fine, until this morning when it blue screened while resuming from hibernate. A short while later it blue screened while resuming from sleep. I don't know if this is the same issue as before but it is just as frustrating!
I have attached the new .dmp files to this post. Please help as I am out of ideas!
Thanks,
Quote