Help! BSOD

[Loner19881]

Okay kinda new to computers but here it goes... I have Windows Vista Premium OS 32-bit. My motherboard is a BIOSTAR supports 32 or 64bit. Model mcp69 m2+ n68s+. I have a amd athlon dual core processor. Got ddr2 ram 240 pin 800 ram brand name Corsair... The OS I got came with my e-machine that I had and when installed on this comp that I built it keeps blue screening normaly when I play SC.. Here are the blue screen mini dump files that I decoded with WinDBG...

Probably caused by : ntkrpamp.exe ( nt!PpCheckInDriverDatabase+42 )

Followup: MachineOwner

PAGE_FAULT_IN_NONPAGED_AREA(50)
 
 
Invalid system memory was refrenced.   This cannot be protected by 
try-except, it must be protected by a Probe.   Typically the address is just 
plain bad or it is pointing at freed memory.
 
 
Arguments:
 
 
Arg1: ffffff8e, memory referenced.
 
 
Arg2: 00000000, value 0 = red operation, 1 = write operation.
 
 
Arg3: 81f82029, If non-zero, the instruction address which referenced the bad 
memory address.
 
 
Arg4: 00000000, (reserved)
 
 
 
 
 
Debugging Details:
 
 
------------------
 
 
 
 
 
READ_ADDRESS: ffffff8e
 
 
 
 
 
FAULTING_IP:
 
 
nt!PpCheckInDriverDatabase+42
 
 
81f82029 8b5510          mov       edx,dword ptr [ebp+10h]
 
 
 
 
 
MM_INTERNAL_CODE:   0
 
 
 
 
 
DEFAULT-BUCKET_ID:   VISTA_DRIVER_FAULT
 
 
 
 
 
BUGCHECK_STR:   0x50
 
 
 
 
 
PROCESS-NAME:   System
 
 
 
 
 
CURRENT_IRQL:   0
 
 
 
 
 
TRAP_FRAME:   84f713f0 -- (.trap 0xffffffff84f713f00
 
 
ErrCode = 00000000
 
 
eax=00000001 ebx=00000000 ecx=81f49400 edx=00000000 esi=81f4980 
edi=00000000
 
 
eip=81f82029 esp=84f71464 ebp=84f71488 iopl=0       nv up ei pl zr na pe nc 
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000          efl=00210246
 
 
nt!PpCheckInDriverDatabase+0x42:
 
 
81f82029 8b5510         mov      edx,dword ptr [ebp=10h] 
ss:0010:84f71498={HDAudBus!
 
 
Resetting default scope
 
 
 
 
 
LOCK_ADDRESS:   81f49600 -- (!locks 81f49600)
 
 
 
 
 
Resource @ nt!PiEngineLock (0x81f49600)   Exclusively owned
 
 
          Threads: 839ef020-01<*>
 
 
1 total locks, 1 locks currently held
 
 
 
 
 
PNP_TRIAGE:
 
 
    Lock address   :0x81f49600
 
 
    Thread Count   :1
 
 
    Thread address:0x839ef020
 
 
    Thread wait    :0x2ba
 
 
 
 
 
LAST_CONTROL_TRANSFER:   from 81e62dd4 to 81ead379

Here is the information you asked for please help!

 

[richc46]

Welcome
You will get the best help, if you post the required information
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

 

[Loner19881]

Richc46 I did as your link said I have the zip file posted now

 

[richc46]

Your reports and received and in good order. I want to give your problem all the time that it deserves. If no one else analyzes the data, I will do so later this evening.

 

[Loner19881]

Ok. Thank you Very Much sir I will be randomly checking post.... I have been pulling my hair out for 3 weeks trying to figure these 4 random bsods I keep getting lol... It's quite annoying.. Thank you for your time and interest..

 

[richc46]

Welcome
You have given me several minidump reports. It is important to realize that most times the reports dont agree, but merely give small clues about the true cause.
Your reports are as follows
1A, 50, A, 8E, 4E,
1A
Usual causes: Device driver, memory, kernel
50
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
A
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
8E
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
4E
Usual causes: Device driver, ?memory

Several of these reports point toward memory. I think that is a good place to start.

Take a memtest86. Run 8 passes, and then test each slot with a known good stick for 8 passes.
Guide to using Memtest86+ - Geeks to Go Forums

Advice that is given to all members with BSOD problems is to
Make an SFC scan
http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html
Download and run a full anti virus scan
Download and run a full scan with malwarebytes.

 

[Loner19881]

Ok. I have ran memtest86 3 times on my computer to test if memory is bad.. I just bought the motherboard processor and ram from TigerDirect.com 3 weeks ago. The tests all came back saying memory was good and have ran maleware and virus scans on the harddrive. I also wiped my harddrive and re-installed the windows 3 times.. How can I run some driver tests to see if the windows vista is installing drivers that are conflicting with my motherboard drivers because the windows edition I got came with the Emachines computer that I got and the recovery cd has drivers on it for the old motherboard I just dont know how to break it down to test drivers to see if one of them are causing me to bsod.

 

[Loner19881]

And also it bsoding like that will it destroy any of my hardware?

 

[richc46]

I hope that you understand that I must ask this, because many times when tests are not completed properly and the BSOD cause is never found.
Did you run the memtes86 (not the memory test that comes with Vista) for 8 passes and then you tested each slot with a known good stick?
As I said in my opening post, this is an art as well as a science and in my opinion it points to memory. I want to be sure before we move on

 

[Loner19881]

Yes, I downloaded the memtest86 on my computer then put the iso file to a cd and ran the test on it 8 passes came back ram stick was good

 

[richc46]

You took a ram stick and tested each slot for at least 4 passes?

 

[Loner19881]

yes 8 passes on each actually.. I used the old ram from my old motherboard that i knew was good it is 512 sticks of ram.. I did that like 2 weeks ago when I was googling and trying to figure it out everyone was saying ram problem and told me to memtest it so I did and it came back good.

 

[richc46]

Great, I have an idea what the cause is, but rather than send you on a wild goose chase, complete the other steps that I have given. They are very easy. If you get another BSOD post and it agrees with the ones given, I think that this can be solved.

I have solved many BSODs and read about many others, to learn. The worst that I have seen from BSODs, was major problems to the OS; to the extent that it had to be reinstalled. I have not seen problems for the Hardware; not saying that it cannot happen.

 

[Loner19881]

Ok I just did a virus scan, maleware bite scan and most important the system file scan with the sfc commands and all came back good.

 

[richc46]

I know that your primary concern is to fix this as soon as possible. That being said, this is a driver test (But its a pain). Read the warnings and then try it.

Driver Verifier Inst

Since the driver that crashed you has not been listed you shouldrun driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'lltell you what the driver is. But sometimes it'll crash and won't tell you thedriver. Other times it'll crash before you can log in to Windows. If you can'tget to Safe Mode, then you'll have to resort to offline editing of the registryto disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've gotaccess to another computer so you can contact us if problems arise. Then make aSystem Restore point (so you can restore the system using the Vista/Windows 7Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and pressEnter
- Select "Create custom settings (for code developers)" and click"Next"
- Select "Select individual settings from a full list" and click"Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click"Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limitedexperimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because DriverVerifier is stressing the drivers out. If it doesn't crash for you, then let itrun for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by goingback in and selecting "Delete existing settings" on the first page,then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from yourinstallation DVD to set the system back to the previous restore point that youcreated.

Enable the driver verifier

www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

 

[Loner19881]

It still hasn't created BSOD yet I have been playing Starcraft trying to get it to.... I'll post when it does.

 

[richc46]

Suggestion is 36-48 hours of use.

 

[richc46]

I read over your thread, again. I did come up with an idea. You have 2GB of RAM and you have a problem playing a resource hungry game. My first thought, is that your memory is not sufficient for this game. How much ram are you using during game play (right click on bottom task bar, and bring up task manger and then look at how much ram is left)? Then I had another thought, this what the compatiblity center says about your game.
Windows Vista Compatibility Center Search Results - Starcraft

In addition the Driver Verifier was on when you had the BSODs that you sent me. Turn if off, update game if necessary. If there are more BSODs caused by memory and you say you tested, my contention is that possibly you do not have sufficient memory for the game.

Report you sent showing driver verifier is on. I have bolded the verifier. This can and does cause BSODs

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_BSOD.zip\Windows_NT6_BSOD_jcgriff2\Mini070311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e45000 PsLoadedModuleList = 0x81f5cc70
Debug session time: Sun Jul  3 20:19:21.405 2011 (GMT-4)
System Uptime: 0 days 1:01:07.996
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {4, 2, 0, 81edabf7}
Probably caused by : volsnap.sys ( volsnap!VspLaunchCowRead+38 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81edabf7, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from 81f7c868
Unable to read MiSystemVaType memory at 81f5c420
 00000004 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+23
81edabf7 8b4704          mov     eax,dword ptr [edi+4]
CUSTOMER_CRASH_COUNT:  1
[B]DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP[/B]
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
TRAP_FRAME:  a7d02938 -- (.trap 0xffffffffa7d02938)
ErrCode = 00000000
eax=00000006 ebx=00000002 ecx=00000004 edx=00002462 esi=82c3fab8 edi=00000000
eip=81edabf7 esp=a7d029ac ebp=a7d029bc iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiUnlinkFreeOrZeroedPage+0x23:
81edabf7 8b4704          mov     eax,dword ptr [edi+4] ds:0023:00000004=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 81edabf7 to 81e92fd9
STACK_TEXT:  
a7d02938 81edabf7 badb0d00 00002462 a7d0296c nt!KiTrap0E+0x2e1
a7d029bc 81edaeaf 00002462 81e160c0 81f3d920 nt!MiUnlinkFreeOrZeroedPage+0x23
a7d029fc 81f34439 00000002 81f476e0 00000000 nt!MiRemoveAnyPage+0x16c
a7d02a58 81efa0a0 00000000 00004000 00004000 nt!MiAllocatePoolPages+0x434
a7d02ab0 81f32c57 00000000 00000000 00004000 nt!ExpAllocateBigPool+0x97
a7d02b10 81e78a19 00000000 00004000 62536f56 nt!ExAllocatePoolWithTag+0x116
a7d02b34 83f2af78 00000000 00004000 62536f56 nt!ExAllocatePoolWithTagPriority+0x173
a7d02b64 83f38cc1 8769bdf0 878e2778 88884af4 volsnap!VspLaunchCowRead+0x38
a7d02c2c 83f1243c 88884af0 88884af4 a98cae28 volsnap!VspWriteVolume+0x72b
a7d02cb4 83f14900 00962cb8 88884af4 00000000 volsnap!VspAcquireNonPagedResource+0xc6
a7d02ce8 821286be 008e26c0 878e2784 a7d02d38 volsnap!VolSnapWrite+0x646
a7d02d0c 81e8992d a98cafb8 8de7d240 878e26c0 nt!IovCallDriver+0x23f
a7d02d20 83e12603 8de7d1c8 a7d02d44 81ef2218 nt!IofCallDriver+0x1b
a7d02d2c 81ef2218 8de7d240 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14
a7d02d2c 81ef2311 8de7d240 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x118
8de7d1d8 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31

STACK_COMMAND:  kb
FOLLOWUP_IP: 
volsnap!VspLaunchCowRead+38
83f2af78 56              push    esi
SYMBOL_STACK_INDEX:  7
SYMBOL_NAME:  volsnap!VspLaunchCowRead+38
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: volsnap
IMAGE_NAME:  volsnap.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  49e01f09
FAILURE_BUCKET_ID:  0xA_VRF_volsnap!VspLaunchCowRead+38
BUCKET_ID:  0xA_VRF_volsnap!VspLaunchCowRead+38
Followup: MachineOwner
---------

 

[Loner19881]

These are the system requirements:
Windows Vista, XP or 2000
* 90 MHz Pentium or equivalent
* 16 MB of RAM
* SVGA video card that supports DirectDraw at 640 x 480 resolution, 256 colors
* 80 MB HD space
* 4X CD-ROM drive
Mac OS X 10.3.9 or higher.
* PowerMac or Compatible
* 16 MB of RAM plus Virtual Memory (32 MB RAM recommended)
* Video card that supports 640x480 display in 256 colors
* 80 MB HD space
* 4X CD-ROM drive
And I'm only usin 700 MB while game is running.

 

[richc46]

Fine turn off verifier, it was on when you got the first BSODs
Then check the link I gave you about the game.