Frequent BSOD and rebooting, memory dump?

[NoelDP]

This is not a 'preferred scenario' - as if you needed to be told!
I'm not sure where to go from here - bear with me, and I'll call in the troops, and do some research.

 

[IronChief]

Has a solution been found to this problem yet? I'm still getting random BSOD->restarts =/. Thanks in advance.

 

[koolkat77]

Upload the dumps so we can check.

 

[IronChief]

Done.

 

[koolkat77]

Were there no BSOD-s after 22-11-12? You got just one recent one on 6-12-12?
Upload a screenshot of Summary tab using Speccy:

• Speccy - System Information - Free Download
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

This dump files comes yet again with bugcheck 24.

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880093fc7d8, fffff880093fc030, fffff880012e6c73}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880093fc7d8
Arg3: fffff880093fc030
Arg4: fffff880012e6c73

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


EXCEPTION_RECORD:  fffff880093fc7d8 -- (.exr 0xfffff880093fc7d8)
ExceptionAddress: fffff880012e6c73 (Ntfs!NtfsFcbTableCompare+0x0000000000000003)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880093fc030 -- (.cxr 0xfffff880093fc030)
rax=0780000000000552 rbx=030104fffff8a000 rcx=fffffa800788e640
rdx=fffff880093fcb10 rsi=fffff880093fcb10 rdi=fffffa800788e640
rip=fffff880012e6c73 rsp=fffff880093fca18 rbp=fffff880093fcae0
 r8=030104fffff8a020  r9=0000ffffffffffff r10=fffff88001290180
r11=fffff880093fcb58 r12=fffff880093fcbb4 r13=0000000000000000
r14=fffffa800788e180 r15=fffffa800788e180
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs!NtfsFcbTableCompare+0x3:
fffff880`012e6c73 498b08          mov     rcx,qword ptr [r8] ds:002b:030104ff`fff8a020=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  PMB.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003312100
GetUlongFromAddress: unable to read from fffff800033121c0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsFcbTableCompare+3
fffff880`012e6c73 498b08          mov     rcx,qword ptr [r8]

FAULTING_IP: 
Ntfs!NtfsFcbTableCompare+3
fffff880`012e6c73 498b08          mov     rcx,qword ptr [r8]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8000310c4bd to fffff880012e6c73

STACK_TEXT:  
fffff880`093fca18 fffff800`0310c4bd : fffff880`093fcb58 fffffa80`078758c0 00000000`00000001 fffffa80`0a74a640 : Ntfs!NtfsFcbTableCompare+0x3
fffff880`093fca20 fffff800`0310c535 : fffff880`093fcb90 fffffa80`06bcfab0 fffffa80`06ba3501 fffff880`093fcb10 : nt!FindNodeOrParent+0x3d
fffff880`093fca50 fffff880`012e51a9 : 07800000`00000552 00000000`00000000 fffff8a0`0f6008e0 fffff880`012e1e55 : nt!RtlLookupElementGenericTableFullAvl+0x15
fffff880`093fca80 fffff880`012b6d8b : fffffa80`06ba3500 fffffa80`0788e180 fffffa80`06ba3500 07800000`00000552 : Ntfs!NtfsCreateFcb+0x79
fffff880`093fcb60 fffff880`012db179 : fffff880`0928c270 fffffa80`06bcfab0 fffffa80`06ba3500 00000000`00000000 : Ntfs!NtfsOpenFile+0x1cb
fffff880`093fcd50 fffff880`01243a3d : fffffa80`06ba3500 fffffa80`06bcfab0 fffff880`0928c270 fffffa80`0a74a600 : Ntfs!NtfsCommonCreate+0xc49
fffff880`093fcf30 fffff800`030dacb7 : fffff880`0928c1e0 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`093fcf60 fffff800`030dac78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0928c0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsFcbTableCompare+3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff880093fc030 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFcbTableCompare+3

BUCKET_ID:  X64_0x24_Ntfs!NtfsFcbTableCompare+3

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

Unplug your HDD and see if you're getting BSOD-s. How old is this HDD btw? and is windows installed on the HDD or SSD?

Make a scan with Windows Defender offline:

• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Post back results.

 

[IronChief]

Ran the scan, it didn't seem to detect anything. Here's the pic from the speccy program, and also received a BSOD two separate times when I tried to run a movie. Attached the dumpfiles.

 

[koolkat77]

Will take a look at them.


Hard drive test both short and long with:

• SeaTools for Windows

DOS version of Seatools:

• SeaTools for DOS
• SeaTools for DOS tutorial

 

[IronChief]

And done.

 

[koolkat77]

Good. What about Seatools for DOS? And this part:

Unplug your HDD and see if you're getting BSOD-s. How old is this HDD btw? and is windows installed on the HDD or SSD?

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:info: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

 

[IronChief]

Ran memtest overnight for 8 passes, there were 0 errors. Unplugged my HD and seeing if I get the random BSOD's restarts. I'll get back to you in a day or two, or if my computer decides to randomly restart again. Thanks.

 

[IronChief]

Day 1 Update: I took out my other hard drive and left my computer running. Normally I would have had a restart/BSOD by now. I feel you are probably right about it being the hard drive. Will be sure after another day or two.

 

[koolkat77]

Not a day or two.. Give it a week or week(s) sometimes they come back for no reason.
If you have another computer you should put your hard drive in there and see how it works..

• Hard Drive Diagnostic Procedure

 

[IronChief]

I do not. Guess I'll give you that update in a week then. Thanks for everything!

 

[koolkat77]

You can hand it over to a friend..Let him check &/or test it on his PC.

You're welcome and wait for an update

PS: Back up anything important from that hard drive.

 

[IronChief]

... And I'm back. Somewhere along the line I was using my computer and it freezes on me forcing me to restart. Right before the login screen (directly after the windows logo), my computer hangs.. and my monitor self test comes on meaning my computer isn't booting to windows. Joy. So I restart my computer after awhile of waiting, it does the same thing. Reboot again with windows 7 disk, and try to run a repair on the drive, it says it can't find anything wrong with the drive. Try a memory repair, it reboots instead of going into the memory repair test thing, goes past the "press any key to boot from disk" message, and hangs on an error message screen that says "STOP: c0000006 The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x."

A couple more tries with the windows disk yield no results, so I format. Formatting gets me into windows, but whenever I restart the computer after downloading drivers, it repeats the same thing (hanging right after windows logo). The only way to get past that is to format again. So after formatting a 2nd time, here I am. Crystal disk info is in the blue, and telling me my drive is in "good" health, and Chkdsk scans aren't revealing anything. Currently running Seagate tools Long Generic Test, and it's still running. It even came up with a pop-up message telling me the test is running longer than usual. Googling this issue reveals that people are saying it's a hard drive issues still. What do you guys think? =/

 

[koolkat77]

Do you have another hard drive to test with?

 

[IronChief]

not other than the one I took out before, which crystal disk read as "caution" in the health department.

 

[koolkat77]

I'm calling a more experienced analyst to help you with this issue.
Please wait.

 

[Vir Gnarus]

All your crashdumps and your symptoms are common with either a bad hard drive or a bad drive controller on the motherboard (or PCI card depending what your drives are connected too). The I/O NTSTATUS error that occurred during a paging operation is also conducive of this.

The only way to discern which is causing this is to do hardware swapping, preferably with just a drive you know is in good condition. If the system is stable using that drive, the drive itself was bad, otherwise if still experiencing problems the mobo is the cause. Hard drive tests are not a guarantee on a hard drive's health, nor is SMART data also completely dependable.

I did notice on your CrystalDiskInfo that your drive's SMART data is reporting that a number of Command Timeouts have occurred (11 to be exact). This is caused by a drive not responding properly to commands issued by the PC and are conducive of either a bad hard drive, a bad/insufficient PSU, or a damaged or poorly connected data cable.

 

[IronChief]

Edit: nevermind. Thanks