Forum Home
Press F1
 
Thread ID: 23994 2002-08-31 21:40:00 winmm c.adkins (144) Press F1
Post ID Timestamp Content User
75400 2002-08-31 21:40:00 when playing games the computer will display an explorer box stating it has performed an illegal operation and will be shut down. Sometimes you can go to the details panel to find it has caused a fault at winmm. Other times i know it is the same problem but the system freezes and i have to shut it down and restart. This never used to happen at all and now it is becoming more frequent and frustrating. If anyone can assist me with a remedy it would be greatly appreciated. c.adkins (144)
75401 2002-08-31 22:06:00 Hi, could you advise what operating system you use and the specific error message. Errors like this normally have "an error has occured with xxx at yyy", with the xxx being the file name (like winmm.dll?) and yyy being a reference to a memory address like cx00004567.

cheers
Parry 		parry (27)
75402 2002-08-31 22:51:00 Hey Parry,

I'm not being a smart-a*se or offensive or anything bad.
I REALLY want to learn something.

Your "xxx". Yes. Absolutely. Usefull. I understand.
Your "yyy". I'm lost. I don''t know how to use it. I'd really like to know how to use it.

Would you:

1. Explain.
2. Point me at a useful site wot explains in little words like as wot I can keep up wif?

Cheers,
Alan 		Alan Carpenter (540)
75403 2002-08-31 23:07:00 Im not an expert on such things but ....

The memory address is in hex. When a program runs it is loaded into memory and is assigned a piece of the available memory. Errors can occur if the program makes a call to another program that is expecting or using a particular memory address.

Errors can also occur if a program cant find something. DLL (Dynamic Link Library) files contain code and if the program cant find the DLL or the DLL is corrupt then errors occur. DLL's within Windows contains code that can be used by many programs. For example, if you wrote a program that required printing, you would have to write all the code to do this, unless you made a call to one of Windows DLL files that contains the code routine for printing. A way of using common code if you like.

For example this problem can be the result of a corrupt winmm.dll file - hard to tell at this early stage :-) 		parry (27)
75404 2002-08-31 23:12:00 Heres a link that tells you how RAM works...
www.howstuffworks.com 		parry (27)
75405 2002-09-01 02:31:00 Parry,

Thanks for the How Stuff works (www.howstuffworks.com) pointer. It's fun, and a good place to point some of the people who keep asking me questions. (No Mum. Not you, Mum. I know, Mum. It's other people, Mum. Yes, Mum. I like your questions, Mum. If you'd just ... sort of...remember some of the answers, Mum. I love you too, Mum.)

However, nothing there tells me anything new, and nothing covers the specific point of interpreting the error message mentioned.

I guess it's one of the "Just keep on learning till it all makes sense" things.

Cheers,
Alan 		Alan Carpenter (540)
75406 2002-09-01 03:37:00 The trouble is with some errors like fatal exception and GPF is that there are many reasons why the fault could have occured. Knowing the message then enables a search of Google or MSKB to interpret.

You could never know by seeing a memory address that its error #23 unless youve struck that one before. 		parry (27)
75407 2002-09-02 05:09:00 .









































































































































































































































































































































































































































































Thanks for the reply . Operating windows 98 . Get two different messages .
On a screen with a blue background i get oe at 016f:bff9dfff
On an explorer box the details are as follows . invalid page fault at
0000:00000001
Registers eax=00000000 cs=016f eip00000001 etlgs=00010246 ebx=006ffa5c ss=0177 esp=006ff9fo ebp=006ffa28 ecx=004b3a74 ds=0177 esi=00000000 fs=5187 edx=81710168 es=0177 edi=00000002 gs=0000 bytes at cs:eip 00 00 00 65 04 70 00 16 00 6b d0 65 04 70 00 65 stack dump 004b3a74 00000cb8 00000002 00000000 00000000 06ffa1o 00008a80 bff7363b 00000cb8 00000002 00000000 00000000 8asa2db7 00000177 006ffabc bff94407
I hope this is the information you require 		c.adkins (144)
75408 2002-09-02 05:11:00 Thanks for the reply
could you please forward me the site to go to so i can check out what this faults mean 		c.adkins (144)
75409 2002-09-02 05:50:00 There is no *particular* site, just use Google.

It appears as though that exact error can be from trying to play older 16-bit games designes for early versions of Windows or DOS...what are the applications that produce it? 		godfather (25)
1 2