Crash # 6? I'm losing count

Well, in two months I think this is the dreaded BLUE SCREEN crash number 6 (or 7, or 8)...

I've never seen this message before though and after running a diagnostic (chkdsk /R) and checking memory (and I'll do more of that with memtest, ect. I'm seeing another message when I boot up my computer that I need someone to help me with.

Windows XP Home
Dual channel ram with 256 mb
Dell computer -- intel pentium 4 - CPU 2.8 GHz

When I was doing a simple search for a file it crashed and the blue screen said:

NFTS.sye (maybe .sys ?)
address F91A07ED base at F9180000 Date stamp 3d6de5C1

Anyway, now when I start my computer, it starts up and shows my Windows XP screen, then a blue screen comes up and at the top left in white letters it says:
"checking file system on C:
system is NFTS
cannot open volume for direct access
windows has finished checking the disk...."

then the black Windows XP screen comes back up and it continues to load. This only happened a couple of hours ago and I've only run a few programs.

Before this crash I have not added any software or hardware in weeks. I have restarted the computer several times and this message continues to come up each time.

ANY IDEAS?

 

Oh, yes, I am up to date on virus scans, Ad Aware, Spybot, Spyware Blaster...

My concern is that the error had to do with NFTS and the message I keep getting.

Back on 4/11/04 I posted a thread called "Do I really need to reinstall my OS?" and many of you thought this was a memory issue? Does it still sound like a memory issue with this error?

 

Hi pegg,

I found something in the MSKB about this, but it's no help cuz no fix is specified. MS just acknowledges the issue... Sounds like chkdsk is in some kind of loop.
http://support.microsoft.com/default.aspx?scid=kb;en-us;823439&Product=winxp

It's good that it continues to boot 'normally' but that ntfs.sys stop error is cause for concern. I'd be interested to see if you can run chkdsk /r from the Recovery Console. Here's how to do that:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307654&Product=winxp

Hopefully Adryn will come along with some expert advice on this.

 

RAM errors

I did run CHKDSK /R from my recover console -- unless there's something else you mean. It ran quite awhile and said it fixed MANY problems (every crash I've had I"ve run it and it fixes MANY problems)

Thanks for your ideas

MEMTEST:
I started running memtest86 last night and in less than 20 minutes it found thousands of individual errors (about 112 RAM errors) = 12,00 error counts -- but it was about 1 am and I've only run that program once before and that number seems ridiculous so I'll give it a go again today and make sure I've configured it right.

 

Re: RAM errors

Sounds like a possible ram issue

If memtest ends up giving you a clean bill of health, let us know, maybe we can go through debugging the memory dumps.

Provided you can get to them, of course.

 

Re: RAM errors

That number of errors is not rediculous. I had that many after 5 minutes, killed the test and changed my RAM. The test ran overnight and came up clean. Hope your still under warranty.

 

Just an afterthought. when I had the RAM problem, I went out and got a new hardrive as I was getting errors on it all the time, not the exact ones you had, and that didn't fix it. After from some help here, did the above and the rest is history.

 

Hi pegg, This sound like the problem your having

http://support.microsoft.com/default.aspx?scid=kb;en-us;823439

 

self-healing computer

I ran memtest86 again for only an hour and it showed ZERO errors -- what happened to the THOUSANDS that showed last night? (not that I'm complaining) I thought maybe I had used different configurations so I kept stopping the test and changing parameters but it stayed at zero errors. Last night, the second the test started, the error numbers started spinning out.

So, don't know if this was smart/necessary/profitable...but I set my system restore point back to two days ago. Figured it couldn't hurt. (?)

So far everything is running okay but...like I said, I'm sick of these crashes and M$ can take the blame BUT

...my real concern again is that this CRASH ERROR said it actually had to do with my file system itself: NFTS -- isn't that alarming? (I'm easily alarmed)

Yes - fully warrantied -- never messed with the tower - even though a few of you before suggested I go in there and have a look around. I have no problem asking Dell to come and get it/fix it whatever. Is that the obvious thing to do? (then I won't waste anyone's time here either)

 

Re: self-healing computer

Do you have any files in C:\windows\minidump folder?

Whata re the dates of them?

I can debug them for more info possibly

 

minidump file

Earlier I said that when I start my computer, it starts up and shows my Windows XP screen, then a blue screen comes up and at the top left in white letters it says:
checking file system on C:
system is NFTS
cannot open volume for direct access
windows has finished checking the disk....

Well it's interesting -- but this hasn't happened since I did "system restore"

1) I've had my computer freeze up now a couple of times and I've only been in Windows doing a few things "a couple of times".

2) I only have one file in C:\windows\minidump\mini53004--1.dmp 64kb which is confusing since I've had many minidumps.

If you're going to ask me, Adrynalyne, to do anything like give you the file or post it, you'll have to tell me how.

 

Re: minidump file

Zip the file then attach it to a post.

You should be able to click on manage attachments to do it.

 

Re: minidump file

I've never zipped a file before (okay - that's a pathetic confession) so I hope it works

 

Re: minidump file

Taking a look now

 

Re: minidump file

Ok...doing an analyze -v on the dump was useless, no symbols could be loaded and the timestamps could not be verified.

But, I was able to pull up enough info to not even need to do that. I think you do indeed have a sporadic issue with your ram, especially the way memtest acted. Maybe you should try reseating it, if this happens again?



Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Mini053004-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Sun May 30 18:38:40 2004 This is when the error ocurred
System Uptime: 0 days 13:00:27.766
Loading Kernel Symbols
............................................................................................................................
Loading unloaded module list
..................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fa, f03ac2c8, f03abfc8, f91a07ed} Shows up as a Stop 0x24, usually showing ntfs.sys as the filename

Unable to load image aswMon2.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : memory_corruption

Followup: memory_corruption

 

reseating or getting a replacement?

Thanks for your time and effort, I really appreciate it.

Does "reseating it" mean going into the tower and moving around sticks of memory?

Like I said before, should I just call Dell and tell them this 3 month old computer has given me trouble since the beginning and I want a new one?

 

Re: reseating or getting a replacement?

Reseating would mean removing it, then reseating it back in the slot, yes.

In regards to calling Dell, you will have to be able to reproduce the error before they are going to take it off your hands.

I would reccomend if the computer is this new is wait until it crashes again, then call them instead of reseating it (and giving them an excuse to blame you). As many issues as you are having, it shouldn't be too long before you crash again.

 

Re: reseating or getting a replacement?

Yeah, they would blame me if I went in and did anything. I've already recorded several online chats to technicians, e-mails, I even have the whole set of SRCD's to wipe out everything and start all over. I haven't done that because since the beginning people here have mentioned that it sounds like memory problems.

If I wiped out everything and restored it to the way it was when they delivered it to me, any memory problems would still be there right? If it was some kind of defect?

 

Re: reseating or getting a replacement?

Correct.

If you want, I can give you an exact text file of what the debug shows and you can give that to them. You can even truthfully tell them it came from a Microsoft technician

Memory_corruption so far as I know is hardware related.

 

Re: reseating or getting a replacement?

Yes -- please do -- I am keeping track of many of the errors, and diagnostics I've run, etc.

Do you want me to give you an e-mail address through private message or what?

 

Re: reseating or getting a replacement?

I will just attach it to this post. It takes a few minutes to let the debugger run its course.

 

Re: reseating or getting a replacement?

Here ya go.

Hold onto the minidump, too.

 

Re: reseating or getting a replacement?

Oops. I screwed up the analysis. Here we go again.




Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Mini053004-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Sun May 30 18:38:40 2004
System Uptime: 0 days 13:00:27.766
Loading Kernel Symbols
............................................................................................................................
Loading unloaded module list
..................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fa, f03ac2c8, f03abfc8, f91a07ed}

Unable to load image aswMon2.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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: 001902fa
Arg2: f03ac2c8
Arg3: f03abfc8
Arg4: f91a07ed

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


EXCEPTION_RECORD: f03ac2c8 -- (.exr fffffffff03ac2c8)
ExceptionAddress: f91a07ed (Ntfs!NtfsAcquireFcbWithPaging+0x00000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 0000005a
Attempt to write to address 0000005a

CONTEXT: f03abfc8 -- (.cxr fffffffff03abfc8)
eax=0000005a ebx=f03ac484 ecx=00000000 edx=e29ce268 esi=e298031c edi=e18c4064
eip=f91a07ed esp=f03ac390 ebp=f03ac398 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
Ntfs!NtfsAcquireFcbWithPaging+0x5:
f91a07ed 800000 add byte ptr [eax],0x0 ds:0023:0000005a=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from f91a2351 to f91a07ed

STACK_TEXT:
f03ac398 f91a2351 81a67d80 e29ce008 00000002 Ntfs!NtfsAcquireFcbWithPaging+0x5
f03ac3cc f919ff87 81a67d80 00000016 e16560d0 Ntfs!NtfsFindPrefixHashEntry+0x2e7
f03ac530 f91a14c0 81a67d80 ffa80b88 f03ac594 Ntfs!NtfsCommonCreate+0xb78
f03ac610 804ea221 81af6020 ffa80b88 00000001 Ntfs!NtfsFsdCreate+0x1f8
f03ac620 f92382aa ffa80b98 81b32420 ffb082e8 nt!IopfCallDriver+0x31
f03ac66c 804ea221 81af7480 ffb082e8 ffa80b88 sr!SrCreate+0x12a
f03ac67c 80560609 81b58a88 ffa552e4 f03ac828 nt!IopfCallDriver+0x31
f03ac760 8059a2c6 81b58aa0 00000000 ffa55240 nt!IopParseDevice+0xa4d
f03ac7e8 80596c27 00000000 f03ac828 00000040 nt!ObpLookupObjectName+0x56a
f03ac83c 80553f0d 00000000 00000000 e2655f00 nt!ObOpenObjectByName+0xe9
f03ac8b8 805546d8 f03aca08 00120089 f03ac96c nt!IopCreateFile+0x407
f03ac900 f0878c5a f03aca08 00120089 f03ac96c nt!IoCreateFileSpecifyDeviceObjectHint+0x4c
WARNING: Stack unwind information not available. Following frames may be wrong.
f03aca2c f0878fca ff9f23e0 ff9f2250 f03aca63 aswMon2+0x5c5a
f03aca64 f087379a 819b06f0 009f2250 804ea221 aswMon2+0x5fca
f03acb64 8059a2c6 81b58aa0 00000000 ffb2ad98 aswMon2+0x79a
f03acbec 80596c27 00000000 f03acc2c 00000040 nt!ObpLookupObjectName+0x56a
f03acc40 80553f0d 00000000 00000000 00000001 nt!ObOpenObjectByName+0xe9
f03accbc 80554688 02becd6c 80100000 03b9d698 nt!IopCreateFile+0x407
f03acd04 80557bcd 02becd6c 80100000 03b9d698 nt!IoCreateFile+0x36
f03acd44 8052d571 02becd6c 80100000 03b9d698 nt!NtOpenFile+0x25
f03acd44 7ffe0304 02becd6c 80100000 03b9d698 nt!KiSystemService+0xc4
03b9d6dc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
13 errors : !Ntfs (f91a0786-f91a07ef)
f91a0780 48 14 38 5d cb 0f *00 *00 45 03 00 8b 4d d4 *00 *00 H.8]....E...M...
...
f91a07a0 c3 0f 84 59 e7 01 00 *00 5d cb 0f 85 f3 45 *00 00 ...Y....]....E..
...
f91a07c0 ff 15 78 6f 19 f9 *3f *00 0f 85 69 46 03 00 *80 *00 ..xo..?...iF....
...
f91a07e0 e8 e2 fd fd ff c2 *00 00 55 8b ec 51 51 80 *00 *00 ........U..QQ...

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr fffffffff03abfc8 ; kb

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

Re: reseating or getting a replacement?

Thanks -- I got it and saved it.

 

reseating the memory

Well - someone showed me how to "reseat" the memory so I went in and did it now (I hope it doesn't matter that I didn't wait until there was another crash.

Can you tell me what "reseating the memory" is supposed to do? help prevent? fix? (obviously it helps my problem -- but how exactly? -- I'm always trying to LEARN the reason behind the process and actions I take)

Thanks.

 

Re: reseating the memory

Reseating the RAM sticks can clear up problems caused by bad or intermittent connections where the DIMM pins contact the DIMM slot connector. You're having what looks like a intermittent RAM issue, hence Adryn's recommendation.

 

Re: reseating the memory

Pegg, A wrinkle or 2 from the "olde DOS days". Before you remove your RAM, earth yourself on the metal case of your PC to limit static problems and clean the contacts with a white eraser (as you Yanks say). Bazza

====

 

Crash #7

Hey - big surprise -- it's me again. I got online and opened Outlook Express. Closed it. Opened IE and got to Major Geeks and BIG BLUE SCREEN.

Since we last talked I had both my puny memory sticks exchanged for new ones - but they're still just a total of 256MB (I know that's not much) Have WINDOWS XP. But like I've always said before, when this happens I usually only have one, maybe 2 programs running.

This message said:
STOP: 0x0000008E (0xC0000005, 0xC0000005, 0x8F87FBB5, 0xF02A658C, 0x00000000)
Win32k.sys
address BF87FBBe
base @ BF800000 Date Stamp 3F73195d


UGH-- it mentioned "disable BIOS memory options such as caching or shadowing" I've never done that.

I can't think it's RAM anymore since I begged 2 new sticks (for free) off the DELL guy and these are the new ones.

Also -- do I need to do a system restore?

Do I need to run a CHKDSK? I've always done those before but can't remember if I need to.

Thanks -- you guys keep helping me out with this and I appreciate it.

 

Re: Crash #7

Well, you can email the minidump for it, if you want, and I will debug it for you for more info, if any extra info is to be had.

However, is this the first time it has happened? In my experience, this error is caused by a driver. With you being online, I would think your nic driver is suspect.

 

driver

I'll send you my minidump file like I did before in a couple of hours -- I have to leave for a meeting. I'm wondering if it's a driver to. What's a "nic" driver? (does "nic" stand for something? -- I'll check it out -- see if there's a way to update, etc....)

 

Re: driver

Nic=Network Interface Card.

Your network card, in other words

 

zip file

OK - here you go. Attached is the zip file for today's crash.

You asked if this happened before -- I think you must mean when I'm online. I honestly can't remember there's been so many crashes. On-line, in WORD, doing searches, opening a program... I think you name it and it's happened really.

 

3 questions (more or less)

Any answers? Thanks

 

which model for network card

For "Network Card" I have

Model:Broadcom 440x 10/100 Integrated Controller - Packet Scheduler Miniport
AND
Model: WAN (PPP/SLIP) Interface

So -- I could do a diagnostic on the Broadcom (using Broadcom Advanced Control Suite) and everything passed. Do I try to find an update for the Broadcom or the WAN Interface (I don't know what either one means so...)

Here's a screenshot

 

Ignore Screenshot

I tried to EDIT but..-- ignore the screenshot - it's too blurry

 

Re: Ignore Screenshot

Pegg,

Whats up with this system?




BugCheck 1000008E, {c0000005, bf87fbb5, f02a658c, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf87fbb5, The address that the exception occurred at
Arg3: f02a658c, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
win32k!EngCopyBits+20ba
bf87fbb5 0f0000 sldt word ptr [eax]

TRAP_FRAME: f02a658c -- (.trap fffffffff02a658c)
ErrCode = 00000002
eax=0000001e ebx=bf87fc01 ecx=00000000 edx=00d1f7a0 esi=00d1f7a4 edi=00000000
eip=bf87fbb5 esp=f02a6600 ebp=f02a6608 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!EngCopyBits+0x20ba:
bf87fbb5 0f0000 sldt word ptr [eax] ds:0023:0000001e=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8052d571 to bf87fbb5

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f02a6608 8052d571 010102bf 00000000 f02a68a8 win32k!EngCopyBits+0x20ba
f02a6608 7ffe0304 010102bf 00000000 f02a68a8 nt!KiSystemService+0xc4
00d1f80c 71971bb8 00000000 000200c1 00d1f83c SharedUserData!SystemCallStub+0x4
00d1f80c 71971bb8 00000000 000200c1 00d1f83c 0x71971bb8
00d1f824 7196e6eb 000a5318 00000000 000200c1 0x71971bb8
00d1f840 01022592 000a5318 00000000 000200c1 0x7196e6eb
00d1f878 01023429 03a8012d 00000009 00d1f8b4 0x1022592
00d1f8a8 010234b8 00000006 00d1f96c 0101cbb1 0x1023429
00d1f964 01014159 00000000 0000004a 000100bc 0x10234b8
00d1f988 77d43a50 0003003e 0000004a 000100bc 0x1014159
00d1f9b4 77d43b1f 010140f3 0003003e 0000004a 0x77d43a50
00d1fa1c 77d444f5 00086478 010140f3 0003003e 0x77d43b1f
00d1fa70 77d4c395 0047cfa8 0000004a 000100bc 0x77d444f5
00d1faa0 77f75da3 00d1fab0 00000400 00000400 0x77d4c395
00d1fed8 77d43fd4 00d1ff2c 00000000 00000000 0x77f75da3
00d1ff04 010150e3 00d1ff2c 00000000 00000000 0x77d43fd4
00d1ff48 0101a935 00000000 70aac487 0103e468 0x10150e3
00d1ffb4 77e7d33b 00000000 00000000 00000004 0x101a935
00d1ffec 00000000 70aac3f5 0006fed8 00000000 0x77e7d33b
f02a68d0 8057d4c1 f02a6960 f02a6964 f02a6974 nt!KiCallUserMode+0x4
f02a692c bf85819c 00000000 e16ba898 00000400 nt!KeUserModeCallback+0x87
f02a6bf4 bf875ced bc66cfa8 0000004a 000100bc win32k!EngCreatePalette+0x9951
f02a6c3c bf865816 0066cfa8 0000004a 000100bc win32k!EngPaint+0x5c0c
f02a6cac bf847ca4 e2a963c0 f02a6d64 00000000 win32k!EngLpkInstalled+0x3073
f02a6ce8 bf87bd4e f02a6d14 000025ff 00000000 win32k!EngAllocMem+0x6c12
f02a6d48 8052d571 00d1ff2c 00000000 00000000 win32k!STROBJ_vEnumStart+0x20a4
f02a6d48 7ffe0304 00d1ff2c 00000000 00000000 nt!KiSystemService+0xc4
00d1fed8 77d43fd4 00d1ff2c 00000000 00000000 SharedUserData!SystemCallStub+0x4
00d1fed8 77d43fd4 00d1ff2c 00000000 00000000 0x77d43fd4
00d1ff04 010150e3 00d1ff2c 00000000 00000000 0x77d43fd4
00d1ff48 0101a935 00000000 70aac487 0103e468 0x10150e3
00d1ffb4 77e7d33b 00000000 00000000 00000004 0x101a935
00d1ffec 00000000 70aac3f5 0006fed8 00000000 0x77e7d33b


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
28 errors : !win32k (bf87fb96-bf87ffff)
bf87fb90 04 00 74 0e 8d 48 *00 *00 15 6c 1b 98 bf 83 *00 00 ..t..H...l......
...
bf87fbb0 33 ff 39 7d 08 0f *00 *00 0e 00 00 ff 75 08 *00 *00 3.9}........u...
...
bf87fbd0 57 6a 01 50 e8 2a 00 00 00 8b f8 85 ff 74 *00 *00 Wj.P.*.......t..
...
bf87fbf0 8d 4e 08 ff 15 6c *00 *00 bf 8b c7 5f 5e 5d *00 *00 .N...l....._^]..
...
bf87ff90 0f 85 9d 1f 00 00 *00 *00 00 55 8b ec 83 ec *00 *00 .........U......
...
bf87ffb0 1f 00 ff 75 08 ff *00 *00 1b 98 bf 8b f0 85 *00 *00 ...u............
...
bf87ffd0 0f 6a 01 8d 45 0e *00 *00 75 08 e8 16 00 00 00 *00 .j..E...u.......
...
bf87fff0 5e c9 c2 0c 00 ff *00 *00 1e 98 bf 56 57 e8 *00 *00 ^..........VW...

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .trap fffffffff02a658c ; kb

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption---------

 

Re: Ignore Screenshot

http://www.broadcom.com/drivers/downloaddrivers.php

You can find the latest Broadcom drivers here. Make sure you get the right ones.

I would update these drivers, and if it continues, try turning off L2 cache. L2 cache gets factored into physical memory and could very well be the problem.

 

My question exactly

I've been asking that same question since I purchased it in MARCH!!!

NO - it's NOT the memory EVERY Dell tech says to me but we'll humor you and send you two new memory sticks. OK, great, so now this happened again with those two new sticks in. Someone smarter than me has to give me some idea now...what am I supposed to do?

All right, I'll go to Broadcom but again, this card came with my computer, how old/bad/wrong can it be? I'll go check out the site. It tested ok in my computer....said it was running fine, etc.

 

thinking logically

Just remembered something. A couple times (the day before or so this crash happened) I was copying and pasting info and my computer told me it was "low on memory/save now" or something like that.

So maybe this "caching" is storing up info it doesn't need....BUT I don't know where to go to turn off L2 cache. It sounds familiar but I can't remember where I've seen it so, again, baby steps and I'll do what you say.

And what about the "disable BIOS memory options such as caching or shadowing" -- is that the same thing or another place where a bunch of stuff is being stored in memory and causing problems. I'd like to get those things UNCACHED too -- but I don't know where to do that.

Thanks.

 

Explanations anyone?

Can anyone enlighten me to the place in my computer to go to do these two steps (or maybe they're the same thing?) -- I really don't know.

 

Re: Explanations anyone?

I can't tell you where to look exactly, except in your BIOS. Its called L2 or level 2 cache. Aso for shadowing, same place to look. Look for BIOS or video shadowing and turn it off, if it is enabled.

 

UM - yeah, I'm missing something here

I'm totally at a blank although I shouldn't be. I've booted up my computer and went into the screen that showed me system info -- Level 2 cache: 512 KB Integrated

When I clicked on CPU info and see clockspeed, L2 cache size, Bus speed but I can't change those.

I searched in the help section, looked in my Dell manual, but I don't see how to get IN MY BIOS!! That's what I need to know. I'll take it from there...but

HOW DO I GET IN MY BIOS -- I know, silly question (no such thing as a dumb question, right?) UGH, believe it or not, I've been working on this for an hour so I didn't have to come back here and ask this.

I did update my BIOS version though and did update my network card already.

 

Re: UM - yeah, I'm missing something here

Try F2 or Del (Delete).

 

calling Adrynalyne please

It's only been 1 week since my last crash. Yep - next step the Dell technicians but I was hoping Adryn could do one more mini-dump analysis for me so I can go in armed for battle with some intelligent information.
-------------------------------------------------------------------------------
Secondly, can someone tell me what 8 or 9 crashes in less than 4 months does to a computer? Anything? A lot? wear and tear? messes with ___? I'd like to know in case the Dell people are like "too bad, so sad".
-------------------------------------------------------------------------------
I was online last night. Closed down everything and told computer to shut down and then BAM - big blue screen. NO new hardware. NO new software. nada.

STOP: 0x0000008E (0xC0000005, 0xBFA4B4AE, 0xF00C7AA8, 0x00000000)
ialmdd5.DLL -- address BFA4B4AE Base at BFA14000, Date stamp 00000000

that's the little letter "L" in "ialm..." --- I've never seen that and haven't gone searching yet to find out what that means.

Thanks everybody for any advice. I don't expect you to tell me how to fix this DELL but if you could tell me anything I could use in dealing with the techs I'd appreciate it. (I've kept notes from ALL these crashes)

 

Re: calling Adrynalyne please

Hey - found it. I was in media player yesterday trying to figure out how to make a couple videos smaller to e-mail and I was having a lot of trouble, nothing was happening, blah, blah and I found
http://active.mns.ru/drivers/intel/video/Relnotes141.htm But I don't know what to do with this info so I'll check out what Graphics Driver I have and move my question to hardware if I actually have this driver (my computer was made in March and supposedly this is an updated driver version made in Feb.....)

But -- any OPINIONS re: multiple crashes????

 

Re: calling Adrynalyne please

What is happening to you does not make sense, pegg. Now your video driver is causing the crash?

I would stand firm on this one. Have Dell replace your computer. You have the proverbial lemmon. Get mad, talk to a manager, threaten a lawsuit, if they don't want to help you.

Too many problems that are not being resolved by clean installations.

Now we could assume all these different hardware devices are bad, or failing, but really from where I am sitting, it sure sounds like motherboard failure.

What else could it be? Everything is too random, and you are now using new ram. I would still fight to the bloody end to get Dell to replace the entire system.

I'm curious to see what other people's opinions are.

 

minidump file

Hey- thanks for the advice, Adrynalyne, and seriously, I would like to hear from a few more cause I'm getting on that phone and I'll be assertive but I've asked for help before and they've "pooh poohed" what I've said.

They NEVER believed it was a memory problem (even after the mini-dump analyses said several were "memory corruption"). They aren't going to take my request too well of course.

Here's my mini-dump zip file -- I guess you don't have to analyze it since we know what it is from -- but I'm keeping all the info in text files so I can have it all on record...maybe it'll help me in the near future. I know there's a way for me to do this but maybe you could be so kind to do it for me ONE LAST TIME, Adrynalyne (or someone). Thanks bunches everyone.

 

Re: minidump file

I'll get to it if nobody else can and then attach it as a text file for you.

But, as you already said, its unlikely any new information will be delved from it.

But I understand the wanting to keep records--excellent idea.

I too, am curious what other opinions are.

 

thanks

Thanks -- I'm not in any hurry -- and I knew you were "lurking" in the software forum.

 

Re: minidump file

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\v-1jersc\Desktop\Mini062904-01\Mini062904-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Mon Jun 28 19:57:52 2004
System Uptime: 0 days 5:30:15.464
Loading Kernel Symbols
............................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfa4b4ae, f00c7aa8, 0}

Unable to load image ialmdd5.DLL, Win32 error 2
*** WARNING: Unable to verify timestamp for ialmdd5.DLL
*** ERROR: Module load completed but symbols could not be loaded for ialmdd5.DLL
Probably caused by : ialmdd5.DLL ( ialmdd5+374ae )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfa4b4ae, The address that the exception occurred at
Arg3: f00c7aa8, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
ialmdd5+374ae
bfa4b4ae ff5314 call dword ptr [ebx+0x14]

TRAP_FRAME: f00c7aa8 -- (.trap fffffffff00c7aa8)
ErrCode = 00000000
eax=000003ff ebx=00000345 ecx=000003ff edx=00000000 esi=e12e5010 edi=e1184010
eip=bfa4b4ae esp=f00c7b1c ebp=ff90b000 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ialmdd5+0x374ae:
bfa4b4ae ff5314 call dword ptr [ebx+0x14] ds:0023:00000359=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to bfa4b4ae

STACK_TEXT:
ff90b000 00000000 00000000 00000000 00000000 ialmdd5+0x374ae


FOLLOWUP_IP:
ialmdd5+374ae
bfa4b4ae ff5314 call dword ptr [ebx+0x14]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ialmdd5+374ae

MODULE_NAME: ialmdd5

IMAGE_NAME: ialmdd5.DLL

DEBUG_FLR_IMAGE_TIMESTAMP: 3e9c43bd

STACK_COMMAND: .trap fffffffff00c7aa8 ; kb

BUCKET_ID: 0x8E_ialmdd5+374ae

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