Windows 7 x64 Crashes on Startup When Powering On System

Also, I don't know why the computer just arbitrarily decided to change it to the Windows version RAID driver. I NEVER asked it to do that, and neither did my boyfriend.

 

Don't know if anyone reads this anymore, but I finally got to update the RAID driver. Did that and still had BSODs. Here is the BSOD info.

==================================================
Dump File : 071611-25396-01.dmp
Crash Time : 16/07/2011 4:56:06 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0105e99b
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`05d98018
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+499b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\071611-25396-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 269,848
==================================================


On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-25396-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x499B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltIsCallbackDataDirty+0x20AB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


I can also provide event logs if needed.

This is what I read about the file:
FltMgr.sys is a “system” file used by Windows to help control various aspects of your hard drives & files. Its official name is the “Microsoft Filesystem Filter Manager” and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted. The fltmgr.sys error is caused when Windows cannot read or process files that are on the hard drive, usually because the File System Manager is damaged or unreadable. If this is the case, it can cause hard drives to stop working and the blue screen to appear.

 

When did this latest BSOD occur? Examples of answers I'm looking for:

• While the computer is booting up (Before I even get to the desktop)
• When I play ____ game
• When I open ____ program
• When I try to open ____ folder

 

Does this file exist - C:\Windows\memory.dmp ? If so, what size is it?

What about this one - C:\Windows\Minidump\071611-25396-01.dmp ? If it does exist, please copy it to your Desktop, zip it then attach the resulting zip.

Oh, do you have some kind of auto-cleaning program running at boot?

 

While the computer is booting. It is always while it is booting. Never during usage.

 

I don't see any kind of auto-cleaning program on the computer.

Here's the dump file.

 

Does this file exist - C:\Windows\memory.dmp ? If so, what size is it?

I read information on your thread elsewhere that's not been offered here. I see little point in you jumping between forums and picking and choosing which tests you should run or which questions you should answer.

We're all giving our free time to try to help you out and from what I can see, it doesn't look like anyone has been given enough respect for the time and effort that's been allocated to you thus far.

I wouldn't point the other forum over here, the witticisms about the 'Usual causes' might not go down too well as the author of, or a major contributor to, those pages is likely to be involved in trying to help you there.

So your system wasn't reliable with similar errors, yet:

I suggest you test the RAM that I've already pointed out isn't on the QVL for this 'board (the other forum is still waiting for this too); then re-read my comments and suggestions in #36 and follow them up.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800105e99b, 0, 5d98018}

Probably caused by : fltmgr.sys ( fltmgr!FltpPassThroughInternal+3b )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800105e99b, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000005d98018, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltpPassThroughInternal+3b
fffff880`0105e99b 80780802        cmp     byte ptr [rax+8],2

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000005d98018

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbc100
 0000000005d98018 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800338b220 -- (.trap 0xfffff8800338b220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000005d98010 rbx=0000000000000000 rcx=fffff8800338b400
rdx=fffff8800107c450 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800105e99b rsp=fffff8800338b3b8 rbp=0000000000000000
 r8=fffffa8005d98118  r9=fffffa8005d98010 r10=fffffa8005e7d860
r11=fffffa8005d98160 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
fltmgr!FltpPassThroughInternal+0x3b:
fffff880`0105e99b 80780802        cmp     byte ptr [rax+8],2 ds:0010:00000000`05d98018=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad85d8 to fffff80002a8cd00

STACK_TEXT:  
fffff880`0338a998 fffff800`02ad85d8 : 00000000`0000001e ffffffff`c0000005 fffff880`0105e99b 00000000`00000000 : nt!KeBugCheckEx
fffff880`0338a9a0 fffff800`02a8c382 : fffff880`0338b178 fffffa80`05e7d860 fffff880`0338b220 fffffa80`04c0f010 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0338b040 fffff800`02a8aefa : 00000000`00000000 00000000`05d98018 00000000`00000000 fffffa80`05e7d860 : nt!KiExceptionDispatch+0xc2
fffff880`0338b220 fffff880`0105e99b : fffff880`0107c2a3 fffffa80`04a6f8e0 fffffa80`05e7d860 fffffa80`05e7d860 : nt!KiPageFault+0x23a
fffff880`0338b3b8 fffffa80`00000000 : fffff880`0338b3f0 fffffa80`0012000e fffff880`0105e932 fffffa80`04c0f010 : fltmgr!FltpPassThroughInternal+0x3b
fffff880`0338b3e8 fffff880`0338b3f0 : fffffa80`0012000e fffff880`0105e932 fffffa80`04c0f010 fffffa80`05e7d860 : 0xfffffa80`00000000
fffff880`0338b3f0 fffffa80`0012000e : fffff880`0105e932 fffffa80`04c0f010 fffffa80`05e7d860 fffffa80`05d98010 : 0xfffff880`0338b3f0
fffff880`0338b3f8 fffff880`0105e932 : fffffa80`04c0f010 fffffa80`05e7d860 fffffa80`05d98010 ffffffff`ffffffff : 0xfffffa80`0012000e
fffff880`0338b400 fffffa80`04c0f010 : fffffa80`05e7d860 fffffa80`05d98010 ffffffff`ffffffff 00000000`00000000 : fltmgr! ?? ::FNODOBFM::`string'+0x2
fffff880`0338b408 fffffa80`05e7d860 : fffffa80`05d98010 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfffffa80`04c0f010
fffff880`0338b410 fffffa80`05d98010 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`05e7d860
fffff880`0338b418 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06579790 : 0xfffffa80`05d98010
fffff880`0338b420 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`06579790 fffffa80`05e7d860 : 0xffffffff`ffffffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fltmgr!FltpPassThroughInternal+3b
fffff880`0105e99b 80780802        cmp     byte ptr [rax+8],2

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  fltmgr!FltpPassThroughInternal+3b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929c

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_fltmgr!FltpPassThroughInternal+3b

BUCKET_ID:  X64_0x1E_c0000005_fltmgr!FltpPassThroughInternal+3b

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

I'm not very good at debugging so I may have the following completely wrong, what I did was try to check what was at the address that is contained in Parameter 4:

Code:

0: kd> dd 5d98018
00000000`05d98018  ???????? ???????? ???????? ????????
00000000`05d98028  ???????? ???????? ???????? ????????
00000000`05d98038  ???????? ???????? ???????? ????????
00000000`05d98048  ???????? ???????? ???????? ????????
00000000`05d98058  ???????? ???????? ???????? ????????
00000000`05d98068  ???????? ???????? ???????? ????????
00000000`05d98078  ???????? ???????? ???????? ????????
00000000`05d98088  ???????? ???????? ???????? ????????

No one has suggested that you should skip over anything, it's written that way for completeness and could mean that those unproven may have been from other causes but the OP didn't complete the troubleshooting or report back, perhaps just formatted or scrapped it.

 

I'm sorry, I'm not trying to be "disrespectful," I'm actually extremely, extremely busy. I get different test suggestions from other people, on other forums, I try to complete those steps, change certain settings, do another test on another forum, and all of these things I'm trying to remember to do all while moving into a new apartment. Most of the time, he's using the computer, so I only have a fraction of time to mess around with it, before I allow him to get back on it to play games or whatever before he goes to his job, and I have to go back to moving and organizing.

I'm not TRYING to ignore tests. There are a lot of things I'm trying to do at once here, and not having a huge amount of time to make changes on his computer leaves me with open gaps and holes in the tests I'm asked to do or changes I have to make. I haven't even done a memtest on both of his RAM sticks yet because I just have not had time.

"this problem that he has" means the problem I originally posted about. The system crashing on startup. Mine did not do that, but it did have crashes. My motherboard died before I could fix them all. But he has different crashes than I do, aside from the ahcix64s crashes.

It's not there. Sorry, I wasn't trying to ignore you. I'm multi-tasking in a very big way.

Again, I'm very appreciative of anyone who helps me. If you're talking about the way I responded to your explanations of the bug checks I provided, I knew that there was no way to really tell what was going on with them until I could get a dump file made explaining the crashes. It was helpful to know a short list of things that could cause those errors, but I knew that I'd have to probably post a dump file or crash info the next time I posted.

I'm not choosing. I'm answering as many as I can with the time I have. I may have a quick glance at someone's post that catches my eye and I think I have to answer them while I have time, or if I'm in between moving, or awake late at night when I'm done with everything. You're going to have to be patient with me if I don't answer you right away, or I don't perform your test immediately. Things are hectic around here.

I don't mean to sound rude, disrespectful, or cold. I'm more than grateful for the help anyone gives me, even if you don't have any rock solid information. I'm trying to provide as much information as I possibly can to everyone who is helping me, and at the same time, move. So don't take things the wrong way.

As of right now, I have to try to remember to run a memtest on both of his RAM sticks at once when I get the chance to. Probably when we move the computer to the new apartment. If the tests reveal anything, do you need me to post them here?

 

I'm sorry, Memory.dmp really is there, I just didn't notice it before. I was in a hurry and looking for a folder by that name, not a file.

Memory.dmp is there, and it's 242 MB in size.

I also booted straight to the Memtest disc, and rebooted from it. It started up clean first try after that reboot. I did it again a second time, same thing. I guess no matter what, if I boot from something other than the HDDs the first time powering on, it'll work if I reboot to Windows.

 

Why don't you volunteer some rock-solid information to the helpers on the other forum?

Like the fact that your RAM isn't on the QVL for the motherboard, little things like that might stop that thread from reaching the 200 mark.

 

Why don't you stop stalking me? It's really creepy.

I've read some other forums with people using the same RAM on my motherboard and not having a problem with compatibility. If it does end up being a compatibility issue, I'll deal with it accordingly. If it's not, I'll deal with that, too. Right now it could be any number of things. If you have some sort of problem with me getting help elsewhere, I honestly don't know what to tell you, and I don't understand why it hurts you so much. I'm sorry, but you should really just let it go and help some other people if you have a problem with me.

 

When an OP contains:

and you've spent hours trying you drag out pertinent information, it feels kinda personal, like you want to get the problem fixed, you know? It's not like either of us was unaware that the other knew of the other thread, was it?

So, you don't want to try to help out your current helpers, that's your perogative. I'm outta both of them, good luck.

 

Wow. I apologize for ever wasting my time in your thread, and won't be contributing any more to not being any help to you, like everyone else is.

I'm not sure what you define as "stalking", but if it means dedicating himself to helping you without as much as a truly meant thanks, then I suppose you should call the authorities. I mean man, you mention in your first post that you're filling up forums left and right with your computer issue, so God forbid anyone would want to see what happened in those.

Meanwhile, maybe in the future you could leave out your emotional complex and homosexuality, as neither really has anything to do with coming up with solutions to computer issues.

 

Look, this is a computer forum. You guys are treating me as if I'm not trying to fix the problem simply because of... I... honestly have no idea. I guess because other people are helping me and you guys aren't? I just have no idea what's wrong here. Your behavior is perplexing. I'm not here to enter in a "whose dick is bigger" contest. I'm trying to fix my boyfriend's computer. That's all I'm trying to do, and I just got bad attitudes from all corners here.

He wasn't trying to help, though. He was following my threads to see whether or not he was right and I was wrong, so he could feel good about himself, so he could say "I told you so" and feel important. And I never told him where the forums were. After he stopped responding to me here, and stopped helping me HERE, he went and found my other forums and then acted like a jerk here. If he actually wanted to help, he'd be less of a dick about it. I did what I could here, and so did the others, and if they couldn't help me, they couldn't help me. What I don't understand is, if they don't know exactly what the problem is and can't help me with it, they get incredibly sensitive. I don't know what to say, it's just strange, very strange. You guys can't take things so personally if you're running a computer tech forum. IF you're running it, I don't even know.

No, everyone HAS been helping me, and I appreciate their help. I appreciated the help here, too, but it seemed more like a festering breeding ground for egos here than anything. When I had very little info to give, I got some guesses to what the problem was. When I had more substantial information, no one seemed to care, at all. They were too busy feeling "wronged" that I didn't do... whatever it was they thought I should do. Worship them? I don't know.

When I said before that I've gotten little help elsewhere, that was before I started a whole new forum somewhere else where I've gotten many responses and lots of help. They've been very helpful and I've been very thankful. And just because I get help from there doesn't mean people from this forum need to go searching every page of what I say, how I say it, and whether or not I'm doing what they asked me to, and when I don't mention the thing they told me, they post here after a few days of silence while being as big of an *** as possible! It's WEIRD! VERY WEIRD! It's not "being helpful," it's being a dick.

I really, really don't know what else to say to you guys. I mean, I'm sorry you couldn't help me, and I'm sorry you feel as if you should attack me because of it, and then I have to take ridiculous measures like these such as explaining myself on some forum that isn't even about things like this. If this is such a big problem for you, have this forum taken down, and just move on, it's that simple. Or you could continue to post here about our emotional issues and whether or not you should help me or whether or not I'm responding harshly or whether or not you're just coming off as obsessive creeps.

Whoa. I think that may just be even stranger than being followed on the other forums. I never got emotional here, not once, until Mr. Sensitive decided I was being "disrespectful" even though I definitely wasn't. I guess he wanted me to kiss his *** a bunch of times every time he posted a response. Is that how things go here, because, wow. Maybe it's time for a change.

And I don't know where this "homosexual" thing comes from. I'm female... I never once said I was a guy.

YOU'RE RIGHT. IT HAS NOTHING TO DO WITH FIXING A COMPUTER. Then why are you posting in response to me when it has nothing to do with fixing a computer?! If you want to help people fix their computers, have this forum taken down or something, and go the help people who need it instead of focusing on me. And if you ARE helping others, great, continue to do so. That's all I ask. Help THEM. Stop talking to ME.

 

I'm not going to bother quoting you, because this isn't a forum for flame war type of things, and unlike satrow appears to be, I'm not upset. Besides, I can get my point across without pointing at things you said. I hope you feel better after your little rant, at least.

All I've done in this thread is waste my time. I believe satrow feels the same way. Neither of us "run" the forum. There's two owners of this forum, and they definitely aren't us.

Almost everything you've been asked to do/provide has had to be repeated several times, and even then there's things you haven't done/provided in order to get help here. That's on you. Yeah, I realize troubleshooting can be a lot of work. I do it myself all the time.

I don't speak for people, but I can speak for what I've seen. What I have seen is that satrow spends a good deal of time on this forum helping, or at least trying to help, people. I'm somewhat the same way, though I think I've learned more on this forum, than helped (so far). Satrow's patience doesn't go forever, though, and you frustrated him (and others) to the point of not feeling appreciated, etc. His responses are his responsibility, but you pushed him to that point as well. I don't think making one person out to be a bad guy here is the way to handle things.

So I got your gender wrong. As you seemed to have more computer knowledge than the average novice poster on this forum when you started this thread, I Googled your screen name to see if I could figure out who you were (I say "seemed", because you know far less than I had hoped... nothing wrong with that, but it could've been easier if you could figure out how to get the memory dumps and etc.). The only results I was able to find was some bisexual emo guy, so I figured that was you. Maybe it is... maybe it isn't... your gender isn't important and your relationship to the guy with the troublesome computer isn't important. MY POINT was that in my opinion you mentioned it far more than should be necessary to get help. Again, my view. I don't hate gay people or anything, but it seemed like the lovey dovey thing was just beginning to permeate the thread. It still does.

I do hope you get the computer fixed (unless you already have). If you don't like the way this forum works, then simply leave. No one asked you to stay, and there's plenty of other people coming and going. This forum seems to have a unique vibe that I've adapted to. Some people can't adapt to it... oh well.

Lastly, I was (and am) responding to you without focusing on fixing a computer, because as I already stated, I'm done with that aspect with you.

EDIT: If you'd like to keep going back and forth about why and how and personalities and hate and ETC... probably best to start a new thread in a more appropriate subforum on MG, such as the Lounge.

 

Thank you for responding more maturely than before.

Lastly, I only want to say thank you for your time, whether or not you thought in the end that I deserved it. Don't get me wrong. I appreciate everyone's help. But that doesn't stop me from defending myself when people get a little too touchy for my liking.

I'm sorry it didn't work out, and I'm sorry you wasted your time. That wasn't my intention to any of you. I'm sorry to Satrow, too, even though I'm still really confused about what went wrong.

I won't bother you guys any longer, just as long as you don't bother me, now. Good luck in helping some people with their problems, and don't let this whole issue get to you.

Farewell.