BSOD Windows 7 x64 BAD_POOL_CALLER ntoskrnl.exe

I must add all my drivers are (or at least seem to be) up-to-date, I use Drivermax. I ran verifier.exe, enabled non-Microsoft drivers, restarted and got BSODs before "Welcome" screen, I got to go through Safe Mode and disable this in order to have access to Win7 again. There seems to be another issue with igdkmd64.sys but I don't know how to fix it.

Thank you again.

Your crash dump is not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_____________________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 0, fffff8a012467010}

GetPointerFromAddress: unable to read from fffff80002eb1100
GetUlongFromAddress: unable to read from fffff80002eb11c0
GetUlongFromAddress: unable to read from fffff80002e1fa38
GetUlongFromAddress: unable to read from fffff80002e1fa38
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+112 )

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

Here is some failure report.

Code:

 2048 MB         DDR2-SDRAM (PC2-6400/800 MHz)
Origin: SPD
Memory Size: 2.00 GB
 Memory Type: DDR2-SDRAM (PC2-6400/800 MHz)
Manufacturer of memory: Kingston
Memory Part Code: 9905295-051.A00LF
 Memory Serial Number: 1F09D348


Advanced Test Pattern
  Test begun
10/05/2013 19:10:47  Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:10:55  Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:10:58   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:04   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:06   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:08   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:11   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:13   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:15   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:18   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:20   Error message:  Read-write error at       physical address 000000001FFFF000H memory.
10/05/2013 19:11:22   Error message:
                            Too many errors.
                            10/05/2013 19:11:22
                         Test completed:
                            Failed (Error Code: WME02-I6N)
                            10/05/2013 19:11:23

We will need to run memtest on that module, at least. But better you run memtest with both the modules connected at first. Let us know the situation.

I will wait for memtest86+ report first, and then if memtest comes to be free from errors, for the DV enavled crashdumps.

remundial said:

and I still have BSODs.

remundial said:

Is there any reason why there are BSODs with Driver Verifier enabled (before reaching "Welcome" screen) if it is not a driver issue?

Thank you.

Yes, there are many a reasons. To determine this, we need the full SF DIAG TOOL output files. And, if DV is not enabled properly (dont forget to uncheck all drivers provided by "microsoft" and "unknown" in the list) this may happen, too.

But it is not determined yet that it is not a driver related issue.