Multiple Blue Screen Stop Errors, Various kinds, happens ALOT

Status
Not open for further replies.

HeirRaktus

Posts: 22   +0
It seems everytime I try to use a graphics intensive program my computer shuts down into a blue screen error, and sometimes even when its sitting all alone it will happen. My computer got shocked a long time ago, but since then I have replaced every single part from the hard drives to the motherboard to the video card to the memory...


erm, I tried the Windbg, but I couldnt get it to recognize the symbols so below is the attached minidump files I couldnt read but suffer from. Since the board upload doesnt support .RAR heres a link to my minidump files, 7 of them:

http://rapidshare.de/files/11853101/Minidump.rar.html
 
I think you are having a driver issue here. Please upgrade your videocard and chipset drivers. Disable AGP fastwrites, slow down the AGP slot to 4x and try again.

Let us know if you were able to resolve your problem.

Couldnt access the site though.
 
Hmmm, well heres 5 then

and another 5

as for the drivers, I just bought the videocard yesterday, installed the drivers it came with....

How do I go about turning off fastwrite and turning down the AGP status?
 

Attachments

  • Mini010706-05.zip
    74.9 KB · Views: 7
  • Mini010706-10.zip
    77.6 KB · Views: 5
Hello and welcome to Techspot.

Your minidumps crash with the following errors.

ati2mtag.sys. Video drivers. Bugcheck of 8E.

2x. win32k.sys. Multi-User Win32 Driver. Bugcheck of 8E.

Pool corruption. Bugcheck of C5.

NDIS.sys. NDIS 5.1 wrapper driver. Bugcheck of D1.

ntoskrnl.exe. Windows nt & kernel system file. Bugcheck of 0A.

Net4100.sys. Your modem driver. Bugcheck of D1

ALCXWDM.SYS. Onboard audio drivers. Bugcheck of 0A.

ALCXWDM.SYS. Onboard audio driver. Bugcheck of D1.

ALCXWDM.SYS. Onboard audio driver. Bugcheck of 7E.

Due to what would seem to be the random nature of your crashes. It could be that you have a ram/pagefile problem.

Go HERE and follow the instructions, including creating a new pagefile. See reply #11 for instructions for this.

Regards Howard :wave: :wave:
 
I dont know if this means anything, but this is what one of the crash dump's read out in WinDBG





DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8053d76d, address which referenced memory

Debugging Details:
------------------


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+154
8053d76d 8913 mov [ebx],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8053d885 to 8053d76d

STACK_TEXT:
f7c7de4c 8053d885 84f38aa8 00000000 8511d008 nt!ExDeferredFreePool+0x154
f7c7de84 804e2414 8511d008 00000000 86125330 nt!ExFreePoolWithTag+0x413
f7c7dea0 f78b6f55 8511d008 863aca28 863ab0a4 nt!IopFreeIrp+0xf0
f7c7deb4 f78b424d 863aca28 863ae0e8 863aca28 CLASSPNP!DestroyTransferPacket+0x43
f7c7ded0 f78b2fdf 863ae030 023aca28 8511d09f CLASSPNP!EnqueueFreeTransferPacket+0x114
f7c7def4 804f30ae 00000000 8511d008 863aca28 CLASSPNP!TransferPktComplete+0x1d2
f7c7df24 f77e34ee 8512e200 8511d008 f7c7df6c nt!IopfCompleteRequest+0xa0
f7c7df34 f77e2d25 8512e200 00000001 00000000 SCSIPORT!SpCompleteRequest+0x5c
f7c7df6c f77e32c3 863e2ae8 8512e200 f7c7dfdf SCSIPORT!SpProcessCompletedRequest+0x39f
f7c7dfe0 804f72eb 863e2aa4 863e2a30 00000000 SCSIPORT!ScsiPortCompletionDpc+0x2a5
f7c7dff4 804f6fd3 eda3fd44 00000000 00000000 nt!KiRetireDpcList+0x30
f7c7dff8 eda3fd44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804f6fd3 00000000 00000009 bb835675 00000128 0xeda3fd44


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+154
8053d76d 8913 mov [ebx],edx

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: Pool_corruption

SYMBOL_NAME: nt!ExDeferredFreePool+154

MODULE_NAME: Pool_Corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+154

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+154

Followup: Pool_corruption
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f7fa40b1, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7fa40b1, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: f7fa40b1

CURRENT_IRQL: 2

FAULTING_IP:
+fffffffff7fa40b1
f7fa40b1 ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f77238d3 to f7fa40b1

TRAP_FRAME: f7c7df4c -- (.trap fffffffff7c7df4c)
ErrCode = 00000000
eax=86082af0 ebx=85f97498 ecx=85f97498 edx=00000002 esi=86072f76 edi=86082af0
eip=f7fa40b1 esp=f7c7dfc0 ebp=00000000 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
f7fa40b1 ?? ???
Resetting default scope

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7c7dfbc f77238d3 00000000 86072df8 00000000 0xf7fa40b1
f7c7dfe0 804f72eb 86072f9e 86072f76 7a1d95b0 NDIS!ndisMTimerDpcX+0x75
f7c7dff4 804f6fd3 f79f1d44 00000000 00000000 nt!KiRetireDpcList+0x30
f7c7dff8 f79f1d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
804f6fd3 00000000 00000009 bb835675 00000128 0xf79f1d44


FAILED_INSTRUCTION_ADDRESS:
+fffffffff7fa40b1
f7fa40b1 ?? ???

FOLLOWUP_IP:
NDIS!ndisMTimerDpcX+75
f77238d3 32d2 xor dl,dl

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NDIS!ndisMTimerDpcX+75

MODULE_NAME: NDIS

IMAGE_NAME: NDIS.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dc561

STACK_COMMAND: .trap fffffffff7c7df4c ; kb

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_NDIS!ndisMTimerDpcX+75

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_NDIS!ndisMTimerDpcX+75

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

Ah, sorry Howard, I just got the debug thing working and figured Id post some to help out, almost missed your post...


Yeah, I did the page thing... went to 0, restarted, defraged, put it back up again...


Still getting the errors though
 
I am aware of the crash dump analysis, as I`ve just looked at your minidumps.

That`s why I think you may have a ram/pagefile problem.

Follow the instructions in the link I gave you, and let us know the results.

Regards Howard :)
 
Like I said, I did the page thing

I cant do the mem thing though... BUT, I just bought new memory... so It ought to be good...
 
no floppy or handy re-writeable CD's

as for PSU... the one that came with the case...350 watt

and I have OLDER PSU's from computers that are some 10 years old... but I really dont know enough about hardware to want to mess with motherboard power connections.
 
Your old psu`s probably won`t be of any use.

That 350watt psu that came with your case, may be suspect.

Depending on what hardware you`re running. it might not be putting out enough power for your system.

The problem with generic psu`s is. Even though it may be rated at 350watts. It probably isn`t capable of putting out anywhere near that amount of power.

Even a good quality psu, will only achieve around 70% efficiency.

Take a look at this psu wattage calculator HERE

Also, look at this article on psu`s. The psu thread.

If you can`t test your ram, or try a different psu. I don`t know what else to suggest.

Regards Howard :)
 
yeah, Im at wits end here myself, Ive litterally replaced every piece of hardware and wiped the computer completely to no avail...

well, If I got this right, at its most my computers using 332w off of my 350w PSU, though it says my default power usage is 295w
 
That would explain things.

Just suppose that your cheap no name psu is at most 60% efficient.

That means it is only capable of putting out 210Watts of sustainable power.

I think we may have found the root cause of your problems.

Regards Howard :)
 
Of course, the ONE thing I havent replaced.... Ive spent 600 bucks upgrading to repair a 600 dollar computer, lol.

Well, if its not this, then youll hear from me again to be sure
 
I will look into this post when you have tried howards things. I might have an alternate solution for you. Driver related. But lets c what comes out first.

You asked how you can change agp fastwrites and reads and how to slow down the agp slot.

download rivatuner at http://www.guru3d.com/rivatuner

When the crashes are getting less by using this tool you propably have to upgrade your nvidia driver.

Good luck.
 
well, I wont be able to try his for some time, so go ahead and tell me yours (Id need to buy the PSU and I dont have the cash atm)

alright, shes down to 4x and fastwrites were already off

Not gonna tell me your idea X?
 
Sry, am a little less online last days, very busy developing stuff...

Anyways, you lowered the agp rate, you lowered agp fast writes and reads, did u have less crashes?

Have you updated your chipset drivers? audio drivers? and have you upgraded to the latest nvidia drivers.

The video drivers which came with your card arent probably the latest.

Go to www.windowsupdate.com and c if there are any additional HARDWARE driver updates for your video card. These are WHQL drivers and certified by msoft. Try em.
 
a friend of mine asked about chipset drivers too, I really have no idea if mine are the latest or not...

oh yeah, and less crashes but they still happen more than they should

I also have this annoying question mark next to my USB Imaging device in my device managers list...

windows update says 0 to install sooooo....
 
Ok i will help you get your drivers but you have to tell me the following:

a) what videocard do you have
b) what is your mobo type id and manufacturer
c) what is your audiocard typen id and manufacturer

I know i can extract the answers from the minidumps but dont have microsoft debugging tools installed here.
 
allright, here we go.

First you should disable your onboard graphics chip in the bios.

download chipset drivers;
http://www.viaarena.com/Driver/via_hyperionpro_v504a.zip
These are the absolute latest!

download your usb driver;
http://www.viaarena.com/Driver/VIA_USB2_V270p1-L-M.zip

download the nvidia driver;
http://www.nvidia.com/content/drivers/drivers.asp
select graphics driver, geforce and tnt, select windows xp

download the audio driver;
http://www.pcchips.com.tw/PCCWeb/Pr...uID=16&LanID=0&DetailID=305&DetailName=Driver
and select the audio driver.

download your onboard lan driver;
http://www.pcchips.com.tw/PCCWeb/Pr...uID=16&LanID=0&DetailID=305&DetailName=Driver

When you have downloaded them all, install them in the following order:

chipset, usb, lan, audio, nvidia.

If you still have crashes, post your new minidumps. Be sure to delete the current ones first.
 
Uhm, stupid question, but how do I disable my chipset in bio's? lol

I would really HATE to poke around in there without knowin...
 
I ment your onboard graphic card. I do not know your bios, is it phoenix bios? look for a settings called "disable onboard vga" or something.
 
The third minidump is corrupted.

Download ac'97 driver from realtek itself

http://www.realtek.com.tw/downloads/dlac97-2.aspx?lineid=5&famid=12&series=8&Software=True

Select the driver only, extract, setup or update the current driver.

Test again.

When that doesnt work, disable the realtek ac'97 using device manager.

Test again.

Post the new loggings, they cant be audio related anymore, lets c what else we get.

Second minidump is bug in driver. Driver referred to a memory location which is unavailable or not allowed for read/write by the current kernel thread (may be synchronisation issue).

Try the above,... let us know results.

Did the audio driver from realtek solve your problems?

Be sure to notify us about the status.

(i am not monitoring this thread activily)
 
Status
Not open for further replies.
Back