|
| | |
Group: Forum Members
Last Login: 11/13/2009 5:31:26 PM
Posts: 2, Visits: 2 |
| I am currently getting the BSOD quite often on my notebook. Most recent one says MEMORY_MANAGEMENT. Now, I've ran Windows Diag Tool in Vista and it showed 0 Errors.
I've updated all my windows updates, ran AVG Antivirus/Spyware checker and no threats found.
I Have no installed any new devices in recent weeks.
Running:
Win Vista Home Premium SP2
Dell Inspiron 1520
Intel Core 2 Duo T5250 1.5ghz
2GB Ram
Any help would be great! |
| |
| | | | 
Co-Administrator
Group: Administrators
Last Login: Today @ 5:00:13 PM
Posts: 2,767, Visits: 3,064 |
| We have some pinned posts on diagnosing Stop errors. You should read those and attempt to diagnose the particular BSOD you're getting. There is no single generic fix for BSODs.
ASUS A832nSLI-Deluxe, AMD 64X2 4400 OC 2.4GHz, 2GB OCZ,
Running: Windows 7, Vista 32-bit, Ubuntu 9.10, 9.04
 |
| |
| | | |
Group: Forum Members
Last Login: 11/13/2009 5:31:26 PM
Posts: 2, Visits: 2 |
| Alright, I have a new BSOD and have no idea on what to do. This is a notebook I am using, and running Windows Memory Diag Tool shows NO Errors. (Vista Home Prem) running 2Gigs
This is my memory dump.
Please help!
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\today.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0x81e40000 PsLoadedModuleList = 0x81f57c70
Debug session time: Fri Nov 13 19:13:39.384 2009 (GMT-4)
System Uptime: 0 days 10:12:46.246
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 82083cf3, c810abd0, c810a8cc}
Probably caused by : ntkrpamp.exe ( nt!PfpFlushBuffers+52 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 82083cf3, The address that the exception occurred at
Arg3: c810abd0, Exception Record Address
Arg4: c810a8cc, Context Record Address
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!PfpFlushBuffers+52
82083cf3 8b00 mov eax,dword ptr [eax]
EXCEPTION_RECORD: c810abd0 -- (.exr 0xffffffffc810abd0)
ExceptionAddress: 82083cf3 (nt!PfpFlushBuffers+0x00000052)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000040
Attempt to read from address 00000040
CONTEXT: c810a8cc -- (.cxr 0xffffffffc810a8cc)
eax=00000040 ebx=00000000 ecx=00000040 edx=bbabe000 esi=00000000 edi=c810acc0
eip=82083cf3 esp=c810ac98 ebp=c810ace8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!PfpFlushBuffers+0x52:
82083cf3 8b00 mov eax,dword ptr [eax] ds:0023:00000040=????????
Resetting default scope
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000040
READ_ADDRESS: GetPointerFromAddress: unable to read from 81f77868
Unable to read MiSystemVaType memory at 81f57420
00000040
FOLLOWUP_IP:
nt!PfpFlushBuffers+52
82083cf3 8b00 mov eax,dword ptr [eax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 82083c12 to 82083cf3
STACK_TEXT:
c810ace8 82083c12 00000000 bee98698 00000000 nt!PfpFlushBuffers+0x52
c810ad7c 82015c42 81f3f080 70c2664b 00000000 nt!PfTLoggingWorker+0xaa
c810adc0 81e7eefe 82083b62 81f3f080 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!PfpFlushBuffers+52
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a77feb3
STACK_COMMAND: .cxr 0xffffffffc810a8cc ; kb
FAILURE_BUCKET_ID: 0x7E_VRF_nt!PfpFlushBuffers+52
BUCKET_ID: 0x7E_VRF_nt!PfpFlushBuffers+52
Followup: MachineOwner
---------
|
| |
| |
|