Minidump + blue screen + shut down error

dear wise man and woman of the computerworld.

I am having unexpected shut downs and a blue screen error report after reboot.
mostly after watching a video or a movie on vlc player. so i suspect it has to do with the driver for my display adapter which is a :NVIDIA GeForce 7150M / nForce 630M. So I updated to the latest version directly from the NVIDIA website as the Windows update doesnt find this update as the latest version. but still no luck, as the laptop shuts down unexpected.

I am running Vista home premium on a HP Pavillion dv9815nr.

I hope there is anybody out there who is willing to help me. I really appreciate the time you spend to look into this.

attached is the blue screen error message and the whole dump file. i know

thank you soo much in advance

Simon

the message I get after the reboot is following:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 00000006
BCP2: 00000002
BCP3: 00000000
BCP4: 8370F706
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini061009-04.dmp
C:\Users\Simon\AppData\Local\Temp\WER-90761-0.sysdata.xml
C:\Users\Simon\AppData\Local\Temp\WER24AF.tmp.version.txt


DUMP FILE:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini061009-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x8283d000 PsLoadedModuleList = 0x82954c70
Debug session time: Wed Jun 10 23:38:18.562 2009 (GMT-5)
System Uptime: 0 days 1:34:16.231
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\drivers\TotRec7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TotRec7.sys
*** ERROR: Module load completed but symbols could not be loaded for TotRec7.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6, 2, 0, 8370f706}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : TotRec7.sys ( TotRec7+3706 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000006, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8370f706, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: TotRec7

FAULTING_MODULE: 8283d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4800819e

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000006

CURRENT_IRQL: 0

FAULTING_IP:
TotRec7+3706
8370f706 ?? ???

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 8370f706 to 8288afb9

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8039dd10 8370f706 badb0d00 8371c004 00000000 nt+0x4dfb9
8039dd90 8370fc50 88eedff8 88eede40 85eda901 TotRec7+0x3706
8039dde4 83712695 8039de34 88eede40 8371c15c TotRec7+0x3c50
8039ddf8 837128d8 8039def0 8371c150 8039df28 TotRec7+0x6695
8039de08 828e72eb 88eedfb0 88eede40 71476aa3 TotRec7+0x68d8
8039df28 828e6eab 8039df70 82935902 8039df78 nt+0xaa2eb
8039df88 828e7615 00000000 00000000 00058850 nt+0xa9eab
8039dff4 828e52d5 ab826a44 00000000 00000000 nt+0xaa615
8039dff8 ab826a44 00000000 00000000 00000000 nt+0xa82d5
828e52d5 00000000 00000000 00000000 00000000 0xab826a44


STACK_COMMAND: kb

FOLLOWUP_IP:
TotRec7+3706
8370f706 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: TotRec7+3706

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: TotRec7.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

How old is your laptop? When was the last time you formatted your laptop? I basically format and reinstall OS in every 7-8 months time period for its smooth functioning, so consider installing OS freshly.

The Laptop is 1 year old and I just had it reformatted 1.5 month ago! and until now it worked. thanks for the tip.
is there somebody who can help me with the error and dump file report?