Hello BigCountry,
Here are the results of your bugcheck.
STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Hardware incompatibility, Faulty system service, Memory.
Code:
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81b77e65, a96af7ec, 0}
Unable to load image \SystemRoot\system32\DRIVERS\avgntflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
Probably caused by : avgntflt.sys ( avgntflt+f88d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 81b77e65, The address that the exception occurred at
Arg3: a96af7ec, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {b0, 2, 0, 81c0c152}
Unable to load image \SystemRoot\System32\Drivers\sonypvl2.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sonypvl2.sys
*** ERROR: Module load completed but symbols could not be loaded for sonypvl2.sys
Probably caused by : sonypvl2.sys ( sonypvl2+2228 )
Followup: MachineOwner
---------
1: 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: 000000b0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 81c0c152, address which referenced memory
Debugging Details:
This is from the last nine dump files.
As you can see there are two main causes for this.
avgntflt.sys
sonypvl2.sys
Start by un-installing your anti-virus software. (Don't for get to reinstall AV software when finished.
The other faulting driver is a Sony driver, i would go to the Sony site and download and install new Chipset drivers, Video drivers, Sound drivers, and any other drivers that you need.
Can you confirm that you have all the Vista updates, and service packs 1&2
Un-install all Cyberlink software, this caused one BSOD in the nine i checked.
Clear the CMOS, remove battery for ten minutes then refit.
Run Memtest for at least six hours/over night.
Download and run HDD diagnostic software.
Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.
Try a clean boot too.
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
These are in no particular order, so do the easy ones first.
If you need any more information or help, just ask.
I will check your other drivers later.
Hope this helps, good luck and post your results.
