Computing.Net > Forums > Windows XP > Computer Randomly Freezes/Restarts

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Computer Randomly Freezes/Restarts

Reply to Message Icon

Name: Mark04
Date: October 22, 2004 at 10:59:48 Pacific
OS: XP Home
CPU/Ram: AMD AthlonXP 2.0Ghz/512MB
Comment:

Hi,

Recently are computer has been randomly displaying an error message and then freezing/shutting down (resulting in a restart). Here is the error message (it appears in a DOS style window, Blue with White letters):

"If a driver is identified in the STOP Message, Disable the driver ot check for driver updates, try changing video adaptors.

Diable BIOS Memory Options such as caching or shadowing, in safe mode

Technical Info:

***STOP : 0x0000007E
*** ALCXSES.SYS Address F8131727 Base at FD0DA000, DateStamp 3f33a52a "

Any info on how I can resolve the problem? Or how I can view the options for memory caching/shadowing?

Thanks

Mark.



Sponsored Link
Ads by Google

Response Number 1
Name: cpc2000
Date: October 22, 2004 at 11:45:14 Pacific
Reply:

How often do you get the bsod? Does the bugcheck is always 0x0000007E? You can check the system event log and look for record id 1001. From your problem, the failing module is alcxses.sys. I search google with this keyword and no hit. Can you find out alcxses.sys belongs to which device driver? Upgrade it to the latest patch.

I recalled that my PC crashed with bugcheck 0x000000d1 at alcxwdm.sys which is sound card driver? Maybe alcxses.sys it is a sound card driver.


0

Response Number 2
Name: setishock
Date: October 22, 2004 at 11:51:46 Pacific
Reply:

if the message says to check the vid drivers then check the vid drivers. Ok need to know what vid card you have. Post back...

I may be crazy, but I'm not stupid...


0

Response Number 3
Name: Internet
Date: October 22, 2004 at 11:52:30 Pacific
Reply:

You can also boot into Safe Mode and select Last Known Good Configuration which will restore your drivers to a time (hopefully) when there no driver issues.


0

Response Number 4
Name: Mark04
Date: October 23, 2004 at 04:31:13 Pacific
Reply:

Hi.

How can I check the Vieo Drivers?

I went into Device Manager and there are no exclamation marks etc, i.e. everything is indicated as working normally.

It only happens every now and again (maybe once or twice a day) - sometimes I can be playing a game, othertimes I might be using word, excel or any other program and the error will appear.

Any more info please.
Thanks

Mark.


0

Response Number 5
Name: Mark04
Date: October 23, 2004 at 04:36:27 Pacific
Reply:

OK, I just looked for ID 1001 in the Event Viewer an found these entries:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x001902f8, 0xeed9b69c, 0xeed9b39c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102304-01.dmp.


The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xf7ecc727, 0xf3440b8c, 0xf344088c). A dump was saved in: C:\WINDOWS\Minidump\Mini102204-03.dmp.


The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x001902f8, 0xeed9b69c, 0xeed9b39c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102204-02.dmp.


The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x001902f8, 0xeed9b69c, 0xeed9b39c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102204-01.dmp.


There were a total of 10 found with ID 1001, seperated by a few hours each. They had either the 07 bugcheck or 24 bugcheck.

Any more info...
Thanks a lot!

Mark.


0

Related Posts

See More



Response Number 6
Name: Mark04
Date: October 23, 2004 at 06:48:02 Pacific
Reply:

Hi,

OK, After I installed all the windows updates (there were 18!!) and installed the new drivers for my NVIDIA GeForce MX 420 Card, just a few minutes ago when I was just browsing on the net, the computer restarted again.

I went into Computer Management and searched on ID1001 and found the reason for the restart was as follows:

"The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xe341a083, 0x8279258c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102304-03.dmp."

Any idea what this means? Now there is an '8' instead of 7 or 24.

Mark.


0

Response Number 7
Name: cpc2000
Date: October 23, 2004 at 07:43:50 Pacific
Reply:

You must find out the failing driver name.
Disable the automatic reboot. When BSOD occurs, if the failing module is not windows kernel, bsod displayed the failing module name. When BSOD occurs, drop the failing module and reset your PC.

Are you using XP SP2?

Hope it can help you
Albert


0

Response Number 8
Name: cpc2000
Date: October 23, 2004 at 07:58:24 Pacific
Reply:

Bugcheck x'24' is NTFS_FILE_SYSTEM and x'7E' is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. One of the possible cause of bugcheck x'24' is disk corruption. You had better run the scandisk to make sure your hard disk has no no sector.

As there have two bugcheck codes, it may be storage overlaid by a faulty device driver. If you upgraded to SP2 recently, it had better to fallback to SP1.


0

Response Number 9
Name: Mark04
Date: October 23, 2004 at 11:32:32 Pacific
Reply:

Hi.

I think I am using SP2.

What does BSOD mean and how can I check the driver that failed?

Also, just a few moments a go I got another blue screen error with this code:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

*** STOP: 0x000000D1

Any info on this appreciated. Thanks.
Mark.


0

Response Number 10
Name: cpc2000
Date: October 23, 2004 at 12:45:57 Pacific
Reply:

One of device driver is faulty like my MPEG card driver which overlay windows storage and the result is unpredicatable. Your Windows has bugcheck code 24, 50 and 7E. For your case, it is strict forward as your windows crashes so frequently. Disable the automatic recovery and let BSOD screen freeze so you can check the failing module.

Control Panel --> System -->Advance --> Startup and Recovery -> Disable Automatic Reboot

Since it is a overlay problem, if the failing module looks like windows module (such as win32k.sys, a347bus and etc) and you can ignore it. If the failing module looks like a device driver and most probably it is trouble maker. Go to google and confirm the failing module belongs to which device module. Visit the failing device driver to look for the solution.

If you do not this problem before you upgrade to SP2, fall back to SP1 is one of solution.

Hope it can help you
Albert



0

Response Number 11
Name: cpc2000
Date: October 23, 2004 at 12:54:51 Pacific
Reply:

After you disable automatic recovery. When BSOD occurs, you will see a screen like the following:

A problem has been detected and window has been shut
down to prevent damage to your computer. The problem
seems to be caused by the following file: cap256.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've see this stop error screen, restart your
computer. If this screen appears again, follow these steps:
Check to make sure any new hardware of software is
properly installed. if this is a new installation ask your hardware or
software namfacturer for any windows updates you might need. If problems
continue, disable or remove any newly installed hardware or software
Disable BIOS memory option such as caching or shadowing, if you need
to use safe mode to remove or disable components restart your computer,
press F8 to select advanced startup options, and then select safe mode

STOP: 0x000000050 (OXF9CBC4AB, 0x00000000, OXF9CBC4AB, xxxxxxxx)
cap256.sys-address: F9CBC4AB base at F9CBA000 Date stamp 00000000

where cap256.sys is Grandmars MPEG card device driver.


0

Response Number 12
Name: cpc2000
Date: October 23, 2004 at 12:59:20 Pacific
Reply:

BSOD stands for blue screen of death


0

Response Number 13
Name: Mark04
Date: October 23, 2004 at 13:13:02 Pacific
Reply:

Hi.

Another error occured before, and i got BSOD but with a different code this time. I went to Viewer and this was the data:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xffffffdf, 0x00000002, 0x00000001, 0xf8c11eb9). A dump was saved in: C:\WINDOWS\Minidump\Mini102304-05.dmp

What does d1 mean??

Also, I didnt notice any module names in the BSOD.

Mark.


0

Response Number 14
Name: cpc2000
Date: October 23, 2004 at 20:37:39 Pacific
Reply:

Bugcheck code D1 is similar to bugcheck code 0A. The only difference BSOD usually shows the failing module and Bugcheck 0A cannot show the failing module because it fails at Windows Kernel.

The system event log 1001 does not have the failing module. You can find failing module from the BSOD or use windbg to format the dump. If you do not disable the automatic recovery, the BSOD screen just blink and unless you have a quick eye which catch the failing module name. After you disable the automatic recovery, the system freeze and you can write down the failing module from the blue screen. If the failing module is within windows kernel (ie ntoskrnl.exe), no failing module is displayed. I hope you can find out the fauiling module at the next occurence of BSOD.

Good Luck
Albert


0

Sponsored Link
Ads by Google
Reply to Message Icon

After installing SP2 does... several plattforms



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows XP Forum Home


Sponsored links

Ads by Google


Results for: Computer Randomly Freezes/Restarts

Computer Randomly Freezes www.computing.net/answers/windows-xp/computer-randomly-freezes/79428.html

Computer randomly freezing - win2k & xp www.computing.net/answers/windows-xp/computer-randomly-freezing-win2k-amp-xp/5402.html

Random freeze and strange noise www.computing.net/answers/windows-xp/random-freeze-and-strange-noise/143982.html