Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

riched20.dll dvwin.exe (or dwwin.exe) bad image checksum


  • Please log in to reply
5 replies to this topic

#1 jnl

jnl

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 22 July 2009 - 06:33 PM

On Sunday, my PC's monitor shut off, but the tower remained on. I shut it manually and rebooted. There was an error message that briefly flashed before it shut down. I tried again and it wouldn't even start up.

Wednesday, I was able to scribble down a piece of the error message that said \lsass.exe
And then the monitor shut down (and I had to manually shut down the tower).

The next time I rebooted, I didn't get any message, it just shut down right away.

I found a blank DVD that was in the drive and removed it. After that I was able to boot it, but I still got an error message:
dvwin.exe (or dwwin.exe) bad image
The application or DLL C:\WINDOWS\system32\riched20.dll is not a valid windows image. Please check this against your installation diskette.

The next time it took me to a screen with a blue background that said:
Start up is interrupted
Checking file system on C:
The type of file is NTFS
The volume is dirty
CHKDSK is verifying files

and it changed to a dark blue screen with white writing and said:
STOP: c0000221 {Bad Image Checksum}
The image SHDOCVW.dll is possibly corrupt. The header checksum does not match the computed checksum

It stayed on that screen.


My system:
DellSystem Workstation 380 - bought in 2005 new
BIOS Version AO2
Processor Type: Intel Pentium 4 CPU 3 GHz
Processor Clockspeed: 3 GHz
Bus speed: 800 MHz
L2 cache: 2 MB
L3 cache: O
Multiple Core capable: NO
Hyperthreading capable: Yes
64-bit Technology: Yes (Intel EM64T)

Installed Memory: 2 GB
Memory Speed: 533 MHz
Memory Channel Mode: Dual Interleaved
Memory Technology: DDR2 SDRAM

Boot sequence:
Onboard SATA Hard drive
Onboard or USB CD-ROM drive

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,385 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:29 PM

Posted 22 July 2009 - 07:43 PM

May not be it, but worth reading:

CMOS Checksum Errors - http://www.pcguide.com/ts/x/sys/booterrGBER08-c.html

CMOS Battery Replacement - http://www.liverepair.com/encyclopedia/art...cmosreplace.asp

At times...when users get a rash of errors that don't make any sense, it's due to the CMOS battery needing replacement.

Checksum errors also could indicate bigger problems, but let's hope :thumbsup:.

Louis

#3 jnl

jnl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 01 August 2009 - 04:27 PM

These are more error messages when I tried to reboot:


I got the blue background screen again, this time it said:
"Start up is interrupted
Checking file system on C:
The type of file is NTFS
The volume is dirty
CHKDSK is verifying files
CHKDSK is verifying indexes
CHKDSK is verifying security descriptions
CHKDSK is fixing mirror copy of the security descriptors..."

there was more but I couldn't finish writing it down because the screen went black, then I saw

the windows logo so I thought it was starting up, but then it went back to the dark blue screen

(next try)

It only got up to 58% and then it froze

(next try)

tried to start in safe mode. the left side of the screen is cut off, but I can still make out

what it says.
"A problem has been detected and windows has been shut down to prevent damage to your computer.
CRQL_NOT_LESS_OR_EQUAL

...Disable BIOS memory options such as caching or shadowing...
tech info ***STOP:0x0000000A (0x00000028, 0x00000002, 0x00000000, 0x804F362F)


Check to make sure any new Hardware or software is properly installed.

if problems continue, disable or remove any newly installed hardware or software.
Disable BIOS memory options such as caching or shadowing.

if you need to use safe mode to remove or disable components..."



The thing is, I havent installed any new hardware or software in over a month or few months.

It got stuck on this screen:

multi(0)disk(0)rdisk(0)partition(2)\window\system32\drivers.sys

" "DRIVERS\pci.sys
Pci
isapup
pciide
pclldex
mountmar
ftdisk
dmload
dmio
partmar
volsnap
atapi
iastor
disk
classpnp
fltmgr
sr
drvmedb
pxhelp20
ksecdd
ntfs
ndis
ohcil394
1394Bus
" "Drivers\mup.sys


Another error message:

"A problem has been detected...

PAGE_FAULT_IN_NONPAGED_AREA

technical information

***STOP: 0x00000050 (0x8E142F78, 0x00000001, 0x805266AA, 0x00000000)



and the last time I tried to start in safe mode
I tried to go to Last Known Good Configuration

again, I got PAGE_FAULT

technical information

***STOP: 0x00000050 (0xD99243F0, 0x00000001, 0x8054BFD2, 0x00000000)

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,385 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:29 PM

Posted 01 August 2009 - 05:12 PM

My suggestion would be to try running sfc /scannow or doing a repair install.

To me, it looks like you either have O/S problems (of an unknown origin/cause) or you have memory problems.

FWIW: You can ignore the dwwin.exe file, that's just Dr. Watson, a builtin report tool for XP. The messages about the file checksums...may indicate file corruption.

Do a search of your files (enable all file extensions and hidden/system files first, please) for any .dmp files.

If you find any, try to follow the procedures in the following link: Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

BTW: Did you replace the CMOS battery?

Louis

#5 jnl

jnl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:10:29 PM

Posted 15 August 2009 - 11:15 AM

Update:

Replaced CMOS battery. Finally saw the home screen then it shut off immediately. Tried again and am consistently getting blue screen messages before getting to home screen - even in safe mode. Got two Fatal System errors:
c000021a fatal system error 0x00000005 (0x00000000 0x00000000)

Tried to use System Restore Disk - to repair. Still getting errors and screen freezing. Called Dell support. They can't help because I don't know the administrative password (I didn't think I had one but it must have been set up by my school's IT center when they set up the computer). Tried "admin" but it doesn't work.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,385 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:29 PM

Posted 15 August 2009 - 11:25 AM

<<...I don't know the administrative password (I didn't think I had one but it must have been set up by my school's IT center when they set up the computer...>>

I guess I'm confused...who does this system belong to?

In any case, if "the school" set up an admin password...then it seems that the simple answer is to take the problems/situations you have described thus far...to the person responsible for dealing with IT matters at the school.

Setting up an admin password...limits the amount of changes which can made by anyone else. It's a normal administrative control invoked by those who either own or have responsibility for repair/maintenance/control of computers.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users