Help with BSOD

[cheesybiscuits]

Hi,
Im new here as you can probably tell and am not really sure whats happening

Every now and then i get a BSOD saying at the top

BAD_POOL_CALLER
Stop 0x000000c2 (0x00000007, 0x00001097, 0x00040012, 0x8587A528)

I've read a few other posts but none really solved the problem

Any help would be appreciated

Also i've seen other people upload memory dumps

how do you do this

btw im running on windows 7 Ultimate 32bit

 

[zigzag3143]

Hi,
Im new here as you can probably tell and am not really sure whats happening

Every now and then i get a BSOD saying at the top

BAD_POOL_CALLER
Stop 0x000000c2 (0x00000007, 0x00001097, 0x00040012, 0x8587A528)

I've read a few other posts but none really solved the problem

Any help would be appreciated

Also i've seen other people upload memory dumps

how do you do this

btw im running on windows 7 Ultimate 32bit

We need the actual DMP file. Use these to find and upload it to us. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks

Ken

 

[Jonathan_King]

Welcome!

To upload the memory dumps, copy the dmps from C:\Windows\Minidump to your desktop. Select all of them, right-click, and select Send to>Compressed folder.

On your next post, you will see a paperclip icon. Click it, and upload the zip folder.

 

[cheesybiscuits]

4 different dumps here

 

[Jonathan_King]

Looks like Bit Defender is causing the issue. You may consider removing it and replacing it with Microsoft Security Essentials or another program of your choice.

You may also try updating your network card drivers, and see if that helps also

~JK

 

[cheesybiscuits]

i have uninstalled bitdefender and so far no bsods

Hopefully it will stay that way

Yaaay

Thank you sooooooooo much for the fast replies

 

[cheesybiscuits]

oops spoke too soon

the time in between the crashes was a lot longer though

Again please help

 

[Jonathan_King]

Still looks like Bit Defender is causing the issue. Try reinstalling it, then use Revo Uninstaller to completely remove all traces.

Also, did you try updating your network adapter drivers too?

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


Loading Dump File [C:\Users\Jonathan\Desktop\040210-15256-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
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8284d000 PsLoadedModuleList = 0x82995810
Debug session time: Fri Apr  2 18:41:26.629 2010 (GMT-4)
System Uptime: 0 days 0:56:48.439
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\BdfNdisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BdfNdisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for BdfNdisf6.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, 90e9d59f}

Unable to load image \SystemRoot\system32\DRIVERS\PRISMA02.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PRISMA02.sys
*** ERROR: Module load completed but symbols could not be loaded for PRISMA02.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : BdfNdisf6.sys ( BdfNdisf6+159f )

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

 

[cheesybiscuits]

how do you update your network drivers

we have an old router (Wanadoo which was bought over by orange so there wont be any new drivers for it) but it works and the drivers I have right now are straight from the included CD so i dont think they are out of date

 

[Jonathan_King]

Find your card in Device Manager, right-click on it, and select Update Driver Software.

 

[cheesybiscuits]

it says it is fully updated

 

[Jonathan_King]

Try downloading this driver: Drivers and Downloads

If it won't install, try compatibility mode for Vista.

 

[cheesybiscuits]

never mind install

it wont even download

every time i click download it just gets the dell driver download manager and says nothing is selected and closes itself

BTW I did the thing with bit defender and that worked smoothly

Any Ideas???

 

[Jonathan_King]

Try selecting "Download Via Internet Browser".

View attachment 64868

Since it looks like Bit Defender was causing the issue, let's hope now that the complete uninstallation stops the BSODs.

 

[cheesybiscuits]

its ok managed to install (used internet explorer instead of firefox)

So that should be it now right

Fingers crossed

 

[cheesybiscuits]

thanks for all the help by the way

 

[Jonathan_King]

You're welcome.

I really believe that will work. If not, just post the new dmps and we'll take a look.