an unknown blue screen

Ok so i was in the middle of installing counter strike source, each time i would go to disc 2 during the installation, I would get this bsod while it was installing. I cant take any pictures because it goes by way too fast, I got the minidump file if someone wants to take a look at it and help me out.

Minidump.zip <--- mini dump

Bugcheck:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81cfa010, The address that the exception occurred at
Arg3: 88b57b78, Exception Record Address
Arg4: 88b57874, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExAllocatePoolWithTag+4ca
81cfa010 895804 mov dword ptr [eax+4],ebx
EXCEPTION_RECORD: 88b57b78 -- (.exr 0xffffffff88b57b78)
ExceptionAddress: 81cfa010 (nt!ExAllocatePoolWithTag+0x000004ca)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 76413d43
Attempt to write to address 76413d43
CONTEXT: 88b57874 -- (.cxr 0xffffffff88b57874)
eax=76413d3f ebx=84070978 ecx=84074124 edx=00000001 esi=84070034 edi=aecc36f0
eip=81cfa010 esp=88b57c40 ebp=88b57c8c iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!ExAllocatePoolWithTag+0x4ca:
81cfa010 895804 mov dword ptr [eax+4],ebx ds:0023:76413d43=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 76413d43
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d43868
Unable to read MiSystemVaType memory at 81d23420
76413d43
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+4ca
81cfa010 895804 mov dword ptr [eax+4],ebx
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 81dee583 to 81cfa010
STACK_TEXT:
88b57c8c 81dee583 00000001 00000900 20204d43 nt!ExAllocatePoolWithTag+0x4ca
88b57cd4 81dee161 fffffe00 88826900 888268e0 nt!HvpWriteLog+0x2e6
88b57cf8 81defd43 81d0be10 81d41ec8 00000000 nt!HvSyncHive+0x97
88b57d14 81defbb9 81d0e101 88b57d36 88b57d3c nt!CmpDoFlushNextHive+0xdc
88b57d44 81cb1e22 00000000 00000000 840c1828 nt!CmpLazyFlushWorker+0x9a
88b57d7c 81de1c42 00000000 32df37ab 00000000 nt!ExpWorkerThread+0xfd
88b57dc0 81c4aefe 81cb1d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExAllocatePoolWithTag+4ca
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
STACK_COMMAND: .cxr 0xffffffff88b57874 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+4ca
BUCKET_ID: 0x7E_nt!ExAllocatePoolWithTag+4ca
Followup: MachineOwner
---------

If the memory couldn't be referenced run the memory diagnostic as well as looking at your hard drive for errors with chkdsk. Also, update your video and sound drivers.

im sorry its hard for me to understand except I did recently update my graphic card. How do I work with the other parts, make it simple for me please.

Open up the start menu, type mem and press enter. Reboot and wait. Then right click on your drive and in the tools tabs choose check now for errors and tick both boxes reboot. Also make sure your sound driver is up to date.

ok i ran the memory tool and it turns out there were no errors so i guess all there is left is to update the sound driver, can you help me with this?

Css14 said:

ok i ran the memory tool and it turns out there were no errors so i guess all there is left is to update the sound driver, can you help me with this?

Click to expand...

Chkdsk too. After that open up the start menu, type dxdiag, then navigate to the sound tab and post what device you have. Also search for device and in device manager look for the sound controller. Make sure its the same as dxdiag. Then post what audio device you have.

ok for dxdiag, it said conexant High Definition Smartaudio and for device Manager it had the same thing but had 221 so i would assume its the same thing, but it also had something called Nvidia high definition audio as well.

Can you right click on your speaker icon select playback devices and the one with the tick, update that one. It might also say working.

im afraid i don't know what you mean. Right click in the device manager, sound controller? or on the coxenant speaker icon


edit- ok i right clicked the coxenant speaker icon and clicked update driver and it said it sucessfully updated, is that all now or there still more to do. I don't want to attempt this untill you think im ready

If it said updated, skip the other instructions, and start chkdsk, as above. Then install the software. Make sure Vista is fully updated, along with SP2.

Css14 said:

Ok so i was in the middle of installing counter strike source, each time i would go to disc 2 during the installation, I would get this bsod while it was installing. I cant take any pictures because it goes by way too fast, I got the minidump file if someone wants to take a look at it and help me out.

Minidump.zip <--- mini dump

Click to expand...

As per Frostmourne's listing of your minidump's details, your machine crashed because of corrupted pool memory. Given it happened multiple times in the same spot, the likely explanation is a pool corrupting driver.

It's practically impossible to work out which driver is responsible from that minidump because the evidence is long gone. "Pool" memory can be thought of as a region shared by many OS and 3rd-party components. When it needs a chunk of memory, each driver asks the OS for a pool allocation (ExAllocatePoolWithTag), and then it's supposed to confine itself to only the allocated chunk without going past the upper or lower boundaries. For performance reasons, the OS doesn't normally bother to keep tabs on what drivers are doing with their pool allocs because that would slow things down somewhat, and kernel-mode drivers are meant to be trusted (known-good) code anyway.

The problem is when a driver accidentally - due to a bug - writes outside of its own pool allocations, either past the boundaries of existing allocated regions or with wild unintentional writes elsewhere. If such a write should happen to succeed, there is almost no way you can trace it back to the original corruptor... which is why you can enable "special pool" to make the OS pay greater scrutiny to what drivers are doing with pool.

Since you seem able to repro a crash, this should be relatively painless:

• On an elevated (run as admin) CMD prompt, run VERIFIER /ALL
• Reboot
• Try to repro the crash once more. Save and upload minidump if "successful".
• Disable verifier by running VERIFIER /RESET.

That new minidump may reveal the corruptor in the act.

ok the software installation went longer then usual so it was working but i got a different blue screen this time.

the STOP was 0x000000E6(0x0000000F, 0x00000000, 0x00000000, 0x00000000)


here is the minidump- Minidump.zip

Hmm, verifier caught a fault that time, but it's difficult to be sure whether it's the same issue, especially since you didn't seem to trigger the crash at the same point that time.

Rather than jumping to conclusions, can you repeat those actions 2 or 3 times, always with verifier enabled (it stays enabled until you "reset"), and see whether you experience a crash close to the original point during the game install?

it happens while i attempt to install the game, ive never played it before. I'll trigger the crash for u again 2 times and upload the minidump.

ok so the first crash i did again, it was a new blue screen again and the 2nd one it was the 0x000000E6(0x0000000F, 0x00000000, 0x00000000, 0x00000000) one again.

ok so i tried it one more time and here is the minidump for it

the minidump- Minidump.zip

Bugcheck:

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000f, Boundary overrun. Driver or DMA hardware has
written outside of its allocation.
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------

CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xE6
PROCESS_NAME: MSI26DF.tmp
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81f045a7 to 81ce7b0d
STACK_TEXT:
805f0e1c 81f045a7 000000e6 0000000f 00000000 nt!KeBugCheckEx+0x1e
805f0e3c 81f02e7e 00000000 00000000 87406000 nt!VerifierBugCheckIfAppropriate+0x32
805f0e58 81f02b77 8a41b5e4 87405ff8 00001008 nt!VfAssert+0xa9
805f0e6c 81f028d0 00000001 00000003 b0e55000 nt!ViCheckTag+0x9a
805f0e90 81f02624 c8b3b000 b5196d6c 8411b3e4 nt!ViFreeMapRegistersToFile+0x87
805f0eac 81f01974 00000000 c8b3b000 00010000 nt!ViFlushDoubleBuffer+0xfe
805f0ed8 823270d8 87b6e260 00000010 805f0e00 nt!VfPutScatterGatherList+0xe5
805f0ef4 842b299c 841c0f20 b5196d10 841f0201 PCIIDEX!BmFlush+0x2a
805f0f0c 842b2e31 841ef0e0 b5196d10 841f0201 ataport!IdeFlushScatterGatherList+0x24
805f0f34 842b312d 841ef0e0 b5196d10 805d1120 ataport!IdeProcessCompletedRequests+0x5f
805f0f88 81cc46a2 841ef09c 841ef028 00000000 ataport!IdePortCompletionDpc+0xab
805f0ff4 81cc22d5 bddeeb68 00000000 00000000 nt!KiRetireDpcList+0x147
805f0ff8 bddeeb68 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
805f0ffc 00000000 00000000 00000000 00000000 0xbddeeb68

STACK_COMMAND: kb
FOLLOWUP_IP:
PCIIDEX!BmFlush+2a
823270d8 832600 and dword ptr [esi],0
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: PCIIDEX!BmFlush+2a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PCIIDEX
IMAGE_NAME: PCIIDEX.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 49e01eed
FAILURE_BUCKET_ID: 0xE6_VRF_PCIIDEX!BmFlush+2a
BUCKET_ID: 0xE6_VRF_PCIIDEX!BmFlush+2a
Followup: MachineOwner

This points to motherboard, RAM issues. Check out the links here:

ASUSTeK Computer Inc.-Forum- Vista SP1 BSOD - PCIIDEX.SYS

Vista x64 SP1 Bluescreen on PCIIDEX.sys

i don't understand, so there is something wrong with my motherboard then? what about the other minidump, i think i only had that once

These crashes point to a variety of problems but that seems concrete. Try following the recommendations. The others mention svchost.exe, task manager etc.

ok ill try, it all seems complicated to do. so how do i disable the memory hole in bios?

i think the vista service pack 2 may have messed me up as well so how do i uninstall that?