Solved Windows crashes on startup only when powering on system

[pooch]

Okay, well, I plugged the optical drive back in, and I got a BSOD while Windows was starting up.

STOP 1E
fltmgr.sys

Ok then we have the culprit, are the SATA ports 5 and 6 set to IDE?

 

[MelancholyRose]

Yup, they sure are.
Luckily, I enabled Kernel dump recently instead of small memory, and it caught the BSOD info so that I can post it here now.

==================================================
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
==================================================


[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x499B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr!FltIsCallbackDataDirty+0x20AB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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:
[/FONT]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.

Some places are saying that old drivers can cause this to happen, but I don't know what drivers he has that are outdated, they're all up-to-date as far as I know. Will Driver Verifier determine that?

 

[pooch]

I have asked for one of the BSOD experts to have a look, did you update your chipset drivers? also on that site are many other drivers for your MB it would probably help to download and install all updates that you have not yet done, as I do at least understand the bit about the BSOD maybe being caused by a driver problem.

 

[MelancholyRose]

I didn't update chipset drivers yet. I'll have to do that later, I'm about to go take care of a few things. I'll check back here later.

 

[Jonathan_King]

Hello,

Try running Memtest86 on all sticks at the same time, immediately upon powering on after a break. No need to run for too long, 5-10 minutes should be plenty for what we are testing for.

 

[MelancholyRose]

Ran Memtest after a power on after a long break. Nothing happened. Everything was fine.

I've uploaded the dump file for this particular crash if it'll help. It's on SkyDrive here:
https://skydrive.live.com/?cid=e4de9a8be33ed49b&sc=documents&uc=1&id=E4DE9A8BE33ED49B!126#

It's inside the zipped folder.

I'm going to post some pictures of my wiring inside his case, and of the screen running the Memtest. Maybe there's something you can learn from these that I just can't see. But when looking at his wiring, all looked fine, as well as the Memtest. I'll do that when I get a chance, we're now in the new apartment we moved in to, but we don't have a router yet, so we can only use internet on one computer at a time.

Note: when I rebooted from Memtest the computer started up just fine the first time. It didn't crash the first time starting up when it rebooted. So I guess if something else is booted first before Windows, and I restart from it, Windows will start just fine.

 

[MelancholyRose]

I just received another BSOD this morning when trying to power on again. Well, my boyfriend powered it on. It caught the dump file again and it involves the file cng.sys, stop error 3B, SYSTEM_SERVICE_EXCEPTION.

[FONT=Segoe UI, Arial]On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-23836-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cng.sys[/FONT] (cng+0x85AD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\cng.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cng.sys[/FONT] (cng!SslImportKey+0x3A5D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\drivers\cng.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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

Here's the original dump file. I attached it in a zip.
[/FONT]

 

[MelancholyRose]

And I tried updating the chipset drivers but it just looks like it's trying to update graphics drivers. The graphics driver is up to date. Is there something else that the chipset driver updates besides graphics? Or do I have to uninstall graphics driver, then install chipset, then update graphics? Kind of a pain, but if that's what I have to do, I'll do it.

 

[essenbe]

If you haven't yet, try running a system file checker that will check and try to repair any damaged system files. Open an elevated command prompt(start button-type cmd in search box-right click on cmd and select run as administrator) in the command window type or copy/paste sfc /scannow it will take a few minutes and will either verify the integrity of system files or give you an error log.

 

[MelancholyRose]

I've done that already. It found nothing wrong.

I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.

Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.

I know that ntoskrnl pops up in a LOT of these, too.

 

[MelancholyRose]

I figured I'd also upload a report of all of the drivers on the system, because, I really don't know what else to do here.

 

[essenbe]

I've been through this before and understand your frustration. Jonathan helped me for quite some time, he's really good. One thing he taught me is that when the system can't find what to blame it on, it blames it on ntoskrnl. And, if the system files are not corrupted, which sfc says they are not, it is an extreme rarity that a Microsoft driver will cause a bsod.

 

[pooch]

And I tried updating the chipset drivers but it just looks like it's trying to update graphics drivers. The graphics driver is up to date. Is there something else that the chipset driver updates besides graphics? Or do I have to uninstall graphics driver, then install chipset, then update graphics? Kind of a pain, but if that's what I have to do, I'll do it.

You can leave the graphics drivers installed, The chipset is something else and it just looks like it is for the graphic card, look carefully on the first ATI screen and you will notice chipset drivers is written on the top of it. AMD and ATI work very closely together

 

[MelancholyRose]

I've been through this before and understand your frustration. Jonathan helped me for quite some time, he's really good. One thing he taught me is that when the system can't find what to blame it on, it blames it on ntoskrnl. And, if the system files are not corrupted, which sfc says they are not, it is an extreme rarity that a Microsoft driver will cause a bsod.

Hm, so even the system doesn't really know what's causing it? That IS pretty frustrating. What can you do then if not even the system knows? I'm not sure what else it could be when I've tested for everything else.

What ended up being the cause when you had this problem?

You can leave the graphics drivers installed, The chipset is something else and it just looks like it is for the graphic card, look carefully on the first ATI screen and you will notice chipset drivers is written on the top of it. AMD and ATI work very closely together

Ah, okay. Then I'm just silly >.< Thank you.

 

[pooch]

I think you should run CHKDSK on your drive I know what you wrote before and I disagree with not being able to run it on a RAID0
Have you made a backup of your RAID drive?

 

[MelancholyRose]

No, I haven't. I don't have any discs to burn the microsoft image file to. I haven't had much time to go buy any. I also don't have another drive on me right now.

I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.

 

[pooch]

No, I haven't. I don't have any discs to burn the microsoft image file to. I haven't had much time to go buy any. I also don't have another drive on me right now.

I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.

I have seen references in the internet about not running CHKDSK on a RAID These references are as far as I am concerned totally wrong. I use CHKDSK and my system comprises of 2 x RAID 0.
I doubt very much that running a CHKDSK is to blame for your problems, but if you ran it before and are reluctant to do it again that is OK by me.

 

[MelancholyRose]

Well if you use it all the time and have no problems, then I'm a little more comfortable. I thought people were speaking from experience, like they had corrupted their registry from using it on RAID. I'll try it out.

Further note. I updated chipset drivers. Still crashed. However, I've been noticing something. On the first power on, it'll get as far as the log in screen, but for some reason the log in screen's resolution is lowered, as if the display driver stopped. The cursor is really large like it is in safe mode. It'll reach the password screen, glitch, hang, and make a buzzing sound. The ntoskrnl BSOD followed immediately afterward. I'm going to put my graphics card into his machine and see if it works. I may also supply his a different power cord, just in case there might not be enough power getting to the card.

 

[MelancholyRose]

I tried replacing the power cord for the graphics card and there were no changes. It still crashed. I got some whole new error types, though.

[FONT=Segoe UI, Arial]On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-28204-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
Bug check description: This indicates that invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 22/07/2011 7:56:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-18033-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0x1D555C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600028555C, 0xFFFFF88003A7C060, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
[/FONT]
So, I don't think his graphics card is to blame. I could try swapping my own RAM into his machine and see if it helps. I don't know if it could still be RAM despite the test coming back clean.

At this point I guess it's pointless posting BSODs, since they're completely random and they never really explain anything, because they're all different.

 

[MelancholyRose]

Could it be my PSU? Is it possible that it's not giving enough juice to my CPU/Mobo?