Solved Software- or Configuration-related Crashes

[Vir Gnarus]

Ok, did a light perusing. A couple things:

• Consistently network-related crashes.
• Thread stack for some of the crashes shows up low memory events from NETIO. It may be a symbol error, but it could also mean something's got a memory leak.
• Driver Verifier crash did not show up anything different, meaning the driver causing problem wasn't selected during DV setup, or this is indeed a hardware issue.
• The latest crashdump you provided has errors dotting its stack. The ones I'm concerned about especially are the c0000102 errors, meaning "{Corrupt File} The file or directory %hs is corrupt and unreadable. Please run the Chkdsk utility."

Overall, I see items of suspicion, but nothing really to sink our teeth into. First thing I should go after, however, are the disk-related problems. Do a CHKDSK /R (search for bad sectors) followed by an offline SFC /SCANNOW. Do also hard checks with Seatools and a screenshot of CrystalDiskInfo.


If you want to give us something better to work on that may give a better answer, we'll need you to run Driver Verifier again, let it crash, then after that provide us the Kernel Dump, not the minidump. It's MEMORY.DMP in Windows directory. Zip it up and upload using Mirrorcreator - Upload files to multiple hosts.

 

[toranaboy]

I must say that as someone who used OS/2 and linux back in the olden days it's almost enough to turn a man back to GNU in spite of the loss of games and stuff. If I did it would cause great joy in the heart of an engineer friend of mine who considers me a traitor btw, nothing like this happening when I was using linux, but then we couldn't get drivers for a lot of things anyway and I wasn't up to writing my own

 

[toranaboy]

Thanks, I'll get to work on it this evening.

 

[toranaboy]

Memory.dmp

Here is the link to the MEMORY.DMP file; I didn't have time to work out the other upload service this morning: https://dl.dropboxusercontent.com/u/61830328/MEMORY.rar. I hope Dropbox is all right. If it isn't let me know and I will nut out mirrorcreator tonight. (I never knew such a service existed).

 

[toranaboy]

Dump

Another dump: at https://dl.dropboxusercontent.com/u/61830328/MEMORY1.rar

 

[toranaboy]

Hello?

 

[Vir Gnarus]

Sorry, slipped past me. In fact, I don't think I'll be able to look at this until next week. Way too much going on this week. I'll see what I can do then. I'll notify others to take a gander at them in the meantime.

 

[centaur78]

Hi

The first Memory.dmp... refers to memory management error ( Bugcheck 0x1a). I would suggest you do a memtest for each ram on each slot for atleast 7 to 8 passes... to rule out the RAM ...


The Second Memory1.dmp is refers to SYSTEM_SERVICE_EXCEPTION (3b).. which is caused by a process called "Bash.exe" while accessing a file.

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000094, fffff8000372594f, fffff8800c95e9f0, 0}

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

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff8000372594f, Address of the instruction which caused the bugcheck
Arg3: fffff8800c95e9f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
nt! ?? ::FNODOBFM::`string'+cdb5
fffff800`0372594f f77114          div     eax,dword ptr [rcx+14h]

CONTEXT:  fffff8800c95e9f0 -- (.cxr 0xfffff8800c95e9f0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80139d21e0
rdx=0000000000000000 rsi=fffffa80135e5cb0 rdi=0000000000000000
rip=fffff8000372594f rsp=fffff8800c95f3d8 rbp=fffffa80139d25e0
 r8=0000000000000000  r9=fffffa80139d21e0 r10=fffffffffffffffe
r11=0000000000000001 r12=000000000000004e r13=fffff9802beb0c10
r14=fffffa80139d21c0 r15=fffff8800c95f550
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt! ?? ::FNODOBFM::`string'+0xcdb5:
fffff800`0372594f f77114          div     eax,dword ptr [rcx+14h] ds:002b:fffffa80`139d21f4=00000000
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  bash.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800110c10d to fffff8000372594f

STACK_TEXT:  
fffff880`0c95f3d8 fffff880`0110c10d : fffffa80`135e5cc8 fffff980`2efb0ee0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xcdb5
fffff880`0c95f3e0 fffff880`0110e9aa : fffff980`2beb0c00 fffffa80`109fb400 fffffa80`0e6ad800 fffffa80`0e5b6000 : fltmgr!FltpPerformPreCallbacks+0x39d
fffff880`0c95f4e0 fffff880`0112c2a3 : fffff980`2beb0c10 fffff980`2beb0c10 fffff980`2beb0c10 fffff980`2beb0c10 : fltmgr!FltpPassThroughInternal+0x4a
fffff880`0c95f510 fffff800`03b75d26 : fffff980`2beb0c10 00000000`00000002 00000000`00000040 00000000`00000000 :[COLOR="red"] fltmgr!FltpCreate[/COLOR]+0x293
fffff880`0c95f5c0 fffff800`039ccfdc : 00000000`00000005 fffffa80`134c2cc8 fffffa80`109fb4e0 fffffa80`0ed1dde0 : [COLOR="Red"]nt!IovCallDriver[/COLOR]+0x566
fffff880`0c95f620 fffff800`039c8958 : fffffa80`0e6489b0 fffff800`00000000 fffffa80`134c2b10 00000000`00000001 : nt!IopParseDevice+0x14d3
fffff880`0c95f780 fffff800`039c9b76 : 00000000`00000000 fffffa80`134c2b10 00000000`00100021 fffffa80`0cac7600 : nt!ObpLookupObjectName+0x588
fffff880`0c95f870 fffff800`039cb47c : 00026161`021a0046 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`0c95f940 fffff800`039b5a84 : 00000000`0008e358 00000000`00100021 00000000`0008ebb0 00000000`0008e2f8 : nt!IopCreateFile+0x2bc
fffff880`0c95f9e0 fffff800`036cae93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x58
fffff880`0c95fa70 00000000`773a164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a164a


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+cdb5
fffff800`0372594f f77114          div     eax,dword ptr [rcx+14h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+cdb5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

STACK_COMMAND:  .cxr 0xfffff8800c95e9f0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!_??_::FNODOBFM::_string_+cdb5

BUCKET_ID:  X64_0x3B_VRF_nt!_??_::FNODOBFM::_string_+cdb5

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

Now as far as i understand ... bash.exe belongs to cgywin and i presume it could be related the MKVToolNix -- Cross-platform tools for Matroska....probably some file you were editing ??

So as Vir advised do these and post the snapshot here

Overall, I see items of suspicion, but nothing really to sink our teeth into. First thing I should go after, however, are the disk-related problems. Do a CHKDSK /R (search for bad sectors) followed by an offline SFC /SCANNOW. Do also hard checks with Seatools and a screenshot of CrystalDiskInfo.

Could you also tell me the Segate HDD firmware version ??

 

[toranaboy]

Some tests carried out

Memtest86+ 9 passes no errors

Chkdsk for bad sectors: No problems detected

SFC /Scannow - Repair disc booted, then at System Recovery Options dialog box I selected

'next' and the program responded that the computer had failed to start(?). I declined the

option of System Restore and it carried out a number of tests to establish the cause (without success).

After that, it opened the System Recovery Options dialog box at which I chose Command

Prompt and attempted to run sfc /scannow but it reported that it could not run.

Which test or tests should I perform in SeaTools?

Seagate Firmware Revision: CC4C

A screenshot from Crystal is attached. I hope you can read it.

 

[centaur78]

The Seagate Firmware version Update is CC4H . You can update it if you want..

However it is not that important at this point as the SMART Values from Crystal Disk info does look good as well.

You can also run Seatools as well .. follow it here. Run the short Drive test.... and let me know.

For SFC scannow did you try it like this as mentioned in the tutorial

In the command window that opens type this command below and hit the <enter> key, be sure to use your drive letter, where mine is F: for this demonstration yours probably will not be the same.

sfc /scannow /offbootdir=f:\ /offwindir=f:\windows

 

[toranaboy]

SeaTools short drive self-test was a pass. (Is that the test you meant centaur)? I followed the scannow tutorial. I referred in my narrative to the way my experience diverged from the script when it 'complained' that the machine would not start. What's that about?? Once through that, I ran the command from the terminal and it just refused (I forget the message) to fire up. The noive!

 

[centaur78]

hmm

Ok have you tried running "sfc /scannow" from the command prompt in windows rather than using the DVD

Try that and let me know.

 

[toranaboy]

Scannow Report

Ran scannow from prompt as suggested and turned up some corrupt files. I attach the CBS.log file.

 

[centaur78]

The CBS logs does point to one corrupted file NlsLexicons001a.dll (Microsoft Neutral Natural Language Server Data and Code) that cannot be repaired. Even the store has a mismatch file.... thats why the SFC cannot repair it.

Before providing the solution could you answer the below

Are you having problems with updates or was the whole issue caused after an update ?

Could you also use the SF diag tool to GRAB ALL the files and post here again.

Also are you getting anymore BSOD ???

 

[toranaboy]

The CBS logs does point to one corrupted file NlsLexicons001a.dll (Microsoft Neutral Natural Language Server Data and Code) that cannot be repaired. Even the store has a mismatch file.... thats why the SFC cannot repair it.
Hmm. It's obvious really when you look at it carefully

Before providing the solution could you answer the below

Are you having problems with updates or was the whole issue caused after an update ?
I don't know I'm afraid. Up until 16th May, things were pretty good for updates. Since then, they fail regularly. I imagine the log will confirm that.

Could you also use the SF diag tool to GRAB ALL the files and post here again.
I attach that material.

Also are you getting anymore BSOD ???

Yep. At least daily.

Would it be easier if I just re-installed the OS? This is a home computer so it's not a catastrophe. I don't like to take up your time if it's avoidable. You and Arc have been so kind and helpful.

 

[toranaboy]

Just reviewing the updates history, I note that by far the bulk of the fails are for a single security update for Internet Explorer 10.

 

[centaur78]

Yes you would need to do a repair install or clean install.

A Clean install is always good so that you start fresh and then report back if you still have the same problem..

 

[toranaboy]

Re-install

Yes you would need to do a repair install or clean install.

A Clean install is always good so that you start fresh and then report back if you still have the same problem..

I will do a clean install then. Wish me luck

 

[centaur78]

Best Of luck !!

 

[toranaboy]

Antother Crash

Clean install of Windows 7 went OK so I thought I'd confound everything by upgrading to Win 8 at the same time. I calculated that the kind of problems I had been having would not be changed by such an upgrade. Of course, I had read that a fix for 8.0 was in the works and thought I'd grab a cheap upgrade. Hmmm. Turns out it's worse to use than I thought it would be. Anyhoo, it crashed with a polite screen and re-emerged without mouse support (usb). The keyboard started working again after a couple of reboots. I think the likely explanation then is flaky hardware. The RAM after two rounds of testing must be considered unlikely to be the problem. I suspect I have a dodgy motherboard. What I have done is installed mint 15 to see whether the machine holds up away from windows.

I'll let you know how it goes. If it stays up for a reasonable length of time I'll need to think about trying to re-install windows. (I might pass on Windows 8 though).