BSOD Asus Mini Dump

[kaoticsolja]

Heres what I have,
I have a prebuilt rig Asus CM5675 under warante

Windows 7 Home Premium

Intell Core i5 650

Southbridge intell H55 chipset

I am getting BSOD seemingly when I begin to use to much RAM. I have clean installed twice and still same thing. BSOD only seems to happen when I am preforming large or multiple tasks such as video editing and conversion. I was in the mids of learnign how to flash my BIOS when someone said my BIOS shouldnt be causeing kernel panics. Anyhow I think I will do it anyway when I find the right BIOS (theres so much blah blah on Asus' site. So I read a post on here that said to post my mini dump so people can help me with this problem. I will be taking this back to the store if it dosnt stop. I should have built my own rig! its a Service_Exception error heres the dump///

 

[zigzag3143]

Heres what I have,
I have a prebuilt rig Asus CM5675 under warante

Windows 7 Home Premium

Intell Core i5 650

Southbridge intell H55 chipset

I am getting BSOD seemingly when I begin to use to much RAM. I have clean installed twice and still same thing. BSOD only seems to happen when I am preforming large or multiple tasks such as video editing and conversion. I was in the mids of learnign how to flash my BIOS when someone said my BIOS shouldnt be causeing kernel panics. Anyhow I think I will do it anyway when I find the right BIOS (theres so much blah blah on Asus' site. So I read a post on here that said to post my mini dump so people can help me with this problem. I will be taking this back to the store if it dosnt stop. I should have built my own rig! its a Service_Exception error heres the dump///

These were caused by MDFSYSNT.sys which is a Mac driver. Are you by chance running win 7 from boot camp?


Waiting for info before suggesting a fix

MDFSYSNT.sys    6/22/2009 15:52:50    0x4a3fef22    fffff880`01823000    fffff880`01882000    MDFSYSNT.sys+6ec4    0x0005f000                    
MDPMGRNT.SYS    7/6/2009 16:05:22    0x4a526712    fffff880`015f0000    fffff880`015fd000        0x0000d000

Launchpad caused mdfsysnt.sys to fail

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


Loading Dump File [C:\Users\K\Desktop\012311-28938-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;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`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Sun Jan 23 12:27:23.885 2011 (GMT-5)
System Uptime: 0 days 12:02:17.337
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..................
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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 22, {f00cf, fffff880090da798, fffff880090da000, fffff80002fad0bf}

Probably caused by : MDFSYSNT.sys ( MDFSYSNT+6ec4 )

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

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

FILE_SYSTEM (22)
Arguments:
Arg1: 00000000000f00cf
Arg2: fffff880090da798
Arg3: fffff880090da000
Arg4: fffff80002fad0bf

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x22

PROCESS_NAME:  launchpadremov

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88001829ec4 to fffff80002e79740

STACK_TEXT:  
fffff880`090d97d8 fffff880`01829ec4 : 00000000`00000022 00000000`000f00cf fffff880`090da798 fffff880`090da000 : nt!KeBugCheckEx
fffff880`090d97e0 00000000`00000022 : 00000000`000f00cf fffff880`090da798 fffff880`090da000 fffff800`02fad0bf : MDFSYSNT+0x6ec4
fffff880`090d97e8 00000000`000f00cf : fffff880`090da798 fffff880`090da000 fffff800`02fad0bf 00000000`00000000 : 0x22
fffff880`090d97f0 fffff880`090da798 : fffff880`090da000 fffff800`02fad0bf 00000000`00000000 00000000`00000000 : 0xf00cf
fffff880`090d97f8 fffff880`090da000 : fffff800`02fad0bf 00000000`00000000 00000000`00000000 fffff880`0187cd09 : 0xfffff880`090da798
fffff880`090d9800 fffff800`02fad0bf : 00000000`00000000 00000000`00000000 fffff880`0187cd09 fffff880`01856818 : 0xfffff880`090da000
fffff880`090d9808 00000000`00000000 : fffff880`01848840 fffff880`0186217c fffff880`01865555 00000000`00000000 : nt!ExDeferredFreePool+0x233


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MDFSYSNT+6ec4
fffff880`01829ec4 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  MDFSYSNT+6ec4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MDFSYSNT

IMAGE_NAME:  MDFSYSNT.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a3fef22

FAILURE_BUCKET_ID:  X64_0x22_MDFSYSNT+6ec4

BUCKET_ID:  X64_0x22_MDFSYSNT+6ec4

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

 

[kaoticsolja]

THANKS FOR THE INFO. No I am not using bootcamp. I am just using MACdriver to read info from my external HD

PS I read this on another forum

I ditched MacDrive today, as I kept getting BSOD in XP One on April 8th and one today almost a month apart since i got MacDrive.

the BSOD gave me a MDFSYSNT.SYS (which is a drive for HSF/HSF+/Journaled formatted drives, only one conclusion; macdrive as my first BSOD with it was when i plugged in my external drive with leopard on it and after a fe wminutes of transferring files out of the Leopard drive a BSOD.


I wanted to use it to transfer files from OSX10.4.10 to XP but ill just use my externaldrive; and the only other reason i used it was for my ipod to play itunes music over the system...since it was formatted for MacOSX not Fat32 (doh!) .... i ended up getting a USB wall charger and plugged it into my stereo set on my desk.

goodtogo...no more messing around with macdrive.
junk junk junk!

 

[kaoticsolja]

But is that the reason for all 3 crashes? AND THANK YOU so much for your help

Found another one...ntoskrnl.exe..but it says my symbols are wrong so im not sure

It would seem this ntoskrnl.exe is the main problem