HiddenC - BSOD (Again)

IoNGeNeRaL · Nov 5, 2010

Hey.

Unfortunately I am getting another 2 BSODs...

zigzag3143 · Nov 5, 2010

HiddenC said:
Hey.

Unfortunately I am getting another 2 BSODs...

Memory Corruption. Run memetest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Also run a system file check

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

Let us know if you need help

Ken

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\Windows_NT6_BSOD_jcgriff2\110510-24039-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Fri Nov  5 07:41:04.237 2010 (GMT-4)
System Uptime: 0 days 0:20:07.219
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa8003963480, fffffa8003963480, fffffa8003963400}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )

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

3: 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: fffffa8003963480, the pool entry being checked.
Arg3: fffffa8003963480, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8003963400, 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:  svchost.exe

CURRENT_IRQL:  0

LOCK_ADDRESS:  fffff800030bf400 -- (!locks fffff800030bf400)

Resource @ nt!PiEngineLock (0xfffff800030bf400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff800030bf400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002feed6f to fffff80002ebb740

STACK_TEXT:  
fffff880`09e13ee8 fffff800`02feed6f : 00000000`00000019 00000000`00000003 fffffa80`03963480 fffffa80`03963480 : nt!KeBugCheckEx
fffff880`09e13ef0 fffff800`031b4754 : 00000000`00000002 fffffa80`03a1e080 00000000`00000001 fffffa80`00000000 : nt!ExDeferredFreePool+0xa56
fffff880`09e13fe0 fffff800`031b75bb : 00000000`00000000 fffffa80`03a03900 00000000`00002d11 fffff880`09e14078 : nt!ObpAllocateObject+0xc4
fffff880`09e14040 fffff800`03198f84 : 00000000`00000000 fffff880`09e14251 fffff8a0`0112a130 00000000`00000000 : nt!ObCreateObject+0xdb
fffff880`09e140b0 fffff800`03195195 : fffff8a0`00000000 fffff880`80032390 fffff8a0`00023380 fffffa80`0655b360 : nt!CmpDoOpen+0x154
fffff880`09e14170 fffff800`031b4e84 : fffff800`03194cc0 00000000`00000000 fffffa80`0655b360 00000000`00000200 : nt!CmpParseKey+0x4d5
fffff880`09e14440 fffff800`031b9e4d : fffffa80`0655b360 fffff880`09e145a0 00000000`00000240 fffffa80`03a1e080 : nt!ObpLookupObjectName+0x585
fffff880`09e14540 fffff800`03198dcc : ffffffff`80000af0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x1cd
fffff880`09e145f0 fffff800`0319bfca : fffff880`09e149f0 00000000`00020019 fffff880`09e14940 fffff880`00000000 : nt!CmOpenKey+0x28a
fffff880`09e14740 fffff800`02eba993 : fffffa80`00000000 fffff8a0`00a70720 fffff880`00000200 fffff880`09e149c4 : nt!NtOpenKey+0x12
fffff880`09e14780 fffff800`02eb6f30 : fffff800`0312c498 00000000`00000000 00000000`00000200 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09e14918 fffff800`0312c498 : 00000000`00000000 00000000`00000200 00000000`00000000 fffff8a0`00a70720 : nt!KiServiceLinkage
fffff880`09e14920 fffff800`03128be2 : 00000000`00000000 fffff880`09e14b20 fffff8a0`082b5c00 00000000`00000000 : nt!IopOpenRegistryKeyEx+0x38
fffff880`09e14980 fffff800`03129cd1 : 00000000`00000002 00000000`00000000 fffff880`00000000 00000000`00000001 : nt!IopGetDeviceInterfaces+0x37e
fffff880`09e14af0 fffff800`03127af1 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff8a0`082b5c10 : nt!PiGetInterfaceDeviceList+0x41
fffff880`09e14b50 fffff800`0315d1b0 : fffff8a0`082b5c10 fffff800`00008000 fffff880`09e14c01 fffff800`03386da0 : nt!PiControlGetInterfaceDeviceList+0x111
fffff880`09e14bd0 fffff800`02eba993 : fffffa80`03d55b60 00000000`0073e940 fffff880`09e14ca0 00000000`0073e9c8 : nt!NtPlugPlayControl+0x100
fffff880`09e14c20 00000000`77a90daa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0073e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a90daa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a56
fffff800`02feed6f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a56

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56

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

IoNGeNeRaL · Nov 5, 2010

Sigh. Why do I continue to get issues? :/

Another issue I have, is that my Windows Theme and network device gets disabled in Services for some odd reason...

IoNGeNeRaL · Nov 5, 2010

Memtest reports no issues at all.

CarlTR6 · Nov 5, 2010

How many passes did you run? You should run at least seven passes. That will take six to eight hours.

You still have two obsolete drivers loaded on your system.

000.fcl Fri Sep 26 09:11:22 2008 - CyberLink FCL Driver,CyberLink

AsUpIO.sys Sun Jul 05 22:21:38 2009 - Asus utility driver. ASUSTeK Computer Inc.-Support-

Update these drivers or uninstall Cyberlink.

IoNGeNeRaL · Nov 5, 2010

Yeah, I did that before I posted this thread.

richc46 · Nov 5, 2010

Did you take a good stick of ram and test each slot?

zigzag3143 · Nov 5, 2010

HiddenC said:
Memtest reports no issues at all.

Something is corrupting the memory. either it is the memory istself, or a driver causing it to corrupt.With memtest you may even have to test it one stick at a time, and one mobo slot at a time with known good ram

since it appears the memory may not be the cause lets try driver verifier

Beyond that, please run Verifier with these settings:

Code:
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation 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 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:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

CarlTR6 · Nov 5, 2010

Update the two drivers I listed in my post above.

IoNGeNeRaL · Nov 5, 2010

zigzag3143 said:
HiddenC said:

Memtest reports no issues at all.

Click to expand...

Something is corrupting the memory. either it is the memory istself, or a driver causing it to corrupt.With memtest you may even have to test it one stick at a time, and one mobo slot at a time with known good ram

since it appears the memory may not be the cause lets try driver verifier

Beyond that, please run Verifier with these settings:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation 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 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:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

Click to expand...

CarlTR6 said:

Update the two drivers I listed in my post above.

Click to expand...

I do not wish to make my system even more unstable by doing this verifier thing.

@ Carl: ASUS Update Utility is the latest version, and I have that version. So is CyberLink. CL sucks anyway. I only wanted it for their DVD Player software but the video quality is aweful. Thanks Carl and zig.

Rep + to both of you.

CarlTR6 · Nov 5, 2010

Just uninstall Cyberlink. It has created problems for others. And you are very welcome. Keep us updated; we want you to kick this problem.

Thank you for the rep!

HiddenC - BSOD (Again)

IoNGeNeRaL

New member

My Computer

zigzag3143

New member

My Computer

IoNGeNeRaL

New member

My Computer

IoNGeNeRaL

New member

My Computer

CarlTR6

Antique Senior Member

My Computer

IoNGeNeRaL

New member

My Computer

richc46

Moderator

My Computer

zigzag3143

New member

My Computer

CarlTR6

Antique Senior Member

My Computer

IoNGeNeRaL

New member

My Computer

CarlTR6

Antique Senior Member

My Computer