BSOD sometimes, keeps rebooting

My computer started randomly rebooting and/or crashing about 2 weeks ago. Sometimes I get BSOD, sometimes my screen goes black and I loose all function till reboot. I ran the dump file scan. From what I could research it looks like a driver is causing the crash by trying to write to an invalid memory address, but I can't tell how to fix it. Can someone please help me figure out what this means?

Thanks!
Cynthia

I'm running Vista Home Premium 32bit. It is OEM on HP a6200n PC, but has been upgraded to SP2. PC is about 2 years old


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

Loading Dump File [C:\Users\Accountant\AppData\Local\Temp\WER6660.tmp\Mini071211-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 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.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x82611000 PsLoadedModuleList = 0x82728c70
Debug session time: Tue Jul 12 21:42:28.182 2011 (UTC - 7:00)
System Uptime: 0 days 2:53:53.869
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {60, 1b, 1, 826b85ce}
Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 826b85ce, address which referenced memory
Debugging Details:
------------------

USER_LCID_STR: ENU
OS_SKU: 3
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82748868
Unable to read MiSystemVaType memory at 82728420
00000060
CURRENT_IRQL: 1b
FAULTING_IP:
nt!KiUnwaitThread+d
826b85ce 095660 or dword ptr [esi+60h],edx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 82706af0 -- (.trap 0xffffffff82706af0)
ErrCode = 00000002
eax=86e18980 ebx=00000000 ecx=00000000 edx=00000100 esi=00000000 edi=b2f1b358
eip=826b85ce esp=82706b64 ebp=82706b74 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!KiUnwaitThread+0xd:
826b85ce 095660 or dword ptr [esi+60h],edx ds:0023:00000060=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 826b85ce to 8265efd9
STACK_TEXT:
82706af0 826b85ce badb0d00 00000100 8b87d3ff nt!KiTrap0E+0x2e1
82706b74 826bb055 00000000 8270e580 000000a0 nt!KiUnwaitThread+0xd
82706c88 826baeeb 82706cd0 87f8ca02 82706cd8 nt!KiTimerListExpire+0x93
82706ce8 826bb655 00000000 00000000 000a34a0 nt!KiTimerExpiration+0x22a
82706d50 826b989d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82706d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnwaitThread+d
826b85ce 095660 or dword ptr [esi+60h],edx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiUnwaitThread+d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb710d6
FAILURE_BUCKET_ID: 0xA_nt!KiUnwaitThread+d
BUCKET_ID: 0xA_nt!KiUnwaitThread+d
Followup: MachineOwner

So that we may give you the best possible help, we request that you submit the following information
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html
Dont worry about the rebooting. That is a setting that we can change. It allows you to reboot automatically after a BSOD. I would leave it for now.

I updated original post to inlcude requested files and information. Any help you can give will be greatly appreciated!

Cynthia

I will try my best. Dont worry about the reboot. Thats a safeguard to insure that the computer keeps running after a BSOD

Allow me to give a little background first. The reports that you gave me do not give a cause for the problem, they give clues. The clues that you supplied leads me to memory problems, which we shall address. Take the test, if you fail take corrective action. If you pass, I iwill examined the clues again and see what the next step should be.
Run for 8 passes. Then take a known good stick and test each slot for 8 passes
Good Luck
Guide to using Memtest86+ - Geeks to Go Forums

I ran the memory test per the instructions on the link you provided. I got no failures. I let the complete 8 passes run 2x on each memory stick. It took forever, but no failures.

Seems kind of fast but if you say you did 8, Ill go with that, but at least 4 or 5 in each slot.
You run everything for 8 passes. Then you open the computer take a good stick and test each slot for 4 passes.

I could let it run overnight, the only problem is that according to the website you need to do one stick at a time and this is a work machine so I won't be here to change sticks in the middle of the night. Is it possible there is a defective memory module that is embedded on the motherboard? Or a driver error?

If the memory passes, then the next step is the driver test.
Taking a good stick and testing each slot will test the MB. That is why it was suggested.

Because of you need for the computer, I looked it over again; especially for little clues.. If the memory test pases, uninstall Symantec. You can make a system restore point first, so that you can install again if you want. Replace with Microsoft Security Essentials; just a hunch. If it works you saved a lot of time, if not, you lost nothing. Just based on a little something that I saw.
If you still BSOD, we do a driver test. I hope that we can avoid that.