Blue screen in winXP

[Hui]

i've suffered the blue screen death for my PC, the error message is:
STOP: 0x000000D1 (0XC8E17800, 0X0000000D9, 0X00000001, 0XBA330BB5)
Delta.sys - Address ..................

the Delta.sys is the driver of my sound card (M-audio AP192)

I tried a old version of the soundcard driver, but the same problem occured.

Help me plz........... :chef:

by the way, why i cann't find the minidump file in my windows folder?

 

[cpc2004]

Hu Hui,

You don't have the minidump. System event 1001/1003 is the useful diagnostic information of your problem.

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here.

Most probably you disable the minidump option.

Install pstat
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/pstat-o.asp

1) execute pstat at command mode
2) pstat > c:\pstat.txt
3) attach c:\pstat.txt here

 

[Hui]

Hi, thanks for your help,
i checked the even view, there is no 1001 even, for the but many 1003 warning even. the 1003 even said " my computer cannot renew the address from the DHCP server, my Mac address is............" (my win xp is not english version, so i translate the brief meaning

I downloaded the pstat, but i don't know why i can't upload the txt file, it also failed. so, if you don't mind, i can't send it to you by email.

Thx again..

 

[cpc2004]

Hu Hui,

At the reply screen, move downward and you will see additional option. It allows the user to attach the txt, zip and jpg.

 

[Hui]

Thx.....here is the file.... :angel:

 

[cpc2004]

Hui,

I want the system event 1003 and the application event 1003.

From the bugcheck code parameter
0x000000D1 (0XC8E17800, 0X0000000D9, 0X00000001, 0XBA330BB5)

It crashes at IRQL x'D9' which is invalid and I don't find any hits relating to delta.sys of your version. Your version of delta.sys is quite current. When do you have the blue screen? You can try another version of delta.sys. If it still crashes, the culprit is faulty ram.You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram

 

[cpc2004]

Hi Hui,

Do you have any update? The patch level of your windows is 4 years behind. Most of your device driver is out dated such as nVidia Display card driver is at 2001. Your delta.sys is also at 2001. Upgrade them to latest level.

 

[Hui]

Thx for your help~~~~

I dont know why it said the device driver is out dated such as nVidia Display card driver is at 2001, i did donwload the latest the drive for all device.

These few days, it doesnt have too many bluescreen error, instead, the xp is always freeze, mouse cursor can move on the screen, but can not click anything, and i push the "CTRL + ALT + DEL", xp no response, i push the "Num Lock" key in the keyboard, it did work.

I disable the "HyperThreading" for my P4 640, problem also exist.

So i reinstall my windows xp.....try to see if any problem exist....

 

[Vigilante]

If Windows just "freezes" still and stops responding, this can certainly be a RAM or overheat issue.
Do run the memtest86 test, perhaps run it overnight.

 

[Hui]

If Windows just "freezes" still and stops responding, this can certainly be a RAM or overheat issue.
Do run the memtest86 test, perhaps run it overnight.

I did run the standard test over more than 15 hours, my ram is 2G, it runed about 18 times, no error reported.

the detail of my PC is

CPU4 640
MB: ASUS P5WD2
Memory: kingston DDR2 4200 1024*2
Video: XFX G6600GT
Audio:M-audio AP192
Network adp: D-link 530tx

For cpu cooling, i use the TT silent 775, idle temp is 47 degree, 55 in game, is that too high?

I reinstall the XP yesterday, i will keep watching it to see if the problem gone.

 

[Vigilante]

55c is is a tad on the warm side, but I don't think is dangerous.

Well one last suggestion, regardless of running memtest86, if your PC starts crashing again, try running with just one of your RAM sticks. And if it crashes more, swap sticks.

memtest86 can test for permenent errors, but can't account for just plain incompatibility.

 

[ajwwong]

bsod with delta audiophile 192

I just installed the delta m-audio audiophile 192... and I'm getting the bsod every hour or so now.

It's because of the delta audiophile 192, but I don't know how to fix it. I'm about to burn the frigging sound card.

I get some IRQL_NOT_EQUAL_OR_LESS error with references to delta.sys -- part of the audiophile 192 driver.

Tech support at m-audio is useless and they say that it's the fault of windows. Dell Tech support says that it's because of the crappy sound card driver. Anyhow...

Here's the minidump:

If anyone has any ideas on how to fix it, please let me know.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Jun 9 17:47:22.296 2008 (GMT-7)
System Uptime: 0 days 0:12:47.850
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image delta.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for delta.sys
*** ERROR: Module load completed but symbols could not be loaded for delta.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {ca711600, 7, 1, b92f0cc5}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
<---- snip ---->

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : delta.sys ( delta+ccc5 )

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