Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent BSOD and rebooting, memory dump?


24 Nov 2012   #21

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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.

My System SpecsSystem Spec
.

07 Dec 2012   #22

Microsoft Windows 7 Ultimate 64-bit
 
 

Has a solution been found to this problem yet? I'm still getting random BSOD->restarts =/. Thanks in advance.
My System SpecsSystem Spec
07 Dec 2012   #23

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Upload the dumps so we can check.
My System SpecsSystem Spec
.


07 Dec 2012   #24

Microsoft Windows 7 Ultimate 64-bit
 
 

Done.
My System SpecsSystem Spec
07 Dec 2012   #25

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

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:This dump files comes yet again with bugcheck 24.
Code:
*******************************************************************************
*                                                                             *
*                        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:Post back results.
My System SpecsSystem Spec
07 Dec 2012   #26

Microsoft Windows 7 Ultimate 64-bit
 
 

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.
My System SpecsSystem Spec
07 Dec 2012   #27

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Will take a look at them.


Hard drive test both short and long with: DOS version of Seatools:
My System SpecsSystem Spec
09 Dec 2012   #28

Microsoft Windows 7 Ultimate 64-bit
 
 

And done.
My System SpecsSystem Spec
09 Dec 2012   #29

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Good. What about Seatools for DOS? And this part:
Quote:
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.
Quote:
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.
Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.
My System SpecsSystem Spec
11 Dec 2012   #30

Microsoft Windows 7 Ultimate 64-bit
 
 

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.
My System SpecsSystem Spec
Reply

 Frequent BSOD and rebooting, memory dump?




Thread Tools



Similar help and support threads for2: Frequent BSOD and rebooting, memory dump?
Thread Forum
Very frequent dump memory BSOD crashes BSOD Help and Support
Solved Frequent BSOD's, can't find a clear pattern. dump attached BSOD Help and Support
Frequent crashes (BSOD) on the new PC with BSOD Dump attached BSOD Help and Support
BSOD - Memory Dump Performance & Maintenance
BSOD memory Dump BSOD Help and Support
BSOD.... Memory Dump BSOD Help and Support
memory dump BSOD BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33