System Crash upon Login, Bug Check Code 0x00000024 (NTFS_FILE_SYSTEM)

[LordShadowWing]

I had Logged in with My Password (Which is Stored Via Barcode on a Sheet of Paper) and Immediately the system Halted, Giving the Blue screen with the Bug Check code of 0x00000024. Could it be possible that my problem is caused by not having a Power Supply Unit with a Max Wattage that is Too Small for my system configuration? The Minimum required files are attached. If you need more information Let me know and I will try to provide.

 

[Arc]

BugCheck 24, {1904fb, fffff8800398c478, fffff8800398bcd0, fffff80002c8282e}

Probably caused by : ntkrnlmp.exe ( nt!RtlSubtreePredecessor+12 )

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

BugCheck 1A, {5003, fffff70001080000, 4b56f, 4b57100096a02}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36b56 )

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

As you have uninstalled Norton already, please mark the thread http://www.sevenforums.com/bsod-hel...outube-video-left-15-min-system-rebooted.html as solved before starting another thread.

The versatility of the bugchecks give an idea of a memory corruption. So test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

 

[LordShadowWing]

Memory Test Shows GREEN Across the Board, I'm going to run the system file checker (sfc) and report the results

 

[Arc]

Memory Test Shows GREEN Across the Board, I'm going to run the system file checker (sfc) and report the results

Interesting!! Something that I did not know. Can you take a camera snap of the memory test screen and let us see it? Eager to see it.

 

[LordShadowWing]

When I said that It was GREEN across the board, I was just stating that there were no problems found. And I have already began the sfc /scannow as of 2:21 PM central time the scan is at
51%

EDIT: SFC has Finished Log File Attached

 

[Arc]

When I said that It was GREEN across the board, I was just stating that there were no problems found.

OK then. Good to know that it did not found any issue with the RAM. Now, some driver may pass bad info to the memory which may result in memory corruption too. So enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[LordShadowWing]

Immediate Bluescreen upon reboot after enabling the driver verifier. DM Log Collector Re ran Dump uploaded.

 

[Arc]

Update Brother Serial USB driver from Software Download | Brother
See how it goes.
___________________________________________________

BugCheck C9, {24c, fffff88007503ba0, fffff98009b20b40, 103}

*** WARNING: Unable to verify timestamp for BrSerIb.sys
*** ERROR: Module load completed but symbols could not be loaded for BrSerIb.sys
*** ERROR: Module load completed but symbols could not be loaded for BrUsbSIb.sys
Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : BrUsbSIb.sys ( BrUsbSIb+ba0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
    call to IoMarkIrpPending.
Arg2: fffff88007503ba0, The address in the driver's code where the error was detected.
Arg3: fffff98009b20b40, IRP address.
Arg4: 0000000000000103, Status code.

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


BUGCHECK_STR:  0xc9_24c

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  24c

FAULTING_IP: 
BrUsbSIb+ba0
fffff880`07503ba0 488bc4          mov     rax,rsp

FOLLOWUP_IP: 
BrUsbSIb+ba0
fffff880`07503ba0 488bc4          mov     rax,rsp

IRP_ADDRESS: fffff98009b20b40

DEVICE_OBJECT: fffffa800fa25310

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LOCK_ADDRESS:  fffff80002e91c40 -- (!locks fffff80002e91c40)

Resource @ nt!PiEngineLock (0xfffff80002e91c40)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002e91c40
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000311d4ec to fffff80002c888c0

STACK_TEXT:  
fffff880`039a1118 fffff800`0311d4ec : 00000000`000000c9 00000000`0000024c fffff880`07503ba0 fffff980`09b20b40 : nt!KeBugCheckEx
fffff880`039a1120 fffff800`031275aa : fffff800`0311bb00 fffff880`07503ba0 fffff980`09b20b40 00000000`00000103 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`039a1160 fffff800`0312847e : 00000000`0000024c 00000000`00000103 fffff980`09b20b40 00000000`fffffffd : nt!ViErrorFinishReport+0xda
fffff880`039a11b0 fffff800`0313384f : 00000000`00000001 fffffa80`0f852b90 fffffa80`0f852c48 fffffa80`0f8a9c50 : nt!VfErrorReport6+0x6e
fffff880`039a1280 fffff800`03133c93 : fffffa80`0f852b90 00000000`00000002 fffffa80`0f8a9b00 fffff880`039a12f8 : nt!IovpCallDriver2+0x13f
fffff880`039a12e0 fffff800`03139d5e : fffff980`09b20b40 fffff980`09b20b40 00000000`00000002 fffffa80`0f8a9b00 : nt!VfAfterCallDriver+0x353
fffff880`039a1330 fffff800`0313c65a : fffff980`09b20ee0 fffffa80`0f8a9b00 fffffa80`0f8a98b0 fffffa80`0f852b90 : nt!IovCallDriver+0x57e
fffff880`039a1390 fffff800`03139d46 : fffff980`09b20b40 00000000`00000002 fffffa80`0f8a98b0 fffffa80`0f82ebe0 : nt!ViFilterDispatchPnp+0x13a
fffff880`039a13c0 fffff880`07512c67 : fffff980`09b20b40 00000000`00000001 fffffa80`0fa25460 fffffa80`0f82ebe0 : nt!IovCallDriver+0x566
fffff880`039a1420 fffff980`09b20b40 : 00000000`00000001 fffffa80`0fa25460 fffffa80`0f82ebe0 fffffa80`0fa25310 : BrSerIb+0xbc67
fffff880`039a1428 00000000`00000001 : fffffa80`0fa25460 fffffa80`0f82ebe0 fffffa80`0fa25310 00000000`00000002 : 0xfffff980`09b20b40
fffff880`039a1430 fffffa80`0fa25460 : fffffa80`0f82ebe0 fffffa80`0fa25310 00000000`00000002 fffffa80`0f82c9d0 : 0x1
fffff880`039a1438 fffffa80`0f82ebe0 : fffffa80`0fa25310 00000000`00000002 fffffa80`0f82c9d0 fffff800`03135eb6 : 0xfffffa80`0fa25460
fffff880`039a1440 fffffa80`0fa25310 : 00000000`00000002 fffffa80`0f82c9d0 fffff800`03135eb6 fffffa80`00000000 : 0xfffffa80`0f82ebe0
fffff880`039a1448 00000000`00000002 : fffffa80`0f82c9d0 fffff800`03135eb6 fffffa80`00000000 fffffa80`00000001 : 0xfffffa80`0fa25310
fffff880`039a1450 fffffa80`0f82c9d0 : fffff800`03135eb6 fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 : 0x2
fffff880`039a1458 fffff800`03135eb6 : fffffa80`00000000 fffffa80`00000001 fffffa80`00000000 00000000`00000000 : 0xfffffa80`0f82c9d0
fffff880`039a1460 fffff800`03139d46 : fffff980`09b20b40 fffff980`09b20b40 fffff980`09b20b40 fffff800`031354ae : nt!VfBeforeCallDriver+0x186
fffff880`039a14c0 fffff800`0313c65a : fffff980`09b20f70 fffffa80`0fa25310 fffffa80`0f8aaa20 fffffa80`0f82c9d0 : nt!IovCallDriver+0x566
fffff880`039a1520 fffff800`03139d46 : fffff980`09b20b40 00000000`00000002 fffffa80`0f8aaa20 fffffa80`0f853be0 : nt!ViFilterDispatchPnp+0x13a
fffff880`039a1550 fffff800`02ef2721 : fffffa80`0f8aaa20 fffff880`039a1650 00000000`c00000bb fffffa80`0f853be0 : nt!IovCallDriver+0x566
fffff880`039a15b0 fffff800`0304b057 : fffff880`039a16d0 fffffa80`0cdb0b80 00000000`00000040 00000000`00000000 : nt!IopSynchronousCall+0xe1
fffff880`039a1620 fffff800`0304bc47 : 00000000`00000030 00000000`00000000 fffffa80`0f882890 00000000`00000001 : nt!PpIrpQueryCapabilities+0x87
fffff880`039a16b0 fffff800`03070e10 : ffffffff`800004b0 ffffffff`800004a0 fffff8a0`05d765d0 00000000`00000030 : nt!PnpQueryAndSaveDeviceNodeCapabilities+0x17
fffff880`039a1720 fffff800`03072a34 : fffffa80`0f882890 fffffa80`0f882890 fffffa80`0cdb0b80 00000000`00000001 : nt!PipProcessStartPhase3+0x530
fffff880`039a1810 fffff800`03072ff8 : fffff800`02e8f500 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PipProcessDevNodeTree+0x264
fffff880`039a1a80 fffff800`02d89087 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
fffff880`039a1ad0 fffff800`02c924b5 : fffff800`02d88d60 fffffa80`0cd91601 00000000`00000000 01020001`02000001 : nt!PnpDeviceActionWorker+0x327
fffff880`039a1b70 fffff800`02f22456 : 0e1a050d`18040c17 fffffa80`0cd91660 00000000`00000080 fffffa80`0cd759c0 : nt!ExpWorkerThread+0x111
fffff880`039a1c00 fffff800`02c7a2c6 : fffff880`037d7180 fffffa80`0cd91660 fffff880`037e1fc0 16253716`27391526 : nt!PspSystemThreadStartup+0x5a
fffff880`039a1c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  BrUsbSIb+ba0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BrUsbSIb

IMAGE_NAME:  BrUsbSIb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aef9e3b

FAILURE_BUCKET_ID:  X64_0xc9_24c_VRF_BrUsbSIb+ba0

BUCKET_ID:  X64_0xc9_24c_VRF_BrUsbSIb+ba0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc9_24c_vrf_brusbsib+ba0

FAILURE_ID_HASH:  {795ca866-2d54-8614-dac9-121699bc19b8}

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

3: kd> lmvm BrUsbSIb
start             end                 module name
fffff880`07503000 fffff880`07506900   BrUsbSIb   (no symbols)           
    Loaded symbol image file: BrUsbSIb.sys
    Image path: \SystemRoot\system32\DRIVERS\BrUsbSIb.sys
    Image name: BrUsbSIb.sys
    Timestamp:        Tue Nov 03 08:36:35 2009 (4AEF9E3B)
    CheckSum:         0000DED6
    ImageSize:        00003900
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[LordShadowWing]

The problem is that I have an OLD Brother MFC-8820D Laser Printer. I could have used the Microsoft provided drivers for it, but wouldn't be able to print using the auto duplexing feature, or use the scanning feeder to scan large documents. I had to use a workaround to get that to work (IE: Using the latest Vista Drivers). I am Looking to save money to get a Newer (And physically smaller) Brother Unit. Probably just a simple printer. You have any suggestions?

 

[Arc]

I think you can install XP or vista in Virtualbox and continuously use the printer there.

 

[LordShadowWing]

I think you can install XP or vista in Virtualbox and continuously use the printer there.

The Problem with that is that I don't want to have to open the VM every time I want to print something.
My original question was: Could my smallish power supply (450 Watt) be causimg my issues?
IE: By not providing enough power for my system.

 

[Arc]

450 watts is really inadequate. It may cause various issues.

But an incompatible printer driver is the issue at its own, irrespective of the wattage of the power supply.