Random BSOD in Windows 7 64 bit

usasma · 23 Jan 2010

Let's wait for the next BSOD to see what happens.
You've made a lot of changes to the system.

kc7404 · 28 Jan 2010

Here are the latest results ......

I hope you might find some information that will help resolve this.

Thank you for your patience.

zigzag3143 · 28 Jan 2010

kc7404 said:

Well, I am feeling a little defeated right now as I just suffered yet another unexpected crash and I had done the following:

000.fcl ----- PowerDVD ----- Uninstalled completely
npusbio_x64.sys ----- NaturalPoint Optitrack ----- This is the most current driver
OA002Afx.sys ----- Creative Camera driver ----- Uninstalled completely
OA002Ufd.sys ----- Creative Camera driver ----- Uninstalled completely
OA002Vid.sys ----- Creative Camera driver ----- Uninstalled completely
PxHlpa64.sys Roxio CD/DVD burning program ----- Uninstalled completely
RtNdPt60.sys ----- Netgear GA511 Driver file ----- Could not find any drivers

Attached is the latest file crash details.

I hope you might have some more clues for me.

Thank you for all of your help and not giving up.

Sincerely,

KC

KC

hi and welcome

we will get to the bottom of this

this last was caused by memory.

I would
download memtestx86 and run for at least 4passes.
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

llet us know the resultls

Ken J+

Code:

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


Loading Dump File [C:\Users\K\Desktop\012210-20607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Fri Jan 22 20:15:10.915 2010 (GMT-5)
System Uptime: 0 days 5:09:20.882
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80069966d0, fffffa80069966c0, fffffa80069966d0}

Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80069966d0, the pool entry being checked.
Arg3: fffffa80069966c0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80069966d0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  VistaFirewallS

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003006d6f to fffff80002ed4f00

STACK_TEXT:  
fffff880`074193d8 fffff800`03006d6f : 00000000`00000019 00000000`00000003 fffffa80`069966d0 fffffa80`069966c0 : nt!KeBugCheckEx
fffff880`074193e0 fffff800`031e21d0 : 00000000`00000004 00000000`00008814 fffff880`63416553 fffff8a0`00000000 : nt!ExFreePool+0x536
fffff880`074194d0 fffff800`0319a1e6 : fffff880`07419840 00000000`00000000 fffffa80`069a0e90 fffff800`031c30c5 : nt!RtlpNewSecurityObject+0xcc0
fffff880`07419760 fffff800`031c2ba1 : 00000000`00000000 fffffa80`07799aa0 00000000`00000000 00000000`00000000 : nt!ObpAssignSecurity+0x82
fffff880`074197d0 fffff800`031bfb52 : fffff880`07419ae8 fffffa80`0d5e0690 fffff8a0`0357ac50 00000000`0102d9d8 : nt!ObInsertObjectEx+0x1e1
fffff880`07419a20 fffff800`031a1fa7 : fffff8a0`10d19310 fffffa80`0d5cf900 fffff8a0`10d192f0 fffffa80`0d5cf910 : nt!SeCopyClientToken+0x8a
fffff880`07419ab0 fffff800`031bf76f : 00000000`00000000 fffff880`07419b28 ffffffff`ffffffff fffffa80`0d5cf910 : nt!SepCreateClientSecurity+0xb7
fffff880`07419ae0 fffff800`03170821 : 00000000`0102db30 fffff960`00000001 fffff880`07419bc8 fffff880`07419c38 : nt!AlpcpCreateSecurityContext+0xe7
fffff880`07419b80 fffff800`02ed4153 : fffffa80`0d6c4060 00000000`00000001 00000000`00000020 00000000`00000001 : nt!NtAlpcCreateSecurityContext+0x130
fffff880`07419c20 00000000`77cb064a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0102d998 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cb064a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePool+536
fffff800`03006d6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePool+536

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

BUCKET_ID:  X64_0x19_3_nt!ExFreePool+536

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

kc7404 · 29 Jan 2010

Hi ZigZag,

Thank you for posting.

When you mentioned that the crash was caused by memory, was it the one yesterday or the crash before it from about 6 days ago?

I know a few things about computers, but only enough to make myself a nuisance, not productive.

I searched for the memtestx86 program but learned it works mainly for a pc with 4GB of RAM and I have 8 GB.

I then opted for the "memtest86+-4.00.iso" file but I do not know how to make it work?

Additionally, when you mention "run a system file check
type cmd in search>right click and run as admin>sfc /scannow", would I simply be:
1) Type cmd (to bring up a DOS Window)
2) How do I get it as an Administrator?
3) Then type sfc/scannow

Do I then take a screen shot of the results or can they be copied and saved in Notepad.

Thank you for any detailed explanation ... I am not IT savvy but I will follow instructions.

Sincerely,

KC

kc7404 · 30 Jan 2010

Hello ZigZag,

I did figure out the scannow command and there were the results:

"Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc/scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>"

I still do not know how to implement and run the memetest86+.

Can someone assist?

Thank you.

Sincerely,

KC

ickymay · 30 Jan 2010

kc7404 said:

Hello ZigZag,

I did figure out the scannow command and there were the results:

"Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>sfc/scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\Windows\system32>"

I still do not know how to implement and run the memetest86+.

Can someone assist?

Thank you.

Sincerely,

KC

download this version of memtest86+ then burn to CD and run that CD from boot for at least 3 passes :)

kc7404 · 31 Jan 2010

Hi Ickymay,

Thank you for the help.

I did copy and burn the file on a cd.

When I reboot my system (Dell) there are 2 keys that I can hit when it is in the process of loading:
F2 --- Setup
F12 --- Boot Menu

I tried to look (as much as I could) into both areas, but could not seem to find where to have my pc automatically run the "memtest86+-2.11.iso" file.

When I brought up the CMD Windows as an Administrator and changed directories to the CD/DVD Drive and tried to execute the file in DOS I got an error message stating that Windows could not open file.

It was suggested to either find some program on my machine or web to see if it could be run but I had little luck.

What am I doing wrong?

Thank you for your help.

Sincerely,

KC

usasma · 31 Jan 2010

You must use an ISO burner to burn the .iso file to the disk. When it does this, it lays out the files in the specific order that's required to make the CD/DVD bootable. Just copying the .iso to the disk won't work.

I'd suggest this free burning tool: ISO Recorder v3
Once it's installed, reboot, then right click on the .iso file and select the option to Copy Image to CD" (should be the top option). Here's a description: How to use ISO Recorder

Also, please run Driver Verifier according to the following directions. This is because of this line in the dump file above: [QUOTE]BAD_POOL_HEADER (19)The pool is already corrupt at the time of the current request.This may or may not be due to the caller.The internal pool links must be walked to figure out a possible cause ofthe problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[QUOTE]

Here's the instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- 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"
- 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 use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run 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 going back 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 your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

kc7404 · 02 Feb 2010

Last night I ran "Memtest86+ Version 2.11" for 3 complete passes (it took over 4 hours to execute) and my computer passed with no errors.

I subsequently set up the Driver Verifier and after rebooting my machine and letting it sit overnight, there were no crashes to report.

Slightly confused, this morning I set it up again (following the same step-by-step process as I had last night) and a crash did occur.

Attached please find the results and I'll await further news.

I cannot express in words the gratitude I have for all of you who have been patiently helping me reach a resolution to this issue.

Sincerely,

KC

kc7404 · 02 Feb 2010

2 Additional files should they prove useful.