Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Windows 7 x64 BAD_POOL_CALLER ntoskrnl.exe


17 May 2013   #1

Windows 7 Professional x64 SP1
 
 
BSOD Windows 7 x64 BAD_POOL_CALLER ntoskrnl.exe

Hi there,

I've had a serious problem of BSOD since I first installed Windows 7 (x86 and x64) on this laptop; a couple of years ago I upgraded RAM from 2 GB to 4 GB (a pair of sticks from a brand called SUPER TALENT), I was hoping I could use Windows 7 x64, but I had a lot of BSOD related with ntoskrnl.exe, I got tired looking for a fix but I could find any, so I bought a pair of Dell Certified memory sticks some days ago (2 GB each) because I thought the other sticks were damaged... For a couple of days Windows 7 seemed to work fine till some hours ago, BSODs returned.

I have installed Windows 7 x32/x64 several times, and I cannot avoid BSODs to appear. Windows XP works fine, and Ubuntu x86 PAE both run smoothly on this laptop, but now I need to migrate to Windows 7 and I'm not able to do it because of continuous BSODs.

==================================================
Dump File : 051713-13244-01.dmp
Crash Time : 2013-05-17 19:32:49
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`00000000
Parameter 4 : fffff8a0`12467010
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051713-13244-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 276.960
==================================================

Thank you very much for your help.

Best regards.


My System SpecsSystem Spec
.

17 May 2013   #2

Windows 7 Professional x64 SP1
 
 

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 Windows 7 again. There seems to be another issue with igdkmd64.sys but I don't know how to fix it.

Thank you again.
My System SpecsSystem Spec
18 May 2013   #3
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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   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   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   Tip

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
---------
My System SpecsSystem Spec
.


18 May 2013   #4

Windows 7 Professional x64 SP1
 
 

Thanks for your response.

This laptop has a Dell app called "PC Checkup", months ago I ran some tests on memory and I always got a bunch of errors, that's why I bought Dell Certified memory sticks, but just after I installed those new modules I ran other tests and get the same errors I had in the past, fortunately I saved a report; some minutes ago I ran other test and it didn't find any error, I read both reports and I've found this on the old one:

"Evaluating state: The hardware was modified since the last assessment. The results belong to an earlier evaluation." (I've translated the reports into English, some text is not show when opened in browsers, I had to modify some things on MS Word, you can find the reports in attached file).

Months ago I also ran memtest86+, I had some clean tests and other were halted by BSODs, the process is very time consuming and I don't know if it's worth the time. I have serious suspicion on graphic card drivers, everytime I install Windows 7 I struggle some minutes trying to make graphics to work, it crashes 2 or 3 times before I'm able to install drivers; although graphics seem to be ok, maybe there's something inherently wrong or incompatible with Windows 7 about this graphic card, but I've read other Dell Vostro 1700s run smoothly on Windows 7 so I don't know what's all about...

Thank you again.
My System SpecsSystem Spec
18 May 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
18 May 2013   #6

Windows 7 Professional x64 SP1
 
 

Yes, there's a failure report showing that but as I wrote before ""Evaluating state: The hardware was modified since the last assessment. The results belong to an earlier evaluation.", with new Dell Certified memory sticks there's no error shown (please see second report), and I still have BSODs.
My System SpecsSystem Spec
18 May 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

I will wait for memtest86+ report first, and then if memtest comes to be free from errors, for the DV enavled crashdumps.
Quote   Quote: Originally Posted by remundial View Post
and I still have BSODs.
My System SpecsSystem Spec
18 May 2013   #8

Windows 7 Professional x64 SP1
 
 

Ok, I will run 8 passes of memtest86+, I'm already running the first one and send results ASAP. I've realized the memtest I ran before was not "86+", just "memtest", this one runs outside Windows 7.

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.
My System SpecsSystem Spec
18 May 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by remundial View Post

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.
My System SpecsSystem Spec
18 May 2013   #10

Windows 7 Professional x64 SP1
 
 

There have been completed 8 passes with memtest86+, not a single error reported. I enabled DV again, according to the indications given here, Windows 7 tried to start up 5 consecutive times and it didn't manage to come to "Welcome" screen, a less than a second BSOD appeared every time, automatically reset, I went through Safe Mode, and reset DV. No new minidumps have been saved. What's the next step without this information? Trying to individualize the driver that's causing problems with DV?

Thank you.
My System SpecsSystem Spec
Reply

 BSOD Windows 7 x64 BAD_POOL_CALLER ntoskrnl.exe




Thread Tools



Similar help and support threads for2: BSOD Windows 7 x64 BAD_POOL_CALLER ntoskrnl.exe
Thread Forum
BSOD - ntoskrnl.exe - BAD_POOL_CALLER BSOD Help and Support
Solved BSOD BAD_POOL_CALLER Windows 7 x64 Home Premium! BSOD Help and Support
BSOD BAD_POOL_CALLER happens randomly or at start when windows loads BSOD Help and Support
Windows 7 enterprise 86x BSOD BAD_POOL_CALLER BSOD Help and Support
Bad_pool_caller bsod windows 7 BSOD Help and Support
BSOD bad_pool_caller windows 7 BSOD Help and Support
BSOD bad_pool_caller windows 7 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 11:39 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33