Random Freezes, BSOD, other crashes

[waterhaus]

Hi, I built a desktop for myself in January of this year and I've had semi-random crashes a few times a week ever since. I updated all the system specs in the user pane, but basically it's Windows 7 Ultimate x64 installed on a SSD with another HDD for most of my data and stuff. The comp uses a sandybridge CPU and motherboard, but I don't think the problems are related to the issues for which those MBs were recalled.

I am unable to reproduce the crashes, but I can almost guarantee that one will happen in any given week. It doesn't seem to matter if I'm gaming, just surfing the net, using lots of apps/few apps, etc. I also can not predict when I will get a BSOD, when the computer will simply freeze, or when the screen will flash with those colors that look like a video card failure.

These crashes come sometimes a few times in a day, and at other times I can go a week or two without a problem. I have tried to keep my drivers updated, and I believe that my BIOS is the most current version as well. This is my first personal build and I've been expecting and dealing with problems like this, but I simply cannot seem to find the cause of these crashes, and it is really starting to be a bother.

This may be unrelated, but sometimes when I boot up the computer, it says it is unable to find the SSD (Where the OS is installed). I usually just reboot it and it works, and I can not predict when I will get that boot error. I've also run memtest and found no errors; I think I quadruple-checked all my wiring and such inside the case and I believe everything is set up correctly - it seems so odd that the computer will run like a dream for days on end, then suddenly just crash.

Any help you may be able to give will be greatly appreciated!

 

[MvdB]

Hello Waterhaus, welcome to SF!

your last dump is a 3D, pointing to what should be a normal system file \SystemRoot\system32\DRIVERS\mv91xx.sys

Please check it is in this directory and ONLY in this directory.

Your second to last dump points to atikmdag.sys
For that please see http://www.sevenforums.com/crashes-debugging/55775-bsod-start-w7-atikmdag-sys.html

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff80000b9bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800132278e

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


CONTEXT:  fffff80000b9bf60 -- (.cxr 0xfffff80000b9bf60)
rax=fffffa8008a6d200 rbx=fffffa8008a7e868 rcx=0000000000000000
rdx=fffffa8008a7e868 rsi=0000000000000000 rdi=fffffa8008a8f608
rip=fffff8800132278e rsp=fffff80000b9c940 rbp=fffffa8008a6d748
 r8=fffff88003940100  r9=0000000000000001 r10=fffffa8008a8f680
r11=fffffa8008a6e018 r12=0000000000000100 r13=fffffa8008a8af90
r14=fffffa8006990890 r15=fffff80000b96080
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000293
mv91xx+0x3178e:
fffff880`0132278e cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  System

CURRENT_IRQL:  a

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800132278e

STACK_TEXT:  
fffff800`00b9c940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mv91xx+0x3178e


FOLLOWUP_IP: 
mv91xx+3178e
fffff880`0132278e cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  mv91xx+3178e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mv91xx

IMAGE_NAME:  mv91xx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c778a22

STACK_COMMAND:  .cxr 0xfffff80000b9bf60 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_mv91xx+3178e

BUCKET_ID:  X64_0x3D_mv91xx+3178e

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

0: kd> lmvm mv91xx
start             end                 module name
fffff880`012f1000 fffff880`0137d000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        Fri Aug 27 11:49:22 2010 (4C778A22)
    CheckSum:         00050BB0
    ImageSize:        0008C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[waterhaus]

Thanks for the quick reply!

I checked and the mv91xx.sys file is in 3 different places: the proper c:\windows\system32\drivers but also
C:\Windows\System32\DriverStore\FileRepository\mv91xx.inf_amd64_neutral_afacc001e9dc1ee8 and
C:\Program Files (x86)\Marvell\mv91xx\driver

Should I delete the other 2 files? Or delete those folders completely?

As for the other crash cause I will look into the possible fixes, thanks for pointing me in the right direction!

 

[MvdB]

Thanks for the quick reply!

I checked and the mv91xx.sys file is in 3 different places: the proper c:\windows\system32\drivers but also
C:\Windows\System32\DriverStore\FileRepository\mv91xx.inf_amd64_neutral_afacc001e9dc1ee8 and
C:\Program Files (x86)\Marvell\mv91xx\driver

Should I delete the other 2 files? Or delete those folders completely?

As for the other crash cause I will look into the possible fixes, thanks for pointing me in the right direction!

Are they all (all 3) the same size? Don't delete (yet) but scan them with av and malwarebytes.... if ok, I guess you can leave them. I'll look up if the Marvell install is ok...

 

[waterhaus]

Hi, I am still getting freezes on my machine, though the BSOD seem to have stopped. Perhaps the Marvell controller is what was causing the BSOD?

At any rate, the freezing is still a constant occurrence, but I am still unable to pinpoint why or when it will happen. My computer has frozen twice today and 3 times yesterday, but it was fine for several days in a row prior to this. I have checked everything I know how to check, installed/updated every driver I can, and still the freezes come. I have noticed that they do tend to come more frequently when gaming, but I can have a freeze just browsing the internet with no other applications open.

I don't think heat is a issue as I have been watching the GPU-Z and CPU-Z programs and recording the temp. I have also double-checked all my wiring inside the case and ensured that everything is locked snugly into place. The freezing can occur 6+ hours after I boot, or it can happen within 15-20 minutes.

I have had some games crash once or twice without freezing the computer; WoW has crashed twice and given me a memory error. I ran the boot Memory checker on a UDB drive for a few hours and found no errors with my RAM, though.

I have looked at dozens of forums relating to the atikmdag.sys issues, but have found nothing that has worked for me.

Any help you may be able to give would be greatly appreciated; I'm at the point that if someone told me that it was for sure a certain piece of hardware, I would throw that piece away and get something else. This freezing problem has really crippled my computer, and this is the computer that I work on as well as game, so this is a very serious issue for me.

Thanks!

 

[MvdB]

I can have a good look at the dump tomorrow but for now please check http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671

I should probably have pointed you there the first time as that driver, the ati one, must be updated.

 

[waterhaus]

Thanks, I'll update to that latest driver, but I', pretty sure I have the 11.6 regular, and it doesn't look like they've changed much in the 11.6b update. I check my drivers every few weeks and I'm thinking that the issue stems from something else.

 

[MvdB]

Thanks, I'll update to that latest driver, but I', pretty sure I have the 11.6 regular, and it doesn't look like they've changed much in the 11.6b update. I check my drivers every few weeks and I'm thinking that the issue stems from something else.

Do you use Driversweeper in safe mode to be sure you fully delete old stuff?

 

[waterhaus]

No, I usually don't. I'll try that too. Thanks!

 

[waterhaus]

It looks like driversweeper has been discontinued; at least that's what it says on the website. Is there another program I might use instead to clean out the old drivers? Also, in looking at the dmp files, i found reference to atikmpag.sys (different from atikmdag.sys) and so I searched for that file and found 6 instances of it on my computer - one in windows/system32/drivers and 5 in

system32/driverstore/filerepository/c7118907.inf_amd64_neutral_8dff244759d44064\B117547

or similar file repository folders. One instance of the file is dated as being last modified on 11/25/2010, which seems strange since I built the computer in January 2011. I scanned all files for viruses and found none, though. I wonder why this is giving me problems?

 

[MvdB]

Driversweeper: Phyxion.net - Driver Sweeper

Your multiple instances... is exactly what we want to cure with driversweeper...

 

[waterhaus]

OK, ran driver sweeper in safe mode, but before I make any changes I have a big question: I have an AMD graphics card, and as I built the system I know it's the only GPU that's ever been used with this comp/windows install. Driver Sweeper finds AMD-Display drivers, but also finds NVIDIA_Display, NVIDIA-Chipset, and NVIDIA-PhysX. I know that the Nvidia chipset may be from the windows install or the mobo, but I should get rid of the nvidia display drivers for sure, right? What about the PhysX drivers? Will AMD drivers install that back?

Also, I am showing sound drivers from both Creative and Realtek, as well as Asus - should I only be using one? I'm pretty sure Realtek is the one I downloaded from the Asus mobo website, yet Asus is listed too. I have had some minor sound problems - for instance Ventrilo telling me I have a sound driver conflict, yet playing sound just fine.

Finally, I have 2 USB drivers, from Fresco Logic and from NEC. The mobo came with a addon card for 2 more USB3 ports, so I am assuming it has something to do with that and is not a problem. I have no idea either way, though.

Thank you so much for all the help you've given so far! I am crossing my fingers that this Nvidia Display driver is the source of my problems, but I am at a complete loss as to figure out why it is even installed.

 

[MvdB]

I'm on a iPAD right now so it is hard for me to check your system specs...

1. The double nvidia drivers should not be needed. Depending on you mobo (that is what i cannot check right now) it could be the mobo has onboard nvidia graphics. But even so... My choice would be to de-install. We know how to find up to date stuff if it proves to be needed.

2. The same goes for sound. I would deinstall all, reboot and install latest from the manufacturer.

3. Be careful with the chipset however. I have no reason to suspect those for now. Lets do one thing at a time and remember this for later...

4. Multiple usb is logical only if you have multiple different usb components (ie mobo usb2, mobo usb3 etc)

Good luck, hope we're getting there....

 

[waterhaus]

OK, I ran driversweeper in safe mode and uninstalled AMD -Display, Nvidia - Display, Nvidia - PhysX, and the 3 sounds drivers (realtek, Asus, and Creative). I reinstalled Realtek (from the P8P67 Pro downloads section - that's my mobo). I rebooted into safe mode again and tried to install the latest 11.7 AMD drivers for my Radeon HD 6950, and I got this error: "Failed to load detection driver." The install failed. I rebooted into safe mode again and ran driversweeper again to clear out any partial install that the AMD drivers might have done, and tried again, with the 11.6 drivers (these 11.6 drivers are the one I was using before, I still had the install saved on my machine) I got the exact same "Failed to load detection driver" error. Also, curiously, driversweeper said there were no Realtek or any other sound drivers, too, but sound is working just fine from the green output on the mobo to my speakers, but whatever. The big issue is that my computer is no longer benefitting from the GPU. I can run regular and safe mode both without issue, but obviously this is no good because of the terrible resolution from whatever onboard CPU graphics processing or whatever I am getting now.

How do I re-install the drivers for the GPU? I have looked around online for people with similar errors, but the advice is wildly varying and I can't find a consensus on what to do. In Device Manager, Windows is recognizing that I have an AMD Radeon 6900 Series card, but the Device Status Message says this:

"Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"

Driver File Details on that card points to Windows\system32\coinst.dll and Windows\sysWOW64\Oemdspif.dll

The settings also show a Driver Date of 5/24/2011 and Driver Version 8.861.0.0, Device Provider: ATI Technologies.

Help! I have no clue what to do now.

 

[waterhaus]

OK, I went ahead and tried to install the most recent video drivers in regular mode (not safe mode) and they installed without problem. I rebooted and they appear to be working again; at least my resolution and dual monitors are back to normal. However, I also noticed that when the computer first booted, there was a small window on the top left of the screen that looked like some sort of video or something. The program was named "MMloaddev" or something - it disappeared after just a second. What is this??

 

[MvdB]

We would have to check with AMD as I am not entirely sure... but that should be a warning that your graphics card is not getting enough power (amps on the 12v rail).
My advice would be to be careful and keep doing one thing at a time, takes patience but it is the only way to find out exactly what action helps (or causes) what problem... If your system works ok now with normal usage, give it some time to be sure. Only the raise the stakes and test something heavier, maybe a demanding (graphics-wise) game. If it messes up when you do that, lets keep a potential power issue in mind for further testing?

Since it is a personal build, you probably know, and have calculated, the details. So IF you realize there might be something loose or incorrectly connected, it's fine to check of-course... but looking at your spec's I'd say the psu should be fine for your system.

What you can / should do if a message on that process returns is uninstal Catalyst itself, not with driversweeper but with its own de-install. That way you should keep your drivers whilst losing the overhead of the extra Catalyst stuff of which this process is a part.

 

[waterhaus]

I did what was suggested and I haven't had a freeze yet, but it's still too early to tell if I will.

I did, however, have another BSOD, a 3d error pointing back at that MV91xx.sys file, which I think is the Marvell storage controller. I have the most recent version from the mobo manufacturer's website:

ASUSTeK Computer Inc. -Support- Drivers and Download P8P67 PRO

but in looking around on the net, I found this website

ASUS P8P67 Pro bios & drivers

Which looks to have more recent Marvell drivers. Also, the mobo site only has one marvell driver, while this other site appears to have 3, one of those 3 pointing specifically to the MV91xx BIOS or something. Should I download and install these newer drivers? Should I install all three of the drivers they have, or just focus on the plain driver download?

I'm not sure if it's important, but before the BSOD my screen did the rainbow color static, but just for a second. I wonder if it's the GPU, but why would it reference HDD/SATA drivers as the cause? I'm still confused. Thanks for your help, MvdB.

 

[MvdB]

It does not hurt to try. As a rule, we go for drivers from the manufacturer of the HW item. However, sometimes a mobo manufacturer needs special settings for a SATA driver to work on his mobo. In that case we must go with the drivers that come with the mobo. I don't like it but sometimes this is trial and error. If you know what you're doing and can retrace your steps / go back, it doesn't hurt to try both and see what is stable.