Windows 7: BSOD with ntoskrnl.exe and uimx64.sys

sportsfan1995 · 28 Jan 2013

I have recently been BSODing again. The last time it did this it was a different ntoskrnl.exe (address state was different) and a different driver dealing with it. I am using an HP Pavilion g series laptop. Attached you will find the exported msinfo32 (system info) text file and the sf diagnostics zip file for the last created occurrence.

==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+5053dc
From Address : fffff800`03010000
To Address : fffff800`035f8000
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
==================================================
==================================================
Filename : uimx64.sys
Address In Stack : uimx64.sys+0
From Address : fffff880`04d18000
To Address : fffff880`04d30000
Size : 0x00018000
Time Stamp : 0x4ff4c9fa
Time String : 7/4/2012 4:55:54 PM
Product Name :
File Description :
File Version :
Company :
Full Path :
==================================================

sportsfan1995 · 28 Jan 2013

Just found an article on windows support forums saying to check for computer updates, and I found 5 updates, one irrelevant, another that has to do with my touchpad, two that deal with resolving issues with Windows 7 (that for some reason are optional), and another dealing with remote desktop connections with Windows 7.

Going to see if that does anything to help by installing the last four updates mentioned.

Dsprague · 28 Jan 2013

Looks like paragon is the cause of your problems, try updating the software off of their website if you can,or it may need to be updated to the latest version of their imaging software.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {62, fffffa800c12f508, fffffa800c1314d0, 1}

*** WARNING: Unable to verify timestamp for uimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uimx64.sys
Probably caused by : uimx64.sys

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

Also dont forget to disable driver verifier it can cause problems if left enabled.

**Northernsoul55** · 28 Jan 2013

Also a lot of your crashes relate to:

PROCESS_NAME: OrbLauncher.ex

It is also an App for Blackberry devices:

Quote:

Orb Launcher is a quick shortcut for your home screen to launch the Orb website for streaming video and music to your computer using the free Orb software.
The app will also keep your backlight on while the app is running so you do not have to worry about fading out while watching videos or listening to music.
This app assumes you have Orb already set up on your computer and is simply a launcher with shortcuts.

https://appworld.blackberry.com/webs...42879/?lang=es

I would suggest either re-install or update the app or remove it completely and see if that helps solve your issue

Cheers

Dave

sportsfan1995 · 28 Jan 2013

Okay, the paragon image mounter was the cause of the problem last time, but it was a different driver, in which I deleted all occurrences of that bad driver. Now it is another driver from PIM (I uninstalled PIM last time) that is causing the error. Should I just go ahead and find all of the drivers that PIM used and delete them? And I don't use Orb Castor for blackberry. I use it for my Iphone but it never performed the way I needed it to so I will also just uninstall that also.

Dsprague · 28 Jan 2013

I think it would be best that you do find and get rid of all the drivers for paragon as they seem to be causing problems on your system.

sportsfan1995 · 28 Jan 2013

I do believe I have deleted all instances of the UIM drivers.

Dsprague · 28 Jan 2013

Glad to hear it, hope this solves the problem, if not post back with your new crash dumps.

sportsfan1995 · 28 Jan 2013

Okay, I still had driver verifier running, but it caused a bsod with the tcpipreg.sys driver, which is a windows driver. Driver verifier was being weird and when I went to select my drivers, it only showed three drivers and they were from Windows, so I selected test all drivers.

Dsprague · 28 Jan 2013

You shouldn't be running driver verifier any more, let the system run normally for a while and see if you continue to get BSODs.

Windows 7: BSOD with ntoskrnl.exe and uimx64.sys

BSOD with ntoskrnl.exe and uimx64.sys problems?