Random Windows 7 BSOD

ttran · 26 Jun 2010

The minidump doesn't say much
I can see that mpc-hc.exe was process name at the time of BSODs. I guess it belong to K-lite codec in the path
%ProgramFiles%\K-Lite Codec Pack\Media Player Classic\mpc-hc.exe
Please remove it from computer. I used it and it never been causing any problem, but just try it for testing.

Do you have driver verifier on? I would suggest to turn it on
[quote]
Driver Verifier Settings

VISTA/Win7 Instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

~Tuan

Jonathan_King · 26 Jun 2010

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\062610-11559-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Sat Jun 26 13:12:14.438 2010 (UTC - 4:00)
System Uptime: 0 days 7:39:29.342
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff6800007e188, d870000097b95867, ff7ff6800007e188}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800007e188
Arg3: d870000097b95867
Arg4: ff7ff6800007e188

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  mpc-hc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ced608 to fffff80002c7b600

STACK_TEXT:  
fffff880`09af97b8 fffff800`02ced608 : 00000000`0000001a 00000000`00000403 fffff680`0007e188 d8700000`97b95867 : nt!KeBugCheckEx
fffff880`09af97c0 fffff800`02cac251 : 00000000`00000000 fffff680`0007eb88 fffffa80`05973b30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31f32
fffff880`09af9970 fffff800`02cbcfca : 00000000`00000000 00000000`0fd74fff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`09af9b30 fffff800`02c7a853 : ffffffff`ffffffff 00000000`09a0e080 00000000`09a0e078 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09af9c20 00000000`7752ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`09a0e048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7752ff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02ced608 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+31f32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32

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

theone320 · 26 Jun 2010

I am not using K-Lite, I am using CCCP, and that I will never remove. I will now turn on Driver Verifier again and see if it finds anything.

theone320 · 27 Jun 2010

Here is a pack of Blue Screens from Driver Verifier.

zigzag3143 · 27 Jun 2010

theone320 said:

Here is a pack of Blue Screens from Driver Verifier.

There are 45 DMP's that is going to take a while. Someone is working on it now.

EDIT

In an effort to save time and because they are so similar I only ran the 5 most recent DMP files. They were caused by your video driver (atikmdag.sys). I would suspect all of them were as well.

I also noticed that the crashes all happened at about 8 mins after boot. That may also indicate either a heat problem or perhaps an underpowered PSU.

You should remove all traces of the current driver (ATI has an un-install tool) before installing a fresh copy.

If that does not cure the problem you might want to download cpu-z and gpu-z to keep an eye on the temps.

ALSO DONT FORGET TO TURN DRIVER VERIFIER OFF

Let us know if you need help with this

Ken

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 26 21:03:03.732 2010 (GMT-4)
System Uptime: 0 days 0:08:01.778
BugCheck D6, {fffff98014f17000, 0, fffff88004b3f145, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+33b145 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD6
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 26 20:27:19.151 2010 (GMT-4)
System Uptime: 0 days 0:08:08.088
BugCheck D6, {fffff98014f43000, 0, fffff88004b8e145, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+33b145 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD6
PROCESS_NAME:  dwm.exe

Uptime

Code:

System Uptime: 0 days 0:08:00.660
System Uptime: 0 days 0:08:01.778
System Uptime: 0 days 0:08:08.088

theone320 · 27 Jun 2010

As you can see here, temperatures are not a problem. I will now turn on Driver Verifier again and see if it still crashes.

Jonathan_King · 27 Jun 2010

Do you have any scheduled tasks?

Remember to follow this part of zigzag's good advice:

You should remove all traces of the current driver (ATI has an un-install tool) before installing a fresh copy.

theone320 · 27 Jun 2010

I uninstalled everything form ATI with their uninstaller and then even ran Driver Sweeper over it to make sure everything is gone. I then restarted and installed the newest ATI Drivers. But is is still giving me BSODs with Verifier on, so I suppose it is just a faulty driver, since ATI did not bluescreen the last time I had Driver Verifier running. But what I want to get rid of are the 0X1A BSODs. The ones Driver Verifier are causing are never 0X1A problems, and I never have anything except 0X1A when running without Driver Verifier. My conclusion is a Hardware or BIOS fault, since after reinstalling Windows I still had the same 0X1A BSOD.
I think the primary culprit is my motherboard. The weird think is, that Memtest86+ does not give me errors, but my PC still randomly crashes every few weeks because of 0X1A errors, which are Memory Management issues. My only hope are Bios settings, but I have no idea what to change. If this continues, I will just get a new motherboard, even if that is an expensive way out. And no, I check scheduler, no Tasks started in the last 24h.

zigzag3143 · 27 Jun 2010

theone320 said:

I uninstalled everything form ATI with their uninstaller and then even ran Driver Sweeper over it to make sure everything is gone. I then restarted and installed the newest ATI Drivers. But is is still giving me BSODs with Verifier on, so I suppose it is just a faulty driver, since ATI did not bluescreen the last time I had Driver Verifier running. But what I want to get rid of are the 0X1A BSODs. The ones Driver Verifier are causing are never 0X1A problems, and I never have anything except 0X1A when running without Driver Verifier. My conclusion is a Hardware or BIOS fault, since after reinstalling Windows I still had the same 0X1A BSOD.
I think the primary culprit is my motherboard. The weird think is, that Memtest86+ does not give me errors, but my PC still randomly crashes every few weeks because of 0X1A errors, which are Memory Management issues. My only hope are Bios settings, but I have no idea what to change. If this continues, I will just get a new motherboard, even if that is an expensive way out. And no, I check scheduler, no Tasks started in the last 24h.

The 0x1A bugcheck is memory management.
STOP 0x0000001A: MEMORY_MANAGEMENT

These last two crashes were still caused by your ati driver. Though the first parameter is a memory exception.

There has to be a problem with your GFX

Ken

Code:

BugCheck D6, {fffff98015163000, 0, fffff88004be7145, 0}
Probably caused by : atikmdag.sys ( atikmdag+33b145 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff880042ed920, fffff880082bb890, 0}
Probably caused by : atikmpag.sys ( atikmpag+22920 )

theone320 · 27 Jun 2010

Yeah but the last time I had Driver Verifier on, it did not show any Ati errors, so it a probably a problem with the current driver. I will just wait for the next version.