Constant BSOD

[Shappo]

Hello everyone

I've been putting up with this issue for some time now, and starting to get tired of this operating system. I've been getting a 0x0000000A BSOD over the last month on my system which is about 12 months old.

I run windows 7 professional x64.

I've tried running memtest86+ several times, and have had no luck in finding any errors.
I've done complete clean installs and ran updates for all my hardware through windows update.

The only problems that I can identify are what I see in the event viewer in the 'manage' section of the computer. I've been getting a critical error consisting of 'Kernell Power - ID 41', which I have no knowledge of what that jazz is about, lol.

I made a .zip using the SF Diag tool in an attachment.

Hope someone can point me in some kind of direction
Thanks heaps.

 

[zigzag3143]

Hello everyone

I've been putting up with this issue for some time now, and starting to get tired of this operating system. I've been getting a 0x0000000A BSOD over the last month on my system which is about 12 months old.

I run windows 7 professional x64.

I've tried running memtest86+ several times, and have had no luck in finding any errors.
I've done complete clean installs and ran updates for all my hardware through windows update.

The only problems that I can identify are what I see in the event viewer in the 'manage' section of the computer. I've been getting a critical error consisting of 'Kernell Power - ID 41', which I have no knowledge of what that jazz is about, lol.

I made a .zip using the SF Diag tool in an attachment.

Hope someone can point me in some kind of direction
Thanks heaps.

Ok the 4 here are caused by memory management. Now it is quite possible that a driver is causing that. In fact probable. When you run memtest you run it outside of windows so no drivers are loaded. Inside windows all the drivers load and one doesn't play nice. SEE SNIP AT BOTTOM

Most of yours are up to date so I suggest at this point you run driver verifier to find out which driver is causing the grief.

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:

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


Let us know if you need assistance


ken J

 

[Shappo]

Hey ken, thanks for the reply.
I will try the driver verifier when I get home, i'll keep you posted how it goes.
Cheers

 

[Shappo]

Okay.

I followed your procedure precisely.

*After setting up the verifier, and then restarting the computer for it to take effect. I immediately received a 0x00000024 BSOD which occurred before loading to the desktop.

*I then rebooted, 'deleted existing settings' and made another .zip from the SF diag tool consisting of my minidump, driver list etc...

Anything I didn't do?

Thanks.

 

[Shappo]

Any idea?

 

[xStat1cSm1thx]

Just out of curiosity, what kind of HDD(s) are you using? I'm assuming SATA. If this is the case, can you tell me which channels it/they are on and whether or not they are set to master/slave?

 

[CarlTR6]

Your latest dump is not a Driver Verifier enabled dump.

Error code 24, NTFS File system. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

I suggest you run Check Disk.

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Tue Nov 16 03:53:44.627 2010 (GMT-5)
System Uptime: 0 days 0:00:09.704
Loading Kernel Symbols
...............................................................
......................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880031b49a8, fffff880031b4210, fffff80002af02b3}

Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+23f )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880031b49a8
Arg3: fffff880031b4210
Arg4: fffff80002af02b3

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


EXCEPTION_RECORD:  fffff880031b49a8 -- (.exr 0xfffff880031b49a8)
ExceptionAddress: fffff80002af02b3 (nt!IopCompleteRequest+0x0000000000000ae3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880031b4210 -- (.cxr 0xfffff880031b4210)
rax=fffff880031b5f80 rbx=fffff98002984ee0 rcx=0000c68f00520050
rdx=0000c68f00520050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002af02b3 rsp=fffff880031b4be0 rbp=0000000000000000
 r8=fffff880031b4ce8  r9=fffff880031b4ce0 r10=0000000000000002
r11=fffff80002aef7d0 r12=fffff880031b5f78 r13=0000000000000000
r14=fffffa800462db60 r15=fffff880009e8180
iopl=0         nv up ei pl nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
nt!IopCompleteRequest+0xae3:
fffff800`02af02b3 488b09          mov     rcx,qword ptr [rcx] ds:002b:0000c68f`00520050=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d080e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsNonCachedIo+23f
fffff880`0125e05f 498b4d78        mov     rcx,qword ptr [r13+78h]

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02af02b3 488b09          mov     rcx,qword ptr [rcx]

BUGCHECK_STR:  0x24

IRP_ADDRESS:  ffffffffffffff89

LOCK_ADDRESS:  fffff80002cd4400 -- (!locks fffff80002cd4400)

Resource @ nt!PiEngineLock (0xfffff80002cd4400)    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  : 0xfffff80002cd4400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002aad0c7 to fffff80002af02b3

STACK_TEXT:  
fffff880`031b4be0 fffff800`02aad0c7 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`031b4cb0 fffff800`02ad7b9d : fffffa80`0462db60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`031b4d30 fffff800`02ad9cff : fffff880`031b5200 fffffa80`05ace040 00000000`00000000 fffff880`031b4f60 : nt!KiCommitThreadWait+0x3dd
fffff880`031b4dc0 fffff880`0125e05f : fffffa80`0578ad00 00000000`00000000 fffff8a0`0447f100 0053002b`002b0000 : nt!KeWaitForSingleObject+0x19f
fffff880`031b4e60 fffff880`01261526 : fffff880`031b5200 fffff980`029f2c10 fffff8a0`0447f140 fffff8a0`0447f010 : Ntfs!NtfsNonCachedIo+0x23f
fffff880`031b5030 fffff880`01263f78 : fffff880`031b5200 fffff980`029f2c10 fffff880`031b5301 fffffa80`058cc001 : Ntfs!NtfsCommonRead+0x7a6
fffff880`031b51d0 fffff800`02f76c16 : fffff980`029f2c10 fffff980`029f2c10 fffffa80`058cc030 fffffa80`059ed960 : Ntfs!NtfsFsdRead+0x1b8
fffff880`031b53d0 fffff880`0105e23f : fffff980`029f2fb0 fffff880`031b5480 fffffa80`05cda220 fffffa80`059ed960 : nt!IovCallDriver+0x566
fffff880`031b5430 fffff880`0105c6df : fffffa80`05787cf0 fffffa80`05787cf0 fffffa80`05787c00 fffff980`029f2c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`031b54c0 fffff800`02f76c16 : fffff980`029f2c10 00000000`00000002 fffffa80`05bf6f20 fffffa80`03baa418 : fltmgr!FltpDispatch+0xcf
fffff880`031b5520 fffff800`02ac21f2 : fffff980`029f2c30 00000000`00000043 fffff980`029f2c10 fffffa80`05b92c10 : nt!IovCallDriver+0x566
fffff880`031b5580 fffff800`02d93fb0 : fffffa80`05bf6f00 fffffa80`05bf6f00 00000000`00000001 00000000`0011cd78 : nt!IoPageRead+0x252
fffff880`031b5610 fffff800`02dcbc75 : fffffa80`05bf6f20 00000000`00000000 00000000`00000022 fffff880`031b58c0 : nt!MiCreateImageFileMap+0x170
fffff880`031b5840 fffff800`02dc1013 : fffff880`031b5aa0 00000000`00000000 fffff880`031b5d58 fffff880`031b5a98 : nt!MmCreateSection+0x7a9
fffff880`031b5a50 fffff800`02acf993 : fffffa80`0462db60 fffff880`031b5cf8 fffff880`031b5ae8 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`031b5ad0 fffff800`02acbf30 : fffff800`02ea98b6 fffffa80`0462db60 fffff880`031b5d80 00000000`00000004 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031b5cd8 fffff800`02ea98b6 : fffffa80`0462db60 fffff880`031b5d80 00000000`00000004 00000000`00000038 : nt!KiServiceLinkage
fffff880`031b5ce0 fffff800`02ea9c7c : ffffffff`80000110 00000000`00100000 fffff880`031b5e00 fffff800`02ace93d : nt!MmCheckSystemImage+0x96
fffff880`031b5e10 fffff800`02ea9e97 : ffffffff`80000110 00001f80`00000001 fffff8a0`0447e1d0 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
fffff880`031b5ec0 fffff800`02eb573a : 00000000`00000000 fffff880`031b6080 fffffa80`0462db60 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`031b5f20 fffff800`02ea934f : fffff880`031b6080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23a
fffff880`031b6040 fffff800`02eb5ca8 : fffff880`0fe46000 fffff880`031b6218 00000000`00000000 fffff880`031b61f8 : nt!MiResolveImageReferences+0x2ff
fffff880`031b6160 fffff800`02eb835d : fffff880`031b62d8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x7a8
fffff880`031b6280 fffff800`02f4bc30 : 00000000`00000001 00000000`00000000 fffff880`031b6828 ffffffff`80000130 : nt!IopLoadDriver+0x44d
fffff880`031b6550 fffff800`02d8a794 : fffff880`031b6860 00000000`00000000 00000000`c0000023 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031b6650 fffff800`02d8aaa2 : 00000000`00000000 00000000`00000000 fffff880`031b6860 fffff880`031b6828 : nt!RtlpCallQueryRegistryRoutine+0xf4
fffff880`031b66d0 fffff800`02ebbbcc : fffffa80`055d7010 00000000`00000000 00000000`c0000034 fffff880`031b6828 : nt!RtlQueryRegistryValues+0x17e
fffff880`031b67a0 fffff800`02ebd362 : fffffa80`055d6890 fffffa80`055d7010 00000000`00000001 fffff980`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`031b6950 fffff800`02ebd7fc : fffff800`02cd1d80 00000000`00000000 00000000`00000001 fffff800`02d3d840 : nt!PipProcessDevNodeTree+0x2b2
fffff880`031b6bc0 fffff800`02bd2382 : 00000001`00000003 fffff800`02c755f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031b6c10 fffff800`02add961 : fffff800`02bd2080 fffff800`02ee6401 fffffa80`0462db00 89483824`448948f4 : nt!PnpDeviceActionWorker+0x302
fffff880`031b6cb0 fffff800`02d74c06 : 0000b284`0fc00000 fffffa80`0462db60 00000000`00000080 fffffa80`039e7890 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02aaec26 : fffff880`02f64180 fffffa80`0462db60 fffff880`02f6efc0 4420468b`48502444 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b4bb0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsNonCachedIo+23f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff880031b4210 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsNonCachedIo+23f

BUCKET_ID:  X64_0x24_Ntfs!NtfsNonCachedIo+23f

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

For some reason, we are not getting all of the files generated by the tool in this tutorial: [FONT=&quot]http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html. There are some files missing that would give us more information about your system. Please rerun the tool and upload all of the files generated.

[/FONT]

 

[Shappo]

Righteo, i'll post it up when I get home.
Cheers Carl.

 

[CarlTR6]

Very good. We will be here.

 

[Shappo]

Okay, here's the results form the checkdisk:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  94720 file records processed.                                          File verification completed.
  122 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  135966 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  94720 file SDs/SIDs processed.                                         Cleaning up 342 unused index entries from index $SII of file 0x9.
Cleaning up 342 unused index entries from index $SDH of file 0x9.
Cleaning up 342 unused security descriptors.
Security descriptor verification completed.
  20624 data files processed.                                            CHKDSK is verifying Usn Journal...
  37402168 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  94704 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  13274133 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 102390245 KB total disk space.
  49043156 KB in 73516 files.
     49608 KB in 20625 indexes.
         0 KB in bad sectors.
    200945 KB in use by the system.
     65536 KB occupied by the log file.
  53096536 KB available on disk.

      4096 bytes in each allocation unit.
  25597561 total allocation units on disk.
  13274134 allocation units available on disk.

Internal Info:
00 72 01 00 c8 6f 01 00 ba c1 02 00 00 00 00 00  .r...o..........
56 02 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  V...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Oh and Carl.

For some reason, we are not getting all of the files generated by the tool in this tutorial: http://www.sevenforums.com/crashes-d...tructions.html. There are some files missing that would give us more information about your system. Please rerun the tool and upload all of the files generated.

Check the attachment, I just followed that procedure then.

 

[CarlTR6]

Good job; you got them all. Thanks. Your hard disk looks fine and is probably not the problem.

I went back through a couple of your dumps. One of them blamed ntkrnlmp.exe, which is a Windows system core driver and very unlikely to be the real cause. However, it also blamed avguard.exe, which is an Avira file. Avira is known to cause BSOD's on some Win 7 systems and it was definitely involved in this crash. I suggest that you uninstall Avira and download and install Microsoft Security Essentials in it place. See if this helps your system.

After you have uninstalled Avira, enable Driver Verifier again. Remember, it will cause a BSOD if it finds a faulty driver. If Driver Verifier does not find a faulty dirver or if it blames Windows system drivers, I suggest you test your RAM with Memtest from a cold boot after your computer has been off for a while. Let it run for at least seven passes which will take 6-8 hours. After you test your RAM, try removing all but one stick and see if you get BSOD's.

Because most of your BSOD's are occurring shortly after bootup, it could be a PSU problem. Check all of your cables and wires and make sure they are secure. Do you have another known good power supply you could try in your system?

 

[Shappo]

Alrighty thanks, I'll try that soon with Avira, aswell as the memory test.

And about the PSU, I only have one. But, I think it could be the problem too.
I have a XFX GTS 250, you think that's sucking a bit too much out of a 550w PSU? Because that's what I got installed now.

 

[Shappo]

Right, I uninstalled Avira and replaced it with Microsoft security Essentials.
System has been running fine over the last couple of days, but has BSOD's at random occasions (which I can't afford to have).

As you said, I ran driver verifier after I uninstalled Avira and I received a 0x0000000A BSOD.
I made an updated .zip including the last .dmp and put it in my attachment.

Which driver is failing mind me asking?
In the meantime i'll run memtest.
Thanks.

 

[CarlTR6]

I can't really say because I do not know what all is on your system and the total power demands. But there are wattage calculators online where you can calculate what PSU you need. Keep in mind that PSU output decreases as the power supply gets older.

Your latest dump does not appear to be a Driver Verifier enabled dump. It does not point out any driver; rather it blames pool corruption (memory corruption).

Error code A, [FONT=&quot]IRQL_NOT_LESS_OR_EQUAL. [/FONT]Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Thu Nov 18 06:38:24.011 2010 (GMT-5)
System Uptime: 0 days 0:00:14.088
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002aa32b3}

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

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

2: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002aa32b3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02aa32b3 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff880031b5370 -- (.trap 0xfffff880031b5370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031b5f80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aa32b3 rsp=fffff880031b5500 rbp=0000000000000000
 r8=fffff880031b5608  r9=fffff880031b5600 r10=0000000000000002
r11=fffff80002aa27d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae3:
fffff800`02aa32b3 488b09          mov     rcx,qword ptr [rcx] ds:5530:00000000`00000000=????????????????
Resetting default scope

LOCK_ADDRESS:  fffff80002c87400 -- (!locks fffff80002c87400)

Resource @ nt!PiEngineLock (0xfffff80002c87400)    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  : 0xfffff80002c87400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002a82ca9 to fffff80002a83740

STACK_TEXT:  
fffff880`031b5228 fffff800`02a82ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031b5230 fffff800`02a81920 : 80000001`1c889963 fffff980`026f8ee0 fffffa80`035599b0 fffff800`02c0fb40 : nt!KiBugCheckDispatch+0x69
fffff880`031b5370 fffff800`02aa32b3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02ab0668 : nt!KiPageFault+0x260
fffff880`031b5500 fffff800`02a600c7 : 00000000`00000001 fffff8a0`03828060 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0xae3
fffff880`031b55d0 fffff800`02a36bb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`031b5650 fffff800`02bb6ae8 : fffff8a0`03828060 00000000`00000040 00000000`00000003 00000000`00000001 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`031b5680 fffff800`02e34d66 : fffff8a0`0024a720 fffff8a0`00047890 00000000`69634d43 fffff800`000004ef : nt!ExDeferredFreePool+0x1745
fffff880`031b5730 fffff800`02db5bf0 : fffff880`0000001d fffff880`031b5830 fffff8a0`03867600 0053002b`0000001d : nt!CmpCallCallBacks+0x4f6
fffff880`031b5800 fffff800`02dc67f3 : fffffa80`05cbbb10 fffff880`031b5d80 fffff8a0`00022010 fffff8a0`00021a74 : nt! ?? ::NNGAKEGL::`string'+0x1394b
fffff880`031b5880 fffff800`02d7ce84 : fffff800`02d5ccc0 00000000`00000001 fffffa80`05cbbb10 fffff800`02f16a00 : nt! ?? ::NNGAKEGL::`string'+0x2e020
fffff880`031b5b50 fffff800`02d81e4d : fffffa80`05cbbb10 fffff880`031b5cb0 00000000`00000240 fffffa80`04659a50 : nt!ObpLookupObjectName+0x585
fffff880`031b5c50 fffff800`02d60dcc : 00000000`000007ff 00000000`00000000 fffff8a0`03867600 00000000`00000000 : nt!ObOpenObjectByName+0x1cd
fffff880`031b5d00 fffff800`02d63fca : fffff880`031b60b8 fffffa80`00020019 fffff880`031b6050 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`031b5e50 fffff800`02a82993 : 00000000`00000000 fffff800`02a82993 fffffa80`04648b60 fffff880`031b5f20 : nt!NtOpenKey+0x12
fffff880`031b5e90 fffff800`02a7ef30 : fffff800`02cf4498 ffffffff`800001e0 fffff800`02e2e9ae 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`031b6028 fffff800`02cf4498 : ffffffff`800001e0 fffff800`02e2e9ae 00000000`00000001 fffff800`02d24c9f : nt!KiServiceLinkage
fffff880`031b6030 fffff800`02e69afc : 00000000`00000001 ffffffff`800001c8 00000000`00000000 fffff880`031b6150 : nt!IopOpenRegistryKeyEx+0x38
fffff880`031b6090 fffff800`02e69ced : ffffffff`800001e0 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpIsDeviceInstanceEnabled+0x15c
fffff880`031b6100 fffff800`02e69ecf : 00000000`00000000 fffff980`015c4fd0 fffff800`02e69e40 ffffffff`80000140 : nt!PnpIsAnyDeviceInstanceEnabled+0x13d
fffff880`031b61a0 fffff800`02e6b4e7 : fffff880`031b62d8 fffff880`10bcf0e8 00000000`00000000 00000000`00000000 : nt!PnpPrepareDriverLoading+0x8f
fffff880`031b6280 fffff800`02efec30 : 00000000`00000001 00000000`00000000 fffff880`031b6828 ffffffff`80000150 : nt!IopLoadDriver+0x5d7
fffff880`031b6550 fffff800`02d3d794 : fffff880`031b6860 00000000`00000000 00000000`c0000023 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031b6650 fffff800`02d3daa2 : 00000000`00000000 00000000`00000000 fffff880`031b6860 fffff880`031b6828 : nt!RtlpCallQueryRegistryRoutine+0xf4
fffff880`031b66d0 fffff800`02e6ebcc : fffffa80`04bff010 00000000`00000000 00000000`c0000034 fffff880`031b6828 : nt!RtlQueryRegistryValues+0x17e
fffff880`031b67a0 fffff800`02e70362 : fffffa80`04bfe890 fffffa80`04bff010 00000000`00000001 fffff980`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`031b6950 fffff800`02e707fc : fffffa80`05bba220 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2
fffff880`031b6bc0 fffff800`02b85382 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031b6c10 fffff800`02a90961 : fffff800`02b85080 fffff800`02edae01 fffffa80`04648b00 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
fffff880`031b6cb0 fffff800`02d27c06 : fffff800`02bcb78e fffffa80`04648b60 00000000`00000080 fffffa80`039e49e0 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02a61c26 : fffff880`02f64180 fffffa80`04648b60 fffff880`02f6efc0 00000000`00000008 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b58c0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+1745
fffff800`02bb6ae8 90              nop

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  nt!ExDeferredFreePool+1745

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!ExDeferredFreePool+1745

BUCKET_ID:  X64_0xA_nt!ExDeferredFreePool+1745

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

Post your Memtest results. Errors, if any, will show on your screen in red.

 

[Shappo]

Righteo, i'll post sometime tomorrow. I'll try leave it overnight.
Thanks again.

 

[CarlTR6]

You are welcome. "See" you tomorrow.

 

[Shappo]

It's been a few day's now.
Havn't seen a BSOD since.
I think uninstalling avira did it.

 

[CarlTR6]

That is good news and the news we like to hear. Thank you for updating us. I hope your problem is behind you. Happy computing!

 

[Shappo]

Thank you

 

[CarlTR6]

You are welcome.