Can someone please help!
I've been trying to fix this problem for the past week, I've called HP (the manufacturer of my laptop) and they will only assist me if I purchase one of their phone support plans.
These are the Crash Dumps I got (I'll type out the relevant information since I do not have the notepad document and can't log onto the OS):
ntkrnlpa.exe
Minidump File: C:\Windows\Minidump\Mini05908-01.dmp
Driver File Name: ntkrnlpa.exe
Driver File Description: NT Kernel & System
Driver File Version: 6.0.6000.16754 (vista_gdr.080917-1612)
Crash Description: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (10000007e)
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 0x8000000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG.
Arguments:
Arg1:c0000005, The exception code that was not handled
Arg2: 81ce892e, The address that the exception occurred at
Arg3: 881ccb78, Exception Record Address
Arg4: 881cc874, Context Record Adress
csrss.exe
Minidump File: C:\Windows\Minidump\Mini112507-01.dmp
Driver File Name: csrss.exe
Driver File Description: Client Server Runtime Process
Driver File Version: 6.0.60000.16386 (vista_rtm.061101-2205)
Crash Description: CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been terminated.
Several processes and threads are necessary for the opetaion of the system; when they are terminated (for any reason), the system can no longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 86df97c0, Terminating object
Arg3: 86df990c, Process image file name
Arg4: 81aaa540, Explanatory message (ascii)
luafv.sys
Minidump File: C:\Windows\Minidump\Mini122707-01.dmp
Driver File Name: luafv.sys
Driver File Description: LUA File Virtualization Filter Driver
Driver File Version: 6.0.6000.16386 (vista_rtm.061101-2205)
Startup Manager "Name": "UAC File Virtualization"
Registry Key Path: "HKLM\System\CurrentCrontrolSet\Services\luafv"
Crash Description: SYSTEM_THREAM_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 0x8000000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81cb5273, The address that the exception occurred at
Arg3: 881a0a28, Exception Record Address
Arg4: 881a0724, Context Record Address
someone please help I do not know what to do and how to fix this problem, I work a lot with this laptop and would love that have it working as soon as possible. If anyone would please help me in solving this I would greatly appreciate it. I ran about 6 virus scanners and cleaned out anything I found, also ran various hardware tests and all hardware passed.
I've been trying to fix this problem for the past week, I've called HP (the manufacturer of my laptop) and they will only assist me if I purchase one of their phone support plans.
These are the Crash Dumps I got (I'll type out the relevant information since I do not have the notepad document and can't log onto the OS):
ntkrnlpa.exe
Minidump File: C:\Windows\Minidump\Mini05908-01.dmp
Driver File Name: ntkrnlpa.exe
Driver File Description: NT Kernel & System
Driver File Version: 6.0.6000.16754 (vista_gdr.080917-1612)
Crash Description: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (10000007e)
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 0x8000000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG.
Arguments:
Arg1:c0000005, The exception code that was not handled
Arg2: 81ce892e, The address that the exception occurred at
Arg3: 881ccb78, Exception Record Address
Arg4: 881cc874, Context Record Adress
csrss.exe
Minidump File: C:\Windows\Minidump\Mini112507-01.dmp
Driver File Name: csrss.exe
Driver File Description: Client Server Runtime Process
Driver File Version: 6.0.60000.16386 (vista_rtm.061101-2205)
Crash Description: CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been terminated.
Several processes and threads are necessary for the opetaion of the system; when they are terminated (for any reason), the system can no longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 86df97c0, Terminating object
Arg3: 86df990c, Process image file name
Arg4: 81aaa540, Explanatory message (ascii)
luafv.sys
Minidump File: C:\Windows\Minidump\Mini122707-01.dmp
Driver File Name: luafv.sys
Driver File Description: LUA File Virtualization Filter Driver
Driver File Version: 6.0.6000.16386 (vista_rtm.061101-2205)
Startup Manager "Name": "UAC File Virtualization"
Registry Key Path: "HKLM\System\CurrentCrontrolSet\Services\luafv"
Crash Description: SYSTEM_THREAM_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 0x8000000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81cb5273, The address that the exception occurred at
Arg3: 881a0a28, Exception Record Address
Arg4: 881a0724, Context Record Address
someone please help I do not know what to do and how to fix this problem, I work a lot with this laptop and would love that have it working as soon as possible. If anyone would please help me in solving this I would greatly appreciate it. I ran about 6 virus scanners and cleaned out anything I found, also ran various hardware tests and all hardware passed.