BleepingComputer.com: System Crash/Blue Screen/New Hardware

Hi,

I just installed a new memory chip, new Video Card and new hard drive. My system worked fine for about 24 hrs, then last night it crashed and gave me the blue screen. I dont' know which one caused the crash. I just found the problem with a bad memory module that was causing my computer to restart on its own constantly, thanks to this forum and everything was running fine, no problems once I took out the bad module.

I just installed a new module, a new NVidia Geoforce video card and a new Maxtor 250 gig hard drive (just for storage).
Last night it crashed and gave me a blue screen.

Windows XP Home Edition Service Pack 3 (build 2600)
Install Language: English (United States)
System Locale: English (United States)
2.67 gigahertz Intel Celeron
16 kilobyte primary memory cache
256 kilobyte secondary memory cache
Not hyper-threaded
Board: SiS-661
Bus Clock: 133 megahertz
BIOS: Phoenix Technologies, LTD 6.00 PG 02/16/2005
331.01 Gigabytes Usable Hard Drive Capacity
252.87 Gigabytes Hard Drive Free Space

COMBO IDE5232CO [CD-ROM drive]

Maxtor 6Y250P0 [Hard drive] (251.00 GB) -- drive 1, SMART Status: Healthy
WDC WD800JB-00JJC0 [Hard drive] (80.03 GB) -- drive 0, SMART Status: Healthy
NVIDIA GeForce 6200 A-LE [Display adapter]
ViewSonic VE710b-2 [Monitor] (17.1"vis, December 2004)

Here is the mini dump file:


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Nov 5 23:48:27.406 2009 (GMT-8)
System Uptime: 0 days 11:51:19.009
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {c03aec14, 2, 0, 804e8ad5}

Probably caused by : win32k.sys ( win32k!itrp_InnerExecute+1c )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c03aec14, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804e8ad5, address which referenced memory

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


READ_ADDRESS: c03aec14

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmAccessFault+96d
804e8ad5 f60701 test byte ptr [edi],1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe

TRAP_FRAME: b5930d5c -- (.trap 0xffffffffb5930d5c)
ErrCode = 00000000
eax=01204f10 ebx=00000000 ecx=00989680 edx=01205013 esi=01205013 edi=b5930e54
eip=bf85ce4b esp=b5930dd0 ebp=b5930e54 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
win32k!itrp_InnerExecute+0x1c:
bf85ce4b 0fb610 movzx edx,byte ptr [eax] ds:0023:01204f10=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 804e0944 to 804e8ad5

STACK_TEXT:
b5930d44 804e0944 00000000 01204f10 00000000 nt!MmAccessFault+0x96d
b5930d44 bf85ce4b 00000000 01204f10 00000000 nt!KiTrap0E+0xd0
b5930dd0 bf85f2a1 e3e2aff0 e3e2afb8 e3e2af5c win32k!itrp_InnerExecute+0x1c
b5930e54 bf85c66f 01204f10 01205013 e3e2af5c win32k!itrp_Execute+0x24f
b5930e7c bf85f709 01204f10 01205013 e3e2af5c win32k!itrp_ExecuteGlyphPgm+0x4c
b5930eb0 bf8604a5 e3e2455c 00000001 00000000 win32k!fsg_SimpleInnerGridFit+0x103
b5930f48 bf85e696 e3e24514 e3e26c78 e3e2af5c win32k!fsg_ExecuteGlyph+0x1d3
b5930fa4 bf85e553 e3e24514 e3e2af5c e3e26c68 win32k!fsg_CreateGlyphData+0xd5
b5930fe4 bf85ecf4 e3e24514 e3e2af5c e3e242bc win32k!fsg_GridFit+0x4d
b593105c bf85c9e5 00000001 b5931078 bf85ca17 win32k!fs__Contour+0x372
b5931068 bf85ca17 e3e24010 e3e24074 b5931090 win32k!fs_ContourGridFit+0x12
b5931078 bf85e219 e3e24010 e3e24074 b593122c win32k!fs_NewContourGridFit+0x10
b5931090 bf85ed66 e27248e0 00000027 b59310cc win32k!bGetGlyphOutline+0xb3
b59310b8 bf85ee74 e27248e0 00000027 00000001 win32k!bGetGlyphMetrics+0x20
b59311fc bf85e3b9 e27248e0 00000027 b59312d0 win32k!lGetGlyphBitmap+0x2b
b5931224 bf85e2a5 00000000 00000001 00000027 win32k!ttfdQueryFontData+0x13e
b5931270 bf85b715 e16f0010 e19f57a8 00000001 win32k!ttfdSemQueryFontData+0x45
b59312a0 bf85ba5b e16f0010 e19f57a8 00000001 win32k!PDEVOBJ::QueryFontData+0x3c
b5931318 bf807af0 b5931680 e1a29734 e1a32270 win32k!xInsertMetricsPlusRFONTOBJ+0x11e
b593134c bf8c4b4e 00000061 e1bb8000 7ffdf234 win32k!RFONTOBJ::bGetGlyphMetricsPlus+0x180
b593138c bf812666 b5931908 b5931680 00000d50 win32k!ESTROBJ::vCharPos_H1+0x57
b59313c4 bf8118a2 7ffdf234 00000061 b5931908 win32k!ESTROBJ::vInit+0x1c7
b5931668 bf812ff9 b5931908 0000000c 00000020 win32k!GreExtTextOutWLocked+0x666
b59317d0 bf80c694 b5931908 7ffdf1e4 0000029c win32k!GreBatchTextOut+0x344
b5931924 804dd970 00000092 0013b3b0 0013b3f8 win32k!NtGdiFlushUserBatch+0x11b
b5931934 7c90e514 badb0d00 0013b3b0 7ffdf000 nt!KiFastCallEntry+0xcd
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5931938 badb0d00 0013b3b0 7ffdf000 88739da8 0x7c90e514
b593193c 0013b3b0 7ffdf000 88739da8 00000018 0xbadb0d00
b5931940 7ffdf000 88739da8 00000018 0020027f 0x13b3b0
b5931944 88739da8 00000018 0020027f 01c90000 0x7ffdf000
b5931948 00000000 0020027f 01c90000 3469e05a 0x88739da8


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!itrp_InnerExecute+1c
bf85ce4b 0fb610 movzx edx,byte ptr [eax]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!itrp_InnerExecute+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e87572

FAILURE_BUCKET_ID: 0xA_win32k!itrp_InnerExecute+1c

BUCKET_ID: 0xA_win32k!itrp_InnerExecute+1c

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

Thank you!
Sherrie

Are these memory modules you refer to...are they the same...made by the same manufacturer, etc.?

I guess I have to wonder...what makes you think that you solved what you classified as a memory situation...by buying one module of RAM?

It's usually not that simple, IMO.

Louis

I posted the problem here:

http://www.bleepingcomputer.com/forums/ind...p;#entry1415467

I did everything I was told to do and we finally realized I had one bad memory module that I had just gotten for mothers day. I pulled the module, added my old module back and I have had no more problems with the computer restarting on it's own after that, and that was back on Sept. 26, 2009.

The memory module came from the same place, but I will have to check to see if they are the same. However, I had two of these modules, ea 1gb. I removed one and replaced it with the old one and no problems. Never had to remove the other one.
I replaced the old one with a new 1gb from the same place and no problems for two days. Then I added the new video card and the new hard drive. Next day I got the blue screen error.

Info appreciated .

Well...you did a nice job providing the BSOD data...but it all seems pretty inconclusive to me. OA errors can be reviewed at http://www.aumha.org/a/stop.htm, left column.

I remember now, I just looked at your posted link .

The one thing that seems to be constant in all your posts...is your motherboard/chipset (ECS FX661/Sis 661) and a CeleronD CPU. I'm kind of curious that you have replaced just about everything but the motherboard or the CPU...but neither of those.

I don't have the bias that some do about ECS boards, I use them (this system has one) and I like them and Sis chipsets...but I don't understand your BIOS data you report this time.

http://www.cpu-upgrade.com/mb-ECS/661FX-M(V1.0B).html

That ECS board comes with an Award BIOS, V1.0B...yet your data reflects a Phoenix 6.00 BIOS.

I'm pretty much grasping at straws, so bear with me.

Did someone flash the BIOS...if so, it appears that the wrong BIOS update may have been used...or the data reported is incorrect.

Start/Run...type msinfo32...what is reflected for BIOS Version Date and SMBIOS Version?

Thanks.

PROCESS_NAME: csrss.exe...that's the one thing I gleaned from your report. I would just double-check the size and location of that file (csrss.exe) on your system.

For info only: http://www.neuber.com/taskmanager/process/csrss.exe.html. My csrss.exe is in C:\Windows\System32 and is 6MB in size.

Louis

BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 2/16/2005
SMBIOS Version 2.2
I didn't replace the cpu nor the motherboard because I can't afford it yet. My son gave me the memory and hard drive and I bought the video card because I was having a lot of problems with the ATI set up.

When I boot up the screen has always said Award Bios Phoenix

csrss.exe is in C:\Windows\system32 and is 6kb
csrss.exe in C:\Windows\$NtServicepackUninstall$ 6kb
csrss.exe in C:\Windows\Servicepackfiles\i386 6kb

Did I miss anything?

Well, it seems that Award & Phoenix merged sometime (1998). Where they used to make separate BIOSes, it's now a joint effort so it's possible that one utility will record the BIOS version as something different. What's reported by msinfo32 seems to be the correct data.

But...I still have a problem with the BIOS version reported...since every retail model of that board lists the Award 1.0 BIOS version indicated on the link I supplied yesterday.

This system...who is the original manufacturer/seller...and what is the model number (if any)? it doesn't appear to be custom-built or put together by someone like you or me.

Although the motherboard might indicate that it's custom-built...motherboard manufacturers do make boards for OEMs (Dell, Gateway, etc.) which have the same ID.

I can think of two things that could possibly be contributors:

a. The chipset drivers are damaged and need to be replaced.

b. You have either a motherboard or CPU problem.

For now, I suggest uninstalling the video card you purchased...the board should have onboard video, according to the specs.

Before you installed the video card, did you disable the onboard in the BIOS? Sometimes this may be necessary, sometimes not.

FWIW: I find it best to make one hardware change at a time, makes it easier to determine what might be wrong. I feel that the RAM and the hard drive are probably free of suspicion...which is why I suggest uninstalling and removing the new video card and using the onboard video (temporarily) to see if problems arise.

Thanks, you are very cooperative...which is sometimes unusual behavior for users with system problems .

Louis

This is the original System

GQ 5130 (purchased at Fry's Electronics 2006 I think)
* CPU: Intel CeleronD 2.66GHz CPU
* Motherboard: ECS 661FX-M
* Chipset: SiS 661FX
* Devices
o 40 GB HDD
o Combo DVD-ROM/CDRW Drive
o Floppy drive
* Memory: 256MB DDR
* Operation System: Windows XP Home Edition SP2
* Accessories Box
o Keyboard
o Mouse w/scroll wheel
o Stereo Speakers
* Mainboard
o Open AGP 8x slot, 3 x PCI slots (1 used)
o 6 x USB ports (4 back, 2 front)
o Build in AC97 audio codec.
o 10/100 Network Interface Card and 56K Modem Card provided.

Video chipset was turned off in Bios when I upgraded to the ATI Radeon 9200 Video Card. ATI Catalyst system was installed. I was having a lot of graphics problems lately and couldn't play a lot of games, so I finally replaced the graphics card with the new NVidia card. I removed the ATI card, installed the new NVidia Card, uninstalled the ATI Drivers/Catalyst system, installed the drivers for the NVidia card. Had problems with the installation and had to do it twice. Then windows Found New Hardware kept popping up and telling me my monitor was new and needed drivers, then it would search and get stuck searching. I finally went in and re installed the monitor drivers on my own and haven't had a problems with that part since.
The ATI Radeon was 128mb, the NVidia is 512 mg.
I searched for a Bios update but could not find any, so I don't believe I installed one.
When I woke up this morning and turned my computer on, it started a chkdisk scan immediately on its own. I don't know how to find a log for it though, so I don't know what it found. I do know that I saw a lot of Attributes being repaired though.

I would love to get a new motherboard and faster CPU but I don't know how. Fry's told me the mother board was not upgradeable.

One thing I am curious about is that I thought my main Hard drive was a FAT32, but the new one says it is NTFS. I just did a quick format on it and set it for Storage. No OS installed on it. My main Hard drive was set at Cable Select, so I set the new one at Cable Select also. They are both EIDE drives.

Just an FYI, I ran a Malware scan (Malwarebytes) and a virus scan (ESET Nod32) before I installed anything and no problems were found.

When the crash occurred and I rebooted, the Microsoft error report said it was a driver or hardware problem which is what it always says which doesn't help.

Also, at one time I had another hard drive installed that I was installing an OS on for my sister. It was set to Slave. When I removed it, my computer still showed it was there until I finally did a reformat to my system. From then on, when I boot up, periodically it will tell me that the boot sequence has changed and to hit F1 to fix it or del to keep going. I checked the Bios and system and the boot sequence is still where it should be.

So, if none of this helps, then I guess I will have to uninstall the video card, which is what I really do not want to do, but will.

Well...to me that all sounds like I asked you to permanently uninstall the card.

If you go back and see what I said...uninstalling the card (temporarily) is an attempt to see what is causing the problem that you initially posted about recently.

If you don't want to do that as a troubleshooting step, that's fine with me.

We try to help, but we don't try to do magic .

Louis

No, I didn't mean it that way. I was hoping you would find something in my new post that might help so i wouldn't have to remove it, even temporarily. I deleted all my ATI drivers and I no longer have the cd that came with it.
I will have to now go in and enable the chipset again and remove the Nvidia card. Was just hoping I wouldn't have to, that is all.
Will let you know what happens.

Drivers for any ATI card or chipset...are always downloadable from the ATI/AMD website or any of several other sites.

Louis

Just a note:

----------
I would love to get a new motherboard and faster CPU but I don't know how. Fry's told me the mother board was not upgradeable.
----------

The drones at fry's might know what they are talking about if you asked every single one of them and averaged the answers. At least used car dealers know when they are lying.

It is a standard micro-atx main board according to the mfg manual, and while socket 478 mainboards are not easy to find and no longer cheap, you can upgrade to just about any of the modern boards that are micro-atx form factor as long as you realize you must purchase CPU and ram that match the specs of the main board. Most new boards no longer have agp either.

Up until about 2008 you could have still upgraded to a better mainboard and kept your processor and ram but I looked recently and it is mainly the corporate supply specialist distributors that still have them at premium prices.

Frys have sold some really cheap pop riveted cases in their loss leaders, but all of them I have seen still have standard ATX holes for standoffs.