BSOD - now with minidump

[rabor]

Could someone please tell me what the heck just happened?

I was playing MW2 when my system crashed, & the screen looked like my gpu had exploded. Did some quick tests but all seems fine..
In the past couple of days/weeks I tested my hardware extensively; my memory had passed approx 18 hours of memtest86+, my cpu did 150 passes of LinX (all mem) & my gpu did approx 4 hours of Furmark dual gpu.

Windows 7 Ultimate 64 - fresh install was done approx 6 weeks ago, & i'm still running Microsoft Security Essentials.

This was the previous problem I had a couple of days ago (in this post are links to my previous problems as well):

http://www.sevenforums.com/crashes-...unning-torrent-client-deluge.html#post1031970

Thanks again!

 

[Jonathan_King]

Start by installing these Realtek drivers: Realtek

Go here: ASUSTeK Computer Inc.-Support-

From the Utilities section, download and run the ATK0110 driver.

ASACPI.sys   Sun Mar 27 22:30:36 2005

If the BSODs persist, please run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 20:09:30.790 2010 (UTC - 4:00)
System Uptime: 0 days 4:45:15.633
BugCheck A, {0, 2, 0, fffff80002ad379f}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[CarlTR6]

Hi, Rabor; sorry you are having trouble. I will take a look and be right. I will edit this post; so refresh this page in about 15 minutes.

 

[CarlTR6]

Jonathan beat me to it. He types faster than i do. Follow his advice and suggestions.

 

[rabor]

I will.., thanks for the ultra fast response!

 

[rabor]

Hi, ok, I installed the Realtek drivers & ATK0110 driver, but again the system froze.

I then ran/enabled driver verifier as suggested & during the reboot I got a BSOD from some corrupted driver or drivers..

Here's the minidump, thanks.

 

[zigzag3143]

Could someone please tell me what the heck just happened?

I was playing MW2 when my system crashed, & the screen looked like my gpu had exploded. Did some quick tests but all seems fine..
In the past couple of days/weeks I tested my hardware extensively; my memory had passed approx 18 hours of memtest86+, my cpu did 150 passes of LinX (all mem) & my gpu did approx 4 hours of Furmark dual gpu.

Windows 7 Ultimate 64 - fresh install was done approx 6 weeks ago, & i'm still running Microsoft Security Essentials.

This was the previous problem I had a couple of days ago (in this post are links to my previous problems as well):

http://www.sevenforums.com/crashes-...unning-torrent-client-deluge.html#post1031970

Thanks again!

To start remove asacpi.sys (dated 2005) it is a known cause.
ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).[/quote



Then update these drivers

JmtFltr.sys        fffff880`05c29000    fffff880`05c34580    0x0000b580    0x46fd3439    9/28/2007 13:04:57                        
vhidmini.sys        fffff880`0593a000    fffff880`0593d680    0x00003680    0x46fd3835    9/28/2007 13:21:57                        
spldr.sys        fffff880`01bbe000    fffff880`01bc6000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`053b0000    fffff880`053bd000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00dd0000    fffff880`00ddb000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

Finally un-install your video driver and re-install current version
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.


Let us know if you need further assistance


Ken J

 

[rabor]

Ken, I had already updated ASACPI.sys in my previous post,

so my next question is; how do I update-, or where do I find these 5 drivers?

I've learned that JmtFltr.sys is from my Belkin Nostromo N52te but there is no newer driver than the one I am using, & otherwise I cannot find this particular driver except for when I go to Carrona where there's a link from JmtFltr.sys to Driver , but then there are several drivers & I wouldnt know which one to use (jmb38x, jmb36x, jmc2xx) or if they even are the correct drivers.

The same goes more or less for the other drivers; I can't find them, or they are linked to programs that I don't use, so i'm a bit at a loss.

Btw, was upgrading my Catalyst 10.9 to 10.10 really necessary?

Thanks again.

 

[CarlTR6]

JmtFltr.sys - JMicron JMB38X Memory Card Reader Driver Driver

From the JMicron website FAQ:

Q1: What Operating Systems are supported?
Ans: Microsoft® Windows® Series: Windows 2003/XP 32/64 bit, Windows 2000
Linux Series: Red Hat Fedora, SuSE , Gentoo , Ubuntu, Slackware, Manadiva, Debian, and other Linux Distribution based on Linux kernel 2.6.18 or above
BSD Series: FreeBSD , OPENBSD , NETBSD , DragonflyBSD
NAS OS Series: FreeNAS , OpenFiler , Open-E NAS
For complete OS listing, go to: http://www.jmicron.com/PDF/OSSupport/OS_Support.pdf

It appears that device is not supported for Win 7. You can search here to see if it is listed as compatible. If it is not, you need to uninstall the card reader and upgrade to one that is certified Windows 7 compatible.

Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

vhidmini.sys - most likely an IVT Corporation BlueSolei Bluetooth HID Mini driver BlueSoleil - Bluetooth Software,Bluetooth Driver,Bluetooth Dongle

I suspect this hardware is obsolete also. If you cannot update the driver, uninstall.


spldr.sys - This is an MS driver; don't worry about it.

GEARAspiWDM.sys - to the best of my knowledge, there is no update for this driver. It is a Vista driver and seem to work with Win 7.

amdxata.sys - this is the latest driver; it is a Vista driver. It seems to work OK with Win 7.

Hope this helps.

 

[rabor]

Hi, JmtFltr.sys seems to be a driver for my Belkin N52te gamepad:



I don't have a cardreader on this system, except for the occasional usb-cardreader, for the rest this system is mainly for gaming & some downloading & music. So there is not a lot of other software installed, plus this is a pretty fresh Windows install. I did install that jmicron driver to be sure tho.

The N52te works perfect btw, been using it since the W7 Beta's & also on previous Vista 64 installs.

About the vhidmini.sys driver; I have no idea what that Blue Soleil stuff is. I have never installed any bluetooth hard- or software; like I said this install is less than 6 weeks old & only a couple of programs have been installed.

Plus, I had to revert to Catalyst 10.9.. As I had already read on several fora; last week's 10.10 is far from perfect & many had to go back to 10.9 - which is only 6 weeks old tbh..

I completely removed Acronis aswell.. see how it runs now.

Thanks all for your help.

 

[CarlTR6]

I learned something; the JmtFltr.sys driver is used for at least two different applications. I appreciate that. It is certainly not the only driver that is used by multiple applications.

You msinfo32 file says vhidmini.sys driver belongs to a Virtual Hid Device. The Blue Soleil is all I could find about it in Driver Reference. It could be used by another application. What virtual devices do you have installed? ONe thing you can do to find out what it is first create a restore point and then navigate to C:\Windows\System32\Drivers, find vhidmini.sys and rename it from .sys to .bak. Reboot and the driver will not load. However, it will break whatever software it is associated with.