Thanks.
Your dumps show memory corruption.
Test your ram with memtest86+ for 8 passes at least.
RAM - Test with Memtest86+
If it finds no errors, run the extended version for 5 passes.
Memory Diagnostics Tool
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 11c926, 2, 1265e5}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000011c926, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000001265e5, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Safari.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800033520cc to fffff800032cc1c0
STACK_TEXT:
fffff880`02e4a868 fffff800`033520cc : 00000000`0000004e 00000000`00000099 00000000`0011c926 00000000`00000002 : nt!KeBugCheckEx
fffff880`02e4a870 fffff800`03270220 : 00000000`00000000 fffff680`0003fb98 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`02e4a8b0 fffff800`0329bd53 : fffffa80`041304d0 fffff700`000042c6 0000007f`fffffff8 fffff8a0`042e6c38 : nt! ?? ::FNODOBFM::`string'+0x32978
fffff880`02e4a940 fffff800`0329ce22 : fffffa80`041304d0 fffffa80`00000003 fffff880`000026b7 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`02e4b1f0 fffff800`0359d6da : fffff8a0`0e103060 fffff880`02e4b530 00000000`00000000 fffffa80`07bf64a0 : nt!MmCleanProcessAddressSpace+0x96
fffff880`02e4b240 fffff800`03580bdd : 00000000`c000041d 00000000`006fc501 00000000`7ee61000 fffffa80`0767fb50 : nt!PspExitThread+0x56a
fffff880`02e4b340 fffff800`032becda : 00000000`05e5e840 fffff880`02e4b540 fffff8a0`0c5c3190 fffff800`033f7fbd : nt!PsExitSpecialApc+0x1d
fffff880`02e4b370 fffff800`032bf020 : 00000000`05e5e060 fffff880`02e4b3f0 fffff800`03580b50 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`02e4b3f0 fffff800`032cb4f7 : fffffa80`07bf64a0 00000000`7ee61000 00000000`00000020 fffffa80`06ddbbf0 : nt!KiInitiateUserApc+0x70
fffff880`02e4b530 00000000`77cd1206 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`05e5dfd0 fffff800`032c3810 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cd1206
fffff880`02e4b710 fffffa80`07bf65a8 : fffff800`032c1bd2 fffffa80`07bf64a0 fffffa80`07bf64a0 6a53f92f`a3ebdecf : nt!KiCallUserMode
fffff880`02e4b718 fffff800`032c1bd2 : fffffa80`07bf64a0 fffffa80`07bf64a0 6a53f92f`a3ebdecf fffff880`02e4bd70 : 0xfffffa80`07bf65a8
fffff880`02e4b720 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`033520cc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffff8a01834f670, fffff8a01834f7b0, 5140306}
Probably caused by : luafv.sys ( luafv!LuafvFreePool+44 )
Followup: MachineOwner
---------
0: 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: fffff8a01834f670, The pool entry we were looking for within the page.
Arg3: fffff8a01834f7b0, The next pool entry.
Arg4: 0000000005140306, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
fffff8a01834f670
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800033b7cae to fffff8000328d1c0
STACK_TEXT:
fffff880`039d2ac8 fffff800`033b7cae : 00000000`00000019 00000000`00000020 fffff8a0`1834f670 fffff8a0`1834f7b0 : nt!KeBugCheckEx
fffff880`039d2ad0 fffff880`02b136a8 : 00000000`00000000 fffff800`0342a2d8 fffffa80`6661754c 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`039d2b80 fffff880`02b0d711 : fffff8a0`1834f688 00000000`00000000 fffffa80`00000000 00000000`00000050 : luafv!LuafvFreePool+0x44
fffff880`039d2bb0 fffff880`02b0e5f1 : 01cd89e1`1850d517 fffffa80`0660dca0 fffffa80`07460600 fffff880`056e279c : luafv!LuafvDereferenceTableNodeEx+0xdd
fffff880`039d2be0 fffff880`02b009bf : fffff880`02b00901 00000000`00000000 fffffa80`00000000 01cd89e1`cb213317 : luafv!LuafvScavengeFileTable+0x211
fffff880`039d2c40 fffff800`03296841 : fffff880`02b00988 fffffa80`03d0e660 fffffa80`03d0e600 fffff800`0342a2d8 : luafv!ScavengerThread+0x37
fffff880`039d2c70 fffff800`03523e6a : 1372b3c1`3530bbb7 fffffa80`03d0e660 00000000`00000080 fffffa80`03cfb890 : nt!ExpWorkerThread+0x111
fffff880`039d2d00 fffff800`0327dec6 : fffff880`009e9180 fffffa80`03d0e660 fffff880`009f3f40 9ffb3033`257fd59b : nt!PspSystemThreadStartup+0x5a
fffff880`039d2d40 00000000`00000000 : fffff880`039d3000 fffff880`039cd000 fffff880`039d29a0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
luafv!LuafvFreePool+44
fffff880`02b136a8 eb38 jmp luafv!LuafvFreePool+0x7e (fffff880`02b136e2)
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: luafv!LuafvFreePool+44
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: luafv
IMAGE_NAME: luafv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc295
FAILURE_BUCKET_ID: X64_0x19_20_luafv!LuafvFreePool+44
BUCKET_ID: X64_0x19_20_luafv!LuafvFreePool+44
Followup: MachineOwner
Run SFC scannow and let it repair files. If it finds files to repair it will ask you to reboot.
SFC /SCANNOW Command - System File Checker
Update to the latest version of your BIOS
Your current ones are a bit old:
Code:
BIOS Version/Date Hewlett-Packard F.20, 13/10/2009
By the way what antivirus are you using? I don't see any or maybe I missed it.
I recommend MSE anyway, Microsoft Security Essentials - Free Antivirus for Windows
Post back once you've done these.
Quote