Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Looking for help with mini dump files


  • Please log in to reply

#1
noiseordinance

noiseordinance

    New Member

  • Member
  • Pip
  • 5 posts
Hi there. I've got this nasty ongoing problem with my Dell Vostro 1500. I get various BSOD's from Windows 7 and Vista. To start, my computer came with XP Pro, and I never had BSODs. I switched to Windows 7, which I love, but started getting Bad_Pool_Caller, irql_not_less_or_equal, etc. I did a fresh install of Vista, same thing. It seems like they happen once a day, even prior to installing any software. I went so far as to buy new memory, and even after running Memtest for a day without any fails, I'm still having the problem. I also downgraded my BIOS, same thing.

Can anyone offer any pointers based on my Mini Dump files? I'm new here, so if I'm doing this wrong, please forgive. I'm at wit's end and keep losing data while typing college essays and whatnot...

Thank you!!!

Attached Files


  • 0

Advertisements


#2
noiseordinance

noiseordinance

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
By the way, I saw another post where someone asked the OP to run BlueScreenView and select all > save to notepad > post the output, so here it is:

==================================================
Dump File : 011810-29499-01.dmp
Crash Time : 1/18/2010 4:21:48 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00001097
Parameter 3 : 0x00000000
Parameter 4 : 0xaafbb008
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+11f1b6
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\011810-29499-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 011510-16255-01.dmp
Crash Time : 1/15/2010 11:10:01 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x93f8d687
Parameter 3 : 0x8a7825a8
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+3d687
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\011510-16255-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 011410-19063-01.dmp
Crash Time : 1/14/2010 3:26:29 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00001097
Parameter 3 : 0x00000000
Parameter 4 : 0x925f0008
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+11f1b6
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\011410-19063-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 011310-19141-01.dmp
Crash Time : 1/13/2010 10:39:53 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00001097
Parameter 3 : 0x00000000
Parameter 4 : 0xb0ac1008
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+b1cd0
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\011310-19141-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
It looks like possible RAM issue.

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#4
noiseordinance

noiseordinance

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
I have two sticks of RAM, 1GB each. I have tested this current pair with memtest. Additionally, this computer actually came with a different pair of memory, which also tested perfect through Memtest, yet caused constant BSODs in both Vista and Windows 7 (fresh installs)... Oh, and I've also had Ubuntu installed on this machine with not so much as a single problem over the past year, for what it's worth... I get the feeling it's a driver issue, though I have no clue how to tell which driver...
  • 0

#5
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Did you?

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A


  • 0

#6
noiseordinance

noiseordinance

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
I've memtested with one stick at a time with no problems. The weird thing is that the BSODs come at random period. Could be the second that I get to my desktop, could be after 8 hours of usage... There doesn't seem to be a specific event that triggers this.
  • 0

#7
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Please, re-read my last reply.
I'm talking about physically removing one RAM stick and running the computer on one RAM stick at a time.
  • 0

#8
noiseordinance

noiseordinance

    New Member

  • Topic Starter
  • Member
  • Pip
  • 5 posts
I could try that I guess, though that would imply something wrong with my motherboard or BIOS / memory voltage, since I can't imagine two pairs of memory would both be bad? The problem is that you have to gut the whole laptop to get to the second stick of memory, so it's a little difficult for testing, especially since I've now gone 2 days without a BSOD. But I guess the main concern I have is that my minidump files to not point to an obvious driver issue, and instead, specifically point to a memory issue... is that correct? Thank you for your help by the way...
  • 0

#9
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts

my minidump files to not point to an obvious driver issue, and instead, specifically point to a memory issue... is that correct?

That's only my opinion.
Dump files are not always clearly pointing to some obvious culprit.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP