STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000)

  • Thread starter GuildWars
  • Start date
In summary, the user is experiencing problems with entering missions in the game Guild Wars. Every time they try to enter a mission, their computer crashes, their screen turns blue, and they are told that their sound card is malfunctioning and to remove the video card drivers and put them back in. The user's sound card has been known to malfunction, and they have also had problems with their microphone.
  • #1
GuildWars
4
0
Every time i try to enter a mission on the computer game Guild Wars, my sound freezes, my screen turns blue and i get a message saying something like...

A problem has been detected and windows has been shut down to prevent damage blah blah blah blah, Technical information ***STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000) ***: ialmdev5.dll 0 address BF04DF7B base at BF042000, DateStamp 43304C9
Beginning dump of physical memory
Physical memory dump complete.

(taken from other post on this site)
this happens nearly every time i try to enter a mission. i chatted with dell, they told me to remove the video card drivers put it in again, and it should work. but no avail! My sound card too messes up sometimes when I am on Ventrilo it says use direct sound input which i already have checked off! A few sound card files and video card files have the names of them in blue lettering. might this be the problem? help me please!
I have Windows Xp Media Center Edition on my Dell XPS M140 Laptop. Any help at all is appreciated.My specs are...
------------------
System Information
------------------
Time of this report: 6/26/2007, 23:33:26
Machine name: LIAM
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: MXC051
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A04
Processor: Intel(R) Pentium(R) M processor 1.73GHz
Memory: 504MB RAM
Page File: 468MB used, 759MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: DirectSound test results: All tests were successful.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
Manufacturer: Intel Corporation
Chip type: Intel(R) 915GM/GMS,910GML Express Chipset
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_2592&SUBSYS_01B51028&REV_03
Display Memory: 128.0 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ialmrnt5.dll
Driver Version: 6.14.0010.4693 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 9/15/2006 17:09:00, 45694 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ialmnt5.sys
Mini VDD Date: 9/15/2006 17:16:48, 1173468 bytes
Device Identifier: {D7B78E66-66D2-11CF-CD61-BF21A2C2CB35}
Vendor ID: 0x8086
Device ID: 0x2592
SubSys ID: 0x01B51028
Revision ID: 0x0003
Revision ID: 0x0003
Video Accel:
Deinterlace Caps: n/a
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Not Available
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run

-------------
Sound Devices
-------------
Description: SigmaTel Audio
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_8384&DEV_7690&SUBSYS_102801B5&REV_1022
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: sthda.sys
Driver Version: 5.10.4633.0000 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 7/29/2005 09:12:44, 1019960 bytes
Other Files:
Driver Provider: SigmaTel
HW Accel Level: Full
Cap Flags: 0xB5B
Min/Max Sample Rate: 44100, 96000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: All tests were successful.

---------------------
Sound Capture Devices
---------------------
Description: SigmaTel Audio
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: sthda.sys
Driver Version: 5.10.4633.0000 (English)
Driver Attributes: Final Retail
Date and Size: 7/29/2005 09:12:44, 1019960 bytes
Cap Flags: 0x41
Format Flags: 0xCC0

-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Poll w/ Interrupt: No
Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x2659
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/4/2004 01:08:44, 57600 bytes
| Driver: usbd.sys, 8/10/2004 07:00:00, 4736 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 01:14:38, 52736 bytes
| Driver: kbdclass.sys, 8/4/2004 00:58:34, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 00:58:34, 24576 bytes
|
+ Synaptics PS/2 Port Pointing Device
| Matching Device ID: *pnp0f13
| Upper Filters: SynTP
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 01:14:38, 52736 bytes
| Driver: mouclass.sys, 8/4/2004 00:58:34, 23040 bytes
| Driver: SynTP.sys, 6/24/2005 08:19:52, 190560 bytes
| Driver: SynTPAPI.dll, 6/24/2005 08:23:40, 90202 bytes
| Driver: SynTPFcs.dll, 6/24/2005 08:37:52, 69722 bytes
| Driver: SynCOM.dll, 6/24/2005 08:22:36, 82013 bytes
| Driver: SynCtrl.dll, 6/24/2005 08:23:00, 114688 bytes
| Driver: SynTPLpr.exe, 6/24/2005 08:38:02, 77914 bytes
| Driver: SynTPCpl.dll, 6/24/2005 08:26:34, 6058074 bytes
| Driver: SynCntxt.rtf, 6/24/2005 08:24:38, 3473903 bytes
| Driver: SynZMetr.exe, 6/24/2005 08:18:44, 163840 bytes
| Driver: SynMood.exe, 6/24/2005 08:18:34, 147456 bytes
| Driver: SynTPEnh.exe, 6/24/2005 08:36:40, 729178 bytes
| Driver: SynTPCOM.dll, 6/24/2005 08:24:12, 41063 bytes
| Driver: Tutorial.exe, 6/24/2005 08:38:26, 212992 bytes
| Driver: InstNT.exe, 6/24/2005 08:40:34, 69632 bytes
| Driver: SynISDLL.dll, 6/24/2005 08:38:48, 548864 bytes
| Driver: SynUnst.ini, 6/29/2005 08:11:50, 189951 bytes
| Driver: SynTPCo2.dll, 6/24/2005 08:40:22, 81920 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x09DA, 0x0006
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 8/4/2004 00:58:34, 23040 bytes
| Driver: mouhid.sys, 8/17/2001 14:48:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 00:58:34, 23040 bytes

----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK

-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Modem Service Provider: Conexant HDA D110 MDC V.92 Modem
DirectPlay8 TCP/IP Service Provider: Wireless Network Connection - IPv4 -

-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s

-------------------------
DirectPlay Lobbyable Apps
-------------------------

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 23.7 GB
Total Space: 70.3 GB
File System: NTFS
Model: FUJITSU MHV2080AH

Drive: D:
Model: TSSTcorp CDRW/DVD TSL462C
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/10/2004 07:00:00, 49536 bytes

--------------
System Devices
--------------
Name: Intel(R) PRO/Wireless 2200BG Network Connection
Device ID: PCI\VEN_8086&DEV_4220&SUBSYS_27218086&REV_05\4&2FA23535&0&18F0
Driver: n/a

Name: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
Device ID: PCI\VEN_8086&DEV_2792&SUBSYS_01B51028&REV_03\3&61AAA01&0&11
Driver: n/a

Name: Microsoft UAA Bus Driver for High Definition Audio
Device ID: PCI\VEN_8086&DEV_2668&SUBSYS_01B51028&REV_03\3&61AAA01&0&D8
Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 5.10.0000.5011 (English), 8/12/2004 19:45:54, 137728 bytes

Name: Intel(R) 82801FB/FBM PCI Express Root Port - 2662
Device ID: PCI\VEN_8086&DEV_2662&SUBSYS_00000000&REV_03\3&61AAA01&0&E1
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/4/2004 01:07:48, 68224 bytes

Name: Intel(R) 82801FB/FBM PCI Express Root Port - 2660
Device ID: PCI\VEN_8086&DEV_2660&SUBSYS_00000000&REV_03\3&61AAA01&0&E0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/4/2004 01:07:48, 68224 bytes

Name: Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C
Device ID: PCI\VEN_8086&DEV_265C&SUBSYS_01B51028&REV_03\3&61AAA01&0&EF
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/10/2004 07:00:00, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/10/2004 07:00:00, 7168 bytes

Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265B
Device ID: PCI\VEN_8086&DEV_265B&SUBSYS_01B51028&REV_03\3&61AAA01&0&EB
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 57600 bytes

Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265A
Device ID: PCI\VEN_8086&DEV_265A&SUBSYS_01B51028&REV_03\3&61AAA01&0&EA
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 57600 bytes

Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
Device ID: PCI\VEN_8086&DEV_2659&SUBSYS_01B51028&REV_03\3&61AAA01&0&E9
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 57600 bytes

Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
Device ID: PCI\VEN_8086&DEV_2658&SUBSYS_01B51028&REV_03\3&61AAA01&0&E8
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:44, 57600 bytes

Name: Intel(R) 82801FBM Ultra ATA Storage Controllers - 2653
Device ID: PCI\VEN_8086&DEV_2653&SUBSYS_01B51028&REV_03\3&61AAA01&0&FA
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 15:51:52, 3328 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (English), 8/4/2004 00:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/4/2004 00:59:44, 95360 bytes

Name: Intel(R) 82801FBM LPC Interface Controller - 2641
Device ID: PCI\VEN_8086&DEV_2641&SUBSYS_00000000&REV_03\3&61AAA01&0&F8
Driver: C:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 8/17/2001 15:58:02, 35840 bytes

Name: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
Device ID: PCI\VEN_8086&DEV_2592&SUBSYS_01B51028&REV_03\3&61AAA01&0&10
Driver: C:\WINDOWS\system32\DRIVERS\ialmnt5.sys, 6.14.0010.4693 (English), 9/15/2006 17:16:48, 1173468 bytes
Driver: C:\WINDOWS\system32\ialmrnt5.dll, 6.14.0010.4693 (English), 9/15/2006 17:09:00, 45694 bytes
Driver: C:\WINDOWS\system32\ialmdnt5.dll, 6.14.0010.4693 (English), 9/15/2006 17:08:52, 121467 bytes
Driver: C:\WINDOWS\system32\ialmdev5.dll, 6.14.0010.4693 (English), 9/15/2006 17:08:42, 238650 bytes
Driver: C:\WINDOWS\system32\ialmdd5.dll, 6.14.0010.4693 (English), 9/15/2006 17:15:46, 956026 bytes
Driver: C:\WINDOWS\system32\igxpxa32.cpa, 9/15/2006 16:44:44, 524850 bytes
Driver: C:\WINDOWS\system32\igxpxa32.vp, 9/15/2006 16:44:44, 929 bytes
Driver: C:\WINDOWS\system32\igxpxk32.vp, 9/15/2006 16:44:44, 58704 bytes
Driver: C:\WINDOWS\system32\igxpxs32.vp, 9/15/2006 17:59:54, 23296 bytes
Driver: C:\WINDOWS\system32\oemdspif.dll, 3.00.0000.4693 (English), 9/15/2006 16:54:26, 57344 bytes
Driver: C:\WINDOWS\system32\hccutils.dll, 3.00.0000.4693 (English), 9/15/2006 16:49:12, 73728 bytes
Driver: C:\WINDOWS\system32\igfxsrvc.dll, 3.00.0000.4693 (English), 9/15/2006 16:50:16, 61440 bytes
Driver: C:\WINDOWS\system32\igfxsrvc.exe, 3.00.0000.4693 (English), 9/15/2006 16:50:14, 163840 bytes
Driver: C:\WINDOWS\system32\igfxpph.dll, 3.00.0000.4693 (English), 9/15/2006 16:53:18, 143360 bytes
Driver: C:\WINDOWS\system32\igfxcpl.cpl, 3.00.0000.4693 (English), 9/15/2006 16:53:06, 81920 bytes
Driver: C:\WINDOWS\system32\igfxcfg.exe, 3.00.0000.4693 (English), 9/15/2006 16:52:58, 450560 bytes
Driver: C:\WINDOWS\system32\igfxdev.dll, 3.00.0000.4693 (English), 9/15/2006 16:49:26, 139264 bytes
Driver: C:\WINDOWS\system32\igfxdo.dll, 3.00.0000.4693 (English), 9/15/2006 16:50:28, 86016 bytes
Driver: C:\WINDOWS\system32\igfxtray.exe, 3.00.0000.4693 (English), 9/15/2006 16:53:36, 94208 bytes
Driver: C:\WINDOWS\system32\igfxzoom.exe, 3.00.0000.4693 (English), 9/15/2006 16:54:06, 114688 bytes
Driver: C:\WINDOWS\system32\hkcmd.exe, 3.00.0000.4693 (English), 9/15/2006 16:50:22, 77824 bytes
Driver: C:\WINDOWS\system32\igfxress.dll, 3.00.0000.4693 (English), 9/15/2006 16:53:24, 1503232 bytes
Driver: C:\WINDOWS\system32\igfxpers.exe, 3.00.0000.4693 (English), 9/15/2006 16:54:22, 118784 bytes
Driver: C:\WINDOWS\system32\igfxrchs.lrc, 3.00.0000.4693 (English), 9/15/2006 16:54:34, 81920 bytes
Driver: C:\WINDOWS\system32\igfxrcht.lrc, 3.00.0000.4693 (English), 9/15/2006 16:54:34, 81920 bytes
Driver: C:\WINDOWS\system32\igfxrdeu.lrc, 3.00.0000.4693 (English), 9/15/2006 16:54:38, 155648 bytes
Driver: C:\WINDOWS\system32\igfxrenu.lrc, 3.00.0000.4693 (English), 9/15/2006 16:49:30, 139264 bytes
 
Last edited:
Computer science news on Phys.org
  • #2
Sounds like a driver problem at ialmdev5.dll, or a hardware problem.

Can you search your video/sound card manufacturer's site for updated drivers?
 
Last edited:
  • #3
yes i did that and it still happened. i just installed new chipset drivers and I am hoping that will solve it.
 
  • #4
Don't a lot of games publish a list of issues with known hardware? Could it be some of the hardware isn't playing nice with the game? Have you tried contacting the maker of the game?
 
  • #5
i have not. ill check up on that.
 
  • #6
Try disabling the sound card driver (in device manager) and try to load the level again. If that solves the problem, perhaps you have a bad sound card driver or a bad sound card.
 
  • #7
GuildWars said:
Every time i try to enter a mission on the computer game Guild Wars, my sound freezes, my screen turns blue and i get a message saying something like...

A problem has been detected and windows has been shut down to prevent damage blah blah blah blah, Technical information ***STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000) ***: ialmdev5.dll 0 address BF04DF7B base at BF042000, DateStamp 43304C9
Beginning dump of physical memory
Physical memory dump complete.

(taken from other post on this site)

Well, I encountered this once in the past. Not only does game, but whenever I run a programme that eats up a lot of memory, or which is slow to run, I always receive that message, or the computer will freeze. And it turned out that the internal fan of my CPU had been dead. You should also check the fan to see if there is something wrong with it. :)
 
  • #8
A problem has been detected and windows has been shut down to prevent damage blah blah blah blah, Technical information ***STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000) ***: ialmdev5.dll 0 address BF04DF7B base at BF042000, DateStamp 43304C9
Beginning dump of physical memory
Physical memory dump complete.

I've repeatedly experienced the same problem as well. I hired a technician to look at the problem, and he told me that it could be either due to faulty RAM or a CPU cooling problem. When I replaced the RAM, the problem seems to have disappeared.
 
  • #9
Try different video modes/resolutions/detail levels/etc. You may be out of luck, though - trying to play games on an integrated video adapter is a crapshoot at best.
 
  • #10
Yep, like others have said, cooling or inadequate power, I've experience it myself too, but happens during the game.
 
  • #11
Well no, I mean flat-out incompatibility issues.
 
  • #12
Really? My boy is getting this error playing WoW. We've tried everything.

The 'puter's a <2 year old Dell. Should I check the fan and memory? (Well, can't checK the memory without replacing it...)
 
  • #13
/rant: In general Microdaft don't write software to be compatible with games, why should they? They expect everyone to play catch up which is kind of understandable under the monoploy, I mean monopoly system. So drivers come out that suit the system not a system that suits anyone but generic.

I am a cynic about MS though, Vista is worse than XP, what do you expect, they release an alpha version and expect everyone else to do their testing for them, :cool: but wish their was something better than Microdaft.

I seriously doubt it's an issue with your computer, it's an issue with the lag between a release, often x million years between game companies and the imperialist masters :biggrin:

This would never happen under Mac! or any other OS

I don't have a Mac by the way, I'm not a fundamentalist :biggrin: although I appreciate their ethics. \rant

gaming_addict said:
Yep, like others have said, cooling or inadequate power, I've experience it myself too, but happens during the game.

What sort of chip do you have? Is it an old P4 because they run hot so, it's not unusual for them to overheat, they were designed to collapse at 105 degrees C+ which for a chip is unimaginably hot, most run now at 70 degrees or less and collapse at nothing over anything close, so the fans cope better.

If your PC's old and like mine with an old chip try using a gel on your CPU to cool it down they are available. I get overheating problems but not so much now.
 
Last edited:
  • #14
Gel?(10 char)
 
  • #15
If the new drivers ones don't work try an older set of video and then soundcard drivers , you may need to use a set which are more than a year old.
Sometimes the game manufacturers will specify a version that was tested with the game and known to work.
 
  • #16
DaveC426913 said:
Gel?(10 char)

I think it's a thermal paste. That's what the techie I hired applied to the processor. My guess is that it increases the thermal conductivity, and let's the CPU cools faster.
 
  • #17
DaveC426913 said:
Really? My boy is getting this error playing WoW. We've tried everything.

The 'puter's a <2 year old Dell. Should I check the fan and memory? (Well, can't checK the memory without replacing it...)
If you have the problem in WoW, you may be in luck. Others, not so lucky: http://www.intel.com/support/graphics/intel945g/

That's one particular Intel integrated video adapter - others may have different compatibility lists/issues. Find out which you have and search for it.
 
Last edited:
  • #18
Schrodinger's Dog said:
/rant: In general Microdaft don't write software to be compatible with games, why should they?
This isn't a Microsoft problem, it is an Intel problem (and partially a user error problem). Microsoft wrote the API (directX), essentially the programming language most games are programmed in. It is up to the video card/adapter manufacturer to write drivers that translate the game's commands into whatever the card needs to do what is required of it. Since integrated video adapters are not really meant for games anyway and simply aren't capable of doing what is required of them, Intel doesn't put any effort into making them compatible.

And that's where the user error comes in: people need to do their homework before buying a PC so they know what they need to buy to be able to play games. You need a discrete (non-integrated) video card with the power and software support required to play games. Granted that's partially a matter of misleading advertising, but people need to learn to read past advertising in general.
 
  • #19
DaveC426913 said:
Gel?(10 char)

Coolant gell, it comes with these chips apparently, but sometimes it deteriorates. Its a sort of gooey silica gel that provides extra coolant to hot chips like some P4's.

My chips currently running at 85 degrees. which is very hot, but when you consider it's got 20 more degrees to go before it is destroyed it puts it into perspective, it doesn't help the fans though which are always working at top RPM: 5625

Type speed fan into google and you'll get a nifty little prog that shows you your heat(deg C) and fan speeds. I have set my warning temp close to the shut down temp to stop getting that annoying siren, because I know these chips are exceptionally hot running and so am not worried.
russ_watters said:
This isn't a Microsoft problem, it is an Intel problem (and partially a user error problem). Microsoft wrote the API (directX), essentially the programming language most games are programmed in. It is up to the video card/adapter manufacturer to write drivers that translate the game's commands into whatever the card needs to do what is required of it. Since integrated video adapters are not really meant for games anyway and simply aren't capable of doing what is required of them, Intel doesn't put any effort into making them compatible.

And that's where the user error comes in: people need to do their homework before buying a PC so they know what they need to buy to be able to play games. You need a discrete (non-integrated) video card with the power and software support required to play games. Granted that's partially a matter of misleading advertising, but people need to learn to read past advertising in general.

I don't care I haven't ranted about Microsoft in ages, stop ruining my fun :smile: I'm sorry with the rant tags I didn't think anyone would take me seriously my bad.

That's some interesting information though, I didn't know you could actually buy graphics cards that are not designed for games. Since the latest ones here at least are all designed specifically for games and come with some graphics heavy game for free usually as well.

I agree with the bolded part 100%
 
Last edited:
  • #20
DaveC426913 said:
Gel?(10 char)
http://www.dansdata.com/goop.htm
"Thermal transfer compound", if you want to be formal. It's the stuff you put between your CPU and your CPU cooler, to aid in the transfer of heat from the former to the latter.
Since most of the people here having problems are using stock systems, it is highly unlikely that heat is the issue.
 
  • #21
Schrodinger's Dog said:
I don't care I haven't ranted about Microsoft in ages, stop ruining my fun :smile: I'm sorry with the rant tags I didn't think anyone would take me seriously my bad.
That's ok - I did it more for everyone's information. Most people don't know this stuff...
That's some interesting information though, I didn't know you could actually buy graphics cards that are not designed for games. Since the latest ones here at least are all designed specifically for games and come with some graphics heavy game for free usually as well.
Prior to about 1996 there was no such thing as a 3d graphics card - they were all 2d only. 3d was accomplished via add-in cards for a few years after that (up to the Voodoo 2). The first 2d/3d cards were the Voodoo Banshee and Riva TNT in late 1998. In many ways, the first "real" 3d game was http://en.wikipedia.org/wiki/Quake#Quake_engine" in 1996. It is only in about the last 5 years that 2d-only cards and adapters went away completely and all integrated chips at least pay lip-service to doing 3d...

But 3d rendering requires some serious processing power and specialized instructions and it isn't reasonable to expect a $5 chip covering 2 square inches of your motherboard to provide even the same order of magnitude of performance as a $200 video card with dedicated memory, a real processor, and a short, direct pathway between them.

Besides expanding their monopoly, part of MS's reason for creating dX was to integrate the api into the operating system better and standardize it, theoretically making games easier to program. This gave them an easy into the console market, as well...
 
Last edited by a moderator:
  • #22
Check the ram. Thats what messed up my comp too. I have two RAM cards though, so to check them was easy. How do you get 504MB though? I thought it only came in multiples of 16 or 8?
 
  • #23
512-8 (dedicated to video)=504
 
  • #24
okay guys, ill try and fix the problem by taking it to comp usa or somewhere hopefully they can tell me whether its the RAM or the fan..
 

Related to STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000)

What does "STOP: 0x0000008E (0xC000005, 0XBF04DF7B, 0xED924B18 0X000000000)" mean?

This is a blue screen error on a Windows computer, also known as the "blue screen of death" or BSOD. The numbers and letters within the parentheses represent the specific error codes and memory addresses that can help identify the cause of the error.

What causes this error to occur?

The most common causes of this error are faulty hardware (such as RAM or hard drive), outdated or corrupt device drivers, and software conflicts. It can also occur due to viruses or malware, overheating, or a damaged Windows installation.

How can I fix this error?

The first step is to restart your computer. If the error persists, try booting into safe mode and running a virus scan. You can also try updating or reinstalling device drivers, performing a system restore, or using a diagnostic tool to check for hardware issues. If all else fails, you may need to reinstall Windows.

How can I prevent this error from happening again?

To prevent this error from occurring, it's important to regularly update your computer's hardware drivers and software. It's also a good idea to run regular virus scans and keep your computer cool to prevent overheating. Backing up important files and keeping them on an external drive can also help prevent data loss in case of a BSOD.

Is this error dangerous?

This error can be dangerous if it occurs frequently and causes your computer to crash. It can also lead to data loss if it occurs while important files are being accessed. However, if it only happens once or twice, it is not typically a cause for major concern.

Similar threads

  • Computing and Technology
Replies
4
Views
16K
  • Programming and Computer Science
Replies
2
Views
2K
  • Nuclear Engineering
Replies
7
Views
629
Replies
3
Views
2K
  • Nuclear Engineering
Replies
7
Views
2K
Replies
58
Views
3K
  • Astronomy and Astrophysics
Replies
2
Views
1K
  • Computing and Technology
Replies
4
Views
3K
  • Nuclear Engineering
Replies
1
Views
3K
  • Computing and Technology
Replies
1
Views
7K
Back
Top