[Help] I need help with BSOD.

[phatcat42141]

Had a computer in the shop the other day doing the exact same thing that you posted -- ended up being that some of the capasitors on the motherboard were starting to "leak" in other words the motherboard either got way to hot or it took too much current from either lightning or power surge. Let me also say this watch out if it is a "leak" on the motherboard as I jarred the do do out of me lol

[Viper81]

ok, i finnally got it today... didn't happen during startup but when i started a program (limewire) right as it started it geve me the blue screen. i have the memory dump file on hand if anyone knows where i can store it for you to get it to help me out with this. although it might just be a program error. (cus i used to have limewire start with the computer but after i started this thread i made it stop starting with computer)....

hit me back... thanks alot

Viper

[cluberti]

Check your PMs.

[Viper81]

ok, it's uploading now, it will probably be up in around 5 hours (i have slow upload speed, Cable 65 KB/s) sorry for how big it is. (i have 2 gigs of ram, could only compress it to 1.28 GB)

thanks alot in advance for all your hard work cluberti..

like i said though. i think limewire has something to do with it. start with that. THANKS

Viper

[cluberti]

OK, I finally finished the dump. Here's what I've got from what's available in the dump:

It appears that a java function was being executed at the time of the crash (since LimeWire's a java client application, I'm not surprised), and the following is the call from the stack that's being executed at the time of the crash:

awt!Java_sun_awt_image_ImagingLib_init+30bb0

So this is a function in awt.dll (that's what awt tells us, before the bang):

6d000000 6d167000   awt		(export symbols)	   awt.dll
	Loaded symbol image file: awt.dll
	Mapped memory image file: C:\Program Files\Java\jre1.5.0_06\bin\awt.dll
	Image path: C:\Program Files\Java\jre1.5.0_06\bin\awt.dll
	Image name: awt.dll
	Timestamp:		Thu Nov 10 16:22:06 2005 (4373B9FE)
	CheckSum:		 00152FA8
	ImageSize:		00167000
	File version:	 5.0.60.5
	Product version:  5.0.60.5
	File flags:	   0 (Mask 3F)
	File OS:		  4 Unknown Win32
	File type:		2.0 Dll
	File date:		00000000.00000000
	Translations:	 0409.04b0
	CompanyName:	  Sun Microsystems, Inc.
	ProductName:	  Java(tm) 2 Platform Standard Edition 5.0 Update 6
	InternalName:	 awt
	OriginalFilename: awt.dll
	ProductVersion:   5.0.60.5
	FileVersion:	  5.0.60.5
	FileDescription:  Java(tm) 2 Platform Standard Edition binary
	LegalCopyright:   Copyright © 2004

It appears, however, that the issue that actually caused the crash was being done in the Nvidia display driver - here's the stack showing the driver doing it's thing, then the bugcheck:

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong.

94665564 8052202d 0000008e c000008e 6d06a777 nt!KeBugCheckEx+0x1b

9466592c 804de403 94665948 00000000 9466599c nt!IoSetFileOrigin+0x58fb

946659b0 bfa20bfe 946659a4 e297b1c0 e116cd40 nt!Kei386EoiHelper+0x1da

94665a3c bfa73ec0 ae904000 00004000 e2979a00 nv4_disp+0x4cbfe

00000000 00000000 00000000 00000000 00000000 nv4_disp+0x9fec0

Here's the information on the display driver you're loading:

bf9d4000 bfd99b00   nv4_disp   (export symbols)	   nv4_disp.dll
	Loaded symbol image file: nv4_disp.dll
	Image path: \SystemRoot\System32\nv4_disp.dll
	Image name: nv4_disp.dll
	Timestamp:		Sat Dec 10 06:38:33 2005 (439ABE39)
	CheckSum:		 003C84D0
	ImageSize:		003C5B00
	File version:	 6.14.10.8198
	Product version:  6.14.10.8198
	File flags:	   8 (Mask 3F) Private
	File OS:		  40004 NT Win32
	File type:		3.4 Driver
	File date:		00000000.00000000
	Translations:	 0409.04b0
	CompanyName:	  NVIDIA Corporation
	ProductName:	  NVIDIA Compatible Windows 2000 Display driver, Version 81.98 
	InternalName:	 nv4_disp.dll
	OriginalFilename: nv4_disp.dll
	ProductVersion:   6.14.10.8198
	FileVersion:	  6.14.10.8198
	FileDescription:  NVIDIA Compatible Windows 2000 Display driver, Version 81.98 
	LegalCopyright:   © NVIDIA Corporation. All rights reserved.

I'd suggest making sure you're using the latest version of the JRE (and thus the latest version of awt.dll), and also update your display driver to the last stable version for your OS. Since it appears that it's the display driver that's got "issues", I'd say that if the problem continues after running the latest stable driver for your OS, contact Nvidia for support, as it's ultimately an issue with their video driver.

At least you can rest assured the likelihood of this being a RAM issue is nil .

Edited May 10, 2006 by cluberti

[Viper81]

you dont understand how much i appreciate this.... i owe you a 6 pack of beer. THANKS ALOT FOR YOUR HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Viper