[SalientAnimal]

I am constently getting a blue screen error and have been unable to read the message to properly diagnose the problem. I have managed to locate the dmp files and hope that someone can assist me in rectifying this problem. The problem is not as a result of a single program as I have had it happen at various times and while performing various tasks and thus can not say that any particular program is to blame for it either.

I have attached my dmp files.

Thanks

Attached Files

•  minidump.zip   181.67KB   205 downloads

[Advertisements]

Are you getting this in windows or when booting up?
Please do the following:
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[rshaffer61]

Are you getting this in windows or when booting up?
Please do the following:
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[SalientAnimal]

Hi

I get the Blue screen when in Windows. This normally occurs a few minutes after I've been working in Windows, sometimes it takes as long as a few hours for the Blue Screen to appear.
Below is the info from the BSOD.txt file:

==================================================
Dump File : Mini021510-03.dmp
Crash Time : 2010/02/15 11:26:58 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x88b9f968
Parameter 2 : 0x89dd9d20
Parameter 3 : 0xb84efcbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021510-03.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021510-02.dmp
Crash Time : 2010/02/15 05:56:46 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x89075750
Parameter 2 : 0x89941e18
Parameter 3 : 0xb3bb2cbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+c9be2
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021510-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021510-01.dmp
Crash Time : 2010/02/15 04:45:53 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x89048750
Parameter 2 : 0x89d07008
Parameter 3 : 0xb84fbcbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021510-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021410-03.dmp
Crash Time : 2010/02/14 10:45:35 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x89394300
Parameter 2 : 0x8937ee18
Parameter 3 : 0xb84fbcbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021410-03.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021410-02.dmp
Crash Time : 2010/02/14 10:41:21 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x884a47d0
Parameter 2 : 0x89aaa008
Parameter 3 : 0xb84ffcbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021410-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021410-01.dmp
Crash Time : 2010/02/14 06:30:23 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x89bf5968
Parameter 2 : 0x899ee260
Parameter 3 : 0xb84fbcbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+27033
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021410-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini021010-01.dmp
Crash Time : 2010/02/10 10:10:57 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x87dcf020
Parameter 2 : 0x89bfd2b0
Parameter 3 : 0xb84f7cbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini021010-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020910-01.dmp
Crash Time : 2010/02/09 11:07:06 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x882e3020
Parameter 2 : 0x88a11840
Parameter 3 : 0xb84f3cbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini020910-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-02.dmp
Crash Time : 2010/02/07 05:23:23 PM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x881e08b8
Parameter 2 : 0x897d17c8
Parameter 3 : 0xb3202cbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+5d59b
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini020710-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-01.dmp
Crash Time : 2010/02/07 09:43:44 AM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x88fc56e8
Parameter 2 : 0x8876adc8
Parameter 3 : 0xb84f3cbc
Parameter 4 : 0x00000001
Caused By Driver : nv4_mini.sys
Caused By Address : nv4_mini.sys+7f4f5
File Description : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Product Name : NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
Company : NVIDIA Corporation
File Version : 6.14.11.9621
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini020710-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
==================================================

[rshaffer61]

Every one of your BSOD's has been caused by your Video Driver.



First, uninstall the NVIDIA drivers (if they are still installed) using Add or Remove Programs. You can get to Add or Remove Programs by clicking on the Start Button, then clicking on Control Panel. Then click Add or Remove Programs. Once in Add or Remove Programs, you need to find NVIDIA Drivers and click Change/Remove. (If you have an NVIDIA chipset, make sure the NVIDIA Display Driver checkbox is checked, then click Remove. Otherwise, just click Yes.)

Next, please download and install Driver Sweeper from here. (Click on the Download (Europe) link, then scroll down and click on I Agree.)

Then, boot the computer into safe mode. To do this,

• Turn the computer on (or restart the computer if it is already on).
• Start tapping the F8 key. The Windows Advanced Boot Options Menu appears. If you begin tapping the F8 key too soon, some computers display a "keyboard error" message. To resolve this, restart the computer and try again.
• Ensure that the Safe mode option is selected.
• Press Enter. The computer then begins to start in safe mode.

Next, open the program, Guru3D Driver Sweeper, that you just installed. Check the checkbox for cleaning NVIDIA - Display drivers. Then press the Clean button.

Download the newest drivers for your video card located Go Here for Nvidia drivers.
Supply the requested information in the drop down windows. It will scan your system and then should give you the newest driver for your video card. Download\Install that and then it should prompt you to reboot.
If not I suggest you do just to make sure the changes take affect.


Thanks to Stettybet0 for the instructions

[SalientAnimal]

Thanks for your help. I have now done all of what you suggested. Hope it works :-)

[rshaffer61]

Let us know how it works now.

[SalientAnimal]

Hey there, well everything seemed to be going fine for the past few days until today my PC crashed again. Is there perhaps something else that could be causing the problemm? I looked at the crash log myself and also the nVidia drivers or files relatated t my display being the reason for the crash. But could there be somethnig else causing this to happen?

[rshaffer61]

Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

[SalientAnimal]

Attached is the file I ran. Thanks

Attached Thumbnails

• 

[rshaffer61]

OK two things i need to seenow to double check everything.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply




Download SIW from HERE and get the Standalone English version
It will install itself and when finished
Then Click on SIW Icon to run program
On the left side click on one at a time of the following and then on the right, copy and paste the information in your next reply



Motherboard Info:

Download SIW from HERE and get the Standalone English version
It will install itself and when finished
Then Click on SIW Icon to run program
On the left side click on the Sensors directory and then on the right, copy and paste the information in your next reply

Edited by rshaffer61, 20 February 2010 - 09:43 AM.

[SalientAnimal]

Ok here is the Results from Who Crashed me: For some reason it didn't pick up the most recent crash:


--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.00
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

This program does post-mortem crash dump analysis with the single click of a button.


To obtain technical support visit www.resplendence.com/support

To check if a newer version of this program is available, click here.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.


--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 2010/02/17 08:37:36 PM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0xEA (0x88E698E8, 0x892E88A0, 0x8A3240D0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
Dump file: C:\WINDOWS\Minidump\Mini021710-01.dmp
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 196.21



On Mon 2010/02/15 09:27:02 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x88B9F968, 0x89DD9D20, 0xB84EFCBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021510-03.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 2010/02/15 03:56:50 PM your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x100000EA (0x89075750, 0x89941E18, 0xB3BB2CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021510-02.dmp
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21



On Mon 2010/02/15 02:45:57 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x89048750, 0x89D07008, 0xB84FBCBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021510-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 2010/02/14 08:45:39 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x89394300, 0x8937EE18, 0xB84FBCBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021410-03.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 2010/02/14 08:41:25 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x884A47D0, 0x89AAA008, 0xB84FFCBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021410-02.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 2010/02/14 04:30:27 PM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x100000EA (0x89BF5968, 0x899EE260, 0xB84FBCBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021410-01.dmp
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 196.21



On Wed 2010/02/10 08:11:01 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x87DCF020, 0x89BFD2B0, 0xB84F7CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini021010-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Tue 2010/02/09 09:07:10 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x882E3020, 0x88A11840, 0xB84F3CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini020910-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 2010/02/07 03:23:27 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x881E08B8, 0x897D17C8, 0xB3202CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini020710-02.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Sun 2010/02/07 07:43:48 AM your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x100000EA (0x88FC56E8, 0x8876ADC8, 0xB84F3CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini020710-01.dmp
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


And WIS info attached

Attached Thumbnails

• 

[rshaffer61]

Well your temps look within normal operating temps so not a problem there that I can tell.
4 of the 11 crashes are due to the video drivers. The other 7 are due to the OS itself.
Lets start with the OS and then do the video.
Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem








]

[SalientAnimal]

Thanks, will try it out, much appreciated.

I've never had problems like this before

[SalientAnimal]

I run the check disk scan with the repair last night and today when I logged onto my computer I got a new error:

On Mon 2010/02/22 02:56:43 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000EA (0x89BC5750, 0x89078708, 0xB46D5CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini022210-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

I'm sorry if I'm being a pain with all this stuff, but I am getting realy frustrated myself and have no idea how to fix this anymore. Would a normal install over the existing OS maybe fix this? Or would it have to be a clean install? I'm just guessing on other things I can maybe try, but I'm not sure....

[rshaffer61]

Would a normal install over the existing OS maybe fix this? Or would it have to be a clean install? I'm just guessing on other things I can maybe try, but I'm not sure....

What you are calling a normal install is what is referred to as a Repair installation and yes it may take care of the problem. This should in most cases leave your data safe.
The other option is to do a Parallel installation which would put a second windows on your system so you could copy your data over but the programs would all have to be reinstalled.
Let me know and i will will post the instruction for which ever you would like to try first.