BSOD ntoskrnl.exe error with HP Pavilion g6 Notebook PC

[sportsfan1995]

My computer has been BSODing lately and I haven't found out the problem yet. I have already ran memtestx86 and it said everything passed.

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name CHRIS-HP
System Manufacturer Hewlett-Packard
System Model HP Pavilion g6 Notebook PC
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Hewlett-Packard F.34, 6/14/2012
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Chris-HP\Chris
Time Zone Central Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.95 GB
Available Physical Memory 4.50 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 11.7 GB
Page File Space 7.95 GB
Page File C:\pagefile.sys
HDD: TOSHIBA MK7575GSX
System board: 1695 KBC Version 15.1F

cause:
==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+37e460
From Address : fffff800`02e4d000
To Address : fffff800`03435000
Size : 0x005e8000
Time Stamp : 0x503f82be
Time String : 8/30/2012 9:11:58 AM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Company : Microsoft Corporation
Full Path : C:\Windows\system32\ntoskrnl.exe
==================================================

 

[Arc]

upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[sportsfan1995]

I exported the system information earlier, and have it saved as system information. That's where I got all of the stuff from for the spec stuff. Also I'm in my PC Service Tech class, so I have some things available that most people wouldn't. About to upload.

 

[sportsfan1995]

and here is the file

 

[Arc]

Uninstall the following programs:

• Start Menu\Programs\avast! Free Antivirus : Install Microsoft Security Essentials.
• Start Menu\Programs\ooVoo
• Start Menu\Programs\Paragon Backup and Recovery™ 12 Compact
• Start Menu\Programs\Paragon Partition Manager™ 12 Free

Let us know if it is changing anything or not.

 

[sportsfan1995]

By change do you mean if there is a BSOD again?

 

[Arc]

By change do you mean if there is a BSOD again?

Then we have to search deeper. But as it is a Stop 0xF4, and silent about anything, initially it is better to isolate the possible things those have bearings on the storage devices.

ooVoo is an odd man out in the list, but it is a known source of crashes, as far as I have seen.

 

[sportsfan1995]

I haven't uninstalled them yet. avast and oovoo aren't a problem to uninstall. the two paragon backup and recovery and partition manager are two programs that I got from giveawayoftheday.com and are registered and i don't believe i will be able to install them again and have them activated and so on. If I have to get rid of them I will, but they are really useful tools. I also currently don't have a way of getting them onto a storage device to transfer them back later if they aren't the problem.

 

[Arc]

You can save your entire existing installation.

http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html

If you take the backup on an external HDD/a set of DVDs, you can restore the entire installation in need.

I have nothing to say against paragon, those are undoubtedly good; but sometimes they may cause disc related BSODs, like any other backup taking programs. And, I also have no way to say it with certainty that paragon is the cause of the crash; it is just a sophisticated guess.

As an alternative approach, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[sportsfan1995]

Okay with Driver Verifier, I am at the screen where you select drivers to verify and there are only two drivers and they are from microsoft

 

[Arc]

Driver Verifier - Enable and Disable

Follow it, step by step.

 

[sportsfan1995]

Here are the crash files, sorry it took so long. It crashed earlier this morning and I just got it back to where it could run windows and let me get here to turn driver verifier off.

 

[sportsfan1995]

a new driver was found that was causing a bsod and it is uim_vimx64.sys (or something like that). After googling the driver, I saw a few articles talking about the paragon image mounter. I don't know if this is right or not but I am going to go ahead and uninstall the program.

 

[Arc]

Yes, it is crashed by Paragon Image Mounter (UIM) Plugin driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e1, fffff98001506f9c, 0, 0}

*** WARNING: Unable to verify timestamp for uim_vimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uim_vimx64.sys
[COLOR=Red]Probably caused by : uim_vimx64.sys[/COLOR] ( uim_vimx64+1827e )

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

As a test, you may uninstall the Paragon products and see if it works or not. Any type of image mounter program is troublesome, as far as I have seen.

 

[sportsfan1995]

as an alternative, could I try to find a new version of the driver? I'm going to go ahead and search for it, but I will probably uninstall the Paragon products. I know for sure that the Paragon Backup and Recovery Utility does allow you to mount images so that you can make bootable usbs/cds/dvds, and so on. I assume that will be the one that has to be uninstalled no matter what

 

[Arc]

The driver is not any old, it is of around July 2012. If you want to search for an update, you may visit in Paragon Software: Download free partition software for home.

 

[sportsfan1995]

Okay I uninstalled the two paragon programs I had installed. The uim_vimx64.sys file is still there though. I have no clue whether or not it is installed by windows or if it is installed by paragon, but I assume paragon. What should I do next?

 

[Arc]

Search in these places:

• C:\Windoes\System32\drivers
• C:\Windows\SysWOW64\drivers

If those are found there, delete those.

 

[sportsfan1995]

Okay I searched in both of those places and deleted the file if I found it, and then I went to My Computer and searched there for the file and this screenshot showed up

 

[Arc]

Delete this one too.
View attachment 249667