BSODs Just Starting!

[imacken]

After many months of no problems, in the last 2 or 3 weeks, I'm getting BSODs about once a day.

The minidump says:

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

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b28a230 -- (.trap 0xfffff8800b28a230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000006ecda80 rbx=0000000000000000 rcx=fffffa80063cd4f0
rdx=fffffa8006ec6d80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800b28a4d0 rsp=fffff8800b28a3c8 rbp=fffffa80054ec040
r8=fffffa80063cd7b0 r9=0000000000000012 r10=fffffa80055397d0
r11=fffffa800927e880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff880`0b28a4d0 60 ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b54e9f to fffff80002ad5f00
STACK_TEXT:
fffff880`0b28a0c8 fffff800`02b54e9f : 00000000`000000fc fffff880`0b28a4d0 80000001`b5a08963 fffff880`0b28a230 : nt!KeBugCheckEx
fffff880`0b28a0d0 fffff800`02ad3fee : 00000000`00000008 00000000`00000000 fffffa80`00000000 fffffa80`09030240 : nt! ?? ::FNODOBFM::`string'+0x42567
fffff880`0b28a230 fffff880`0b28a4d0 : fffff880`0b28a600 00000000`00000000 fffff880`00000080 00000000`00000007 : nt!KiPageFault+0x16e
fffff880`0b28a3c8 fffff880`0b28a600 : 00000000`00000000 fffff880`00000080 00000000`00000007 fffff880`00000001 : 0xfffff880`0b28a4d0
fffff880`0b28a3d0 00000000`00000000 : fffff880`00000080 00000000`00000007 fffff880`00000001 fffffa80`0927e880 : 0xfffff880`0b28a600

STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42567
fffff800`02b54e9f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42567
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
Followup: MachineOwner

Does anyone know what this means?

The only real software/hardware change has been Office 2010 Beta install.

Thanks.

 

[zigzag3143]

After many months of no problems, in the last 2 or 3 weeks, I'm getting BSODs about once a day.

The minidump says:

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

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b28a230 -- (.trap 0xfffff8800b28a230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000006ecda80 rbx=0000000000000000 rcx=fffffa80063cd4f0
rdx=fffffa8006ec6d80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800b28a4d0 rsp=fffff8800b28a3c8 rbp=fffffa80054ec040
r8=fffffa80063cd7b0 r9=0000000000000012 r10=fffffa80055397d0
r11=fffffa800927e880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff880`0b28a4d0 60 ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b54e9f to fffff80002ad5f00
STACK_TEXT:
fffff880`0b28a0c8 fffff800`02b54e9f : 00000000`000000fc fffff880`0b28a4d0 80000001`b5a08963 fffff880`0b28a230 : nt!KeBugCheckEx
fffff880`0b28a0d0 fffff800`02ad3fee : 00000000`00000008 00000000`00000000 fffffa80`00000000 fffffa80`09030240 : nt! ?? ::FNODOBFM::`string'+0x42567
fffff880`0b28a230 fffff880`0b28a4d0 : fffff880`0b28a600 00000000`00000000 fffff880`00000080 00000000`00000007 : nt!KiPageFault+0x16e
fffff880`0b28a3c8 fffff880`0b28a600 : 00000000`00000000 fffff880`00000080 00000000`00000007 fffff880`00000001 : 0xfffff880`0b28a4d0
fffff880`0b28a3d0 00000000`00000000 : fffff880`00000080 00000000`00000007 fffff880`00000001 fffffa80`0927e880 : 0xfffff880`0b28a600

STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42567
fffff800`02b54e9f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42567
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
Followup: MachineOwner

Does anyone know what this means?

The only real software/hardware change has been Office 2010 Beta install.

Thanks.

Hi and welcome


We really need the actual dump file. use these to find and upload it. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks

Ken J+

 

[imacken]

Thanks. Zip file attached.

 

[imacken]

Here is one that happened during the night last night when my PC was asleep!

Anyone?

 

[Tews]

Your dmp file shows critical structure corruption.. This is most likely non recoverable.. back up your data and perform a clean install...

View attachment 47906​

 

[imacken]

Aarghh!!! Is this the only way? I can't face another reinstall at the moment.

 

[usasma]

More info on the STOP 0xFC error: BSOD Index
- Most instances are caused by device drivers
More info on the STOP 0x109 error: BSOD Index
- Usually either a device driver or a RAM (hardware error)

Start with these diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Next, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

adfs.SYS     Mon Nov 03 11:48:14 2008 - Adobe File System
ASACPI.sys   Mon Oct 30 22:09:12 2006 - Asus ATK0110 ACPI Utility (also found in PCProbe and AISuite)
iaStor.sys   Fri Sep 12 16:46:00 2008 - Intel Storage Matrix driver

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 15 05:17:41.062 2010 (GMT-5)
System Uptime: 1 days 18:40:07.952
BugCheck FC, {fffff8800b28a4d0, 80000001b5a08963, fffff8800b28a230, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42567 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 15 22:30:28.835 2010 (GMT-5)
System Uptime: 0 days 17:11:21.614
BugCheck 109, {a3a039d89aa515a3, 0, 500ec59242aa3f10, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

Then, because this is most likely a device driver issue - please run Driver Verifier according to these directions:

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).

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"
- 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.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[imacken]

Thanks a lot for that.
I have 4 identical 500Gb WD SATA drives. 2 are used by Windows and the other 2 by a different OS.
I have run the WD diagnostics (within Windows version) from the links you recommended, aand something weird is going on.
When I run WD's DLG for Windows, select either of the 2 Windows drives, run the test, I get an error that says 'Cable Test: Write sector error, cable test failed'!
If I run it on the other 2 drives (non-Windows) then everything is OK.
Any ideas?

 

[imacken]

usamama,
I've done the following:
1) updated the 3 drivers you highlighted
2) ran MEMTEST with no problems at all for about 3 hours
3) couldn't get the Western Digital CD-bootable HD diagnostic to run. CD boots up, says something about Carella (or something simialr) DR-DOS, then I just get a blank screen
4) see post above about WD Windows Diagnostic not working.
5) ran the malware ActiveScan. It seemed to come up with about 21 infections which I am very suspicious of as MSE doesn't find anything, and neither does Norton NIS.
I'm going to try the Driver Verifier now.

 

[usasma]

Do you have both MSE and Norton installed? If so, get rid of one IMMEDIATELY!!!
As for the 21 infections - what are they? If they're cookies, it's not a problem.
The hard drive tests worry me, try the Hitachi Drive Fitness Test (the Advanced test) on each drive.

 

[imacken]

Thanks. I just use MSE. I only temporarily put Norton on to see if it picked up any of the things that ActiveScan was complaining about.
I'll try the Hitachi test and report back.
Problem hasn't occurred since updating the 3 drivers, though. Fingers crossed!

 

[imacken]

Don't know what's going on here, but I can't get the Hitachi DFT to run either! Both the WD and Hitachi CDs seem to boot OK, then I just get a blank screen and the system reboots and repeat ad nauseum.
BTW, running Verifier came up with nothing. Literally! I ran it as you suggested, system rebooted OK with no messages - nothing.

 

[computersplus]

sounds like to me that Bios SATA controller is set to AHCI try it on IDE

 

[imacken]

Yes, of course! Thank you. I should have thought of that as I have had this issue in the past.

Hitachi DFT works OK now and didn't report any errors on the boot drive.

A weird thing though. I came home to find a BSOD on my screen from what I think was 'Verifier' saying that 'IO Manager has detected a violation by a driver that is defective - WmBEnum.sys'.

Don't understand that as it is a Logitech driver that shouldn't cause any problems.

Any ideas?

 

[computersplus]

did you change fro AHCI to IDE if so I would reinstall now

 

[imacken]

I did to run the diagnostic software, but I'm back on AHCI now.

I thought we were going through all this to try and avoid the reinstall.

 

[computersplus]

if you installed with AHCI it could have caused corruption I would set it to IDE and reinstall that's my opinion

 

[imacken]

Thanks again.

Why would that be, out of interest?

I've been running the betas, various interim builds, RC and the retail W7 for over a year now I guess, on AHCI, and this hasn't been a problem until the last 2-3 weeks. No hardware changes at all in the last 3 months.

What is the issue with AHCI?

 

[computersplus]

the issue with AHCI is it just seems to not work correctly in a lot of cases

 

[imacken]

OK, guys.
Still using AHCI, and there have been no problems for the last day or so.
One weird thing though, if I change the BIOS to EIDE from AHCI, then Windows just will not boot. I get a blue screen, then the 'startup repair' screen after that. Doesn't ever boot. When I change BIOS back to AHCI, everything is OK again.
What is going on there?