A Fistful of Blue Screens

mpiedlourde · Aug 11, 2010

Hi all,

Back in June I had some problems with my system that were resolved by the very helpful members of this forum (link). Unfortunately I've been having some more blue screen issues lately. Most of the time they happen after the system has shut down without going through the full shutdown process (ie power outage or complete system freeze), necessitating a lengthy repair process using the Windows 7 install disc.

Not all of the BSoDs have yielded a minidump file, but I've attached what information I have. The "Windows7_BSOD_jcgriff2" folder and the Perfmon file are both inside the "diagnostics" folder.

Thanks in advance for any help you have to offer.

ttran · Aug 12, 2010

Hi and welcome to SF!

Please remove Norton, third party antivirus are notorious for causing BSODs, please remove it for testing purpose:
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support
Try Microsoft security Essential, it's free and BSODs free:
http://www.microsoft.com/security_essentials

MDFSYSNT.sys was blamed, it is your MacDrive, Mediafour Corporation, please download and install fresh copy of it.
Also, your Realtek audio driver,RtHDMIVX.sys, appear in one DMP, please download and install fresh copy of it
Please perform a http://www.sevenforums.com/tutorials/433-disk-check.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

Code:

BugCheck C2, {7, 1097, 30213, fffff8a00917e140}

GetPointerFromAddress: unable to read from fffff800034b60e0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+c3ea )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff8000308876b, fffff880031af4b8, fffff880031aed20}

Probably caused by : MDFSYSNT.sys ( MDFSYSNT+736b )

Followup: MachineOwner
---------
BugCheck 50, {fffff881046e5d60, 1, fffff880047d2a4b, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck 24, {1904fb, fffff88006ec3718, fffff88006ec2f80, fffff880012d3c55}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+22c )

Followup: MachineOwner
---------
BugCheck BE, {fffff8800513ced8, 8000000127a58121, fffff88003db6610, b}

*** WARNING: Unable to verify timestamp for RtHDMIVX.sys
*** ERROR: Module load completed but symbols could not be loaded for RtHDMIVX.sys
Probably caused by : hardware ( portcls!PcAddToPropertyTable+20f )

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

Are you overclocking anything?

mpiedlourde · Aug 12, 2010

Thanks for your reply!

I didn't have the full Norton Antivirus, but I did have Norton Internet Security, which is now removed. I currently have Avast! Antivirus installed... should I remove that and replace it with Microsoft Security Essentials?

And no, I am not overclocking anything.

richc46 · Aug 12, 2010

MSE is one of the best A/V for Windows, in the opinion of many members. So yes install. It has never been the cause of a BSOD, that I am aware of, so it is good to install, at least for test purposes.

Use the uninstall tool to remove any other A/V. If you need help with that, just post.

mpiedlourde · Aug 12, 2010

OK so I uninstalled all my antivirus stuff and replaced them with Microsoft Security Essentials, and I installed a fresh copy of MacDrive, but I just got another two BSoDs in a row. I've attached the DMPs for both BSoDs to this post. I'm guessing it's still a problem with MacDrive, as I was using a Mac-formatted hard drive when the system crashed, but I'm hoping that isn't the case because I have 2 external hard drives that I can't really reformat right now and I'd like to be able to continue using them.

CarlTR6 · Aug 12, 2010

Both of these dumps blame MDFSYSNT.sys which I think is a driver for your Mac drive.

BugCheck 34 - Usual causes: Insufficient physical memory, Indexing, Device driver

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_081210-18049-01.zip\081210-18049-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`03494e50
Debug session time: Thu Aug 12 20:43:55.276 2010 (GMT-4)
System Uptime: 0 days 0:00:47.588
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {107, ffffffffc0000420, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\MDFSYSNT.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MDFSYSNT.sys
*** ERROR: Module load completed but symbols could not be loaded for MDFSYSNT.sys
Probably caused by : MDFSYSNT.sys ( MDFSYSNT+45c07 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000000107
Arg2: ffffffffc0000420
Arg3: 0000000000000000
Arg4: 0000000000000000

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


EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)
Cannot read Exception record @ ffffffffc0000420

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x34

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000327c17b to fffff800032c7740

STACK_TEXT:  
fffff880`079961d8 fffff800`0327c17b : 00000000`00000034 00000000`00000107 ffffffff`c0000420 00000000`00000000 : nt!KeBugCheckEx
fffff880`079961e0 fffff800`035d921a : 61007400`00022000 fffff880`07996358 f5010000`00002000 01000000`ed410001 : nt! ?? ::FNODOBFM::`string'+0x44c48
fffff880`079962a0 fffff880`018b2c07 : 00000000`00000000 00000d25`20000000 00000000`00002000 fffffa80`04576820 : nt!CcPinRead+0xde
fffff880`07996350 00000000`00000000 : 00000d25`20000000 00000000`00002000 fffffa80`04576820 fffff880`07996448 : MDFSYSNT+0x45c07


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MDFSYSNT+45c07
fffff880`018b2c07 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  MDFSYSNT+45c07

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MDFSYSNT

IMAGE_NAME:  MDFSYSNT.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b6ae447

FAILURE_BUCKET_ID:  X64_0x34_MDFSYSNT+45c07

BUCKET_ID:  X64_0x34_MDFSYSNT+45c07

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

ttran · Aug 12, 2010

Opps..Carl is fast

Hi,

STOP 0x00000034: CACHE_MANAGER

Usual causes: Insufficient physical memory, Indexing, Device driver

You are right, your MDFSYSNT.sys (Macdrive) was blamed again with the stop code above. One way might be able to solve the stop code above is to increase physical memory.

Code:

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.708\081210-18049-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`03494e50
Debug session time: Fri Aug 13 07:43:55.276 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:47.588
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {107, ffffffffc0000420, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\MDFSYSNT.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MDFSYSNT.sys
*** ERROR: Module load completed but symbols could not be loaded for MDFSYSNT.sys
Probably caused by : MDFSYSNT.sys ( MDFSYSNT+45c07 )

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

Regard,

Tuan

CarlTR6 · Aug 12, 2010

You also so have some outdated drivers. I think Ttran mentioned those previously. While these may or may not be contributing to your crashes, they are not helping your system stability.

AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD

gdrv.sys Thu Mar 12 23:22:29 2009 - GIGABYTE Tools, Windows Update

mcdbus.sys Tue Feb 24 05:34:07 2009 - MagicISO SCSI Host Controller belongs to the software MagicDisc or Driver for MagicISO SCSI Host Controller by MagicISO, Inc.

PxHlpa64.sys Tue Jun 23 19:16:35 2009 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

This should give you some help in updating your drivers.

mpiedlourde · Aug 14, 2010

Thanks everyone for your replies. Unfortunately the problems expanded beyond the blue screens and I was getting frequent application crashes and other weird little glitches, so I ultimately elected to just reinstall Windows 7. Things are definitely running smoother now.

CarlTR6 · Aug 14, 2010

Thanks for reporting back. A clean install is certainly a solution.

Glad to hear you are running smoothly.

A Fistful of Blue Screens

New member

My Computer My Computer

At a glance

Computational Biologist

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Moderator

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

Computational Biologist

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Antique Senior Member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer