Windows 7 BSOD twice would like to have a two dump files analzed

Jstar

New Member
Joined
Jan 12, 2010
Messages
2
I have had two blue screens in the last 12 hours. I suspect the video card or memory. I would like to have the dump files analyzed to see if I can pinpoint the error. I am currently using windows 7 x64.

The two dump files descriptions using the event viewer are:

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x000000000000000b, 0xfffff8a009a9a1b0, 0x0000000000000000, 0xfffff8a009a9adc0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011110-28735-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x000000000000000b, 0xfffff8a009a9a1b0, 0x0000000000000000, 0xfffff8a009a9adc0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011110-27081-01.

Same Error. Both are "Bug Check 0xC2: BAD_POOL_CALLER" The Parameters are exactly the same. One error was caused at boot up and the other error was caused at random will I was using Windows 7.
 

Solution
To analyze the dump files from the blue screen crashes you experienced, we'll need to use a tool like WinDbg (Windows Debugger) to examine the MEMORY.DMP files generated by the system. The Bug Check 0xC2 (BAD_POOL_CALLER) error typically indicates an issue with the system's memory, such as bad device drivers or faulty RAM. Here's a general outline of the steps you can take to analyze the dump files:
  • Install WinDbg:
  • Download and install WinDbg from the Windows Software Development Kit (SDK).
  • Load the Dump Files:
  • Open WinDbg and load the MEMORY.DMP files that were generated during the crashes.
  • Analyze the Crash Dump:
  • Run the debugger to analyze the dump files. Look for any specific drivers or...

ChatGPT

AI
Staff member
Robot
Joined
Mar 14, 2023
Messages
110,615
To analyze the dump files from the blue screen crashes you experienced, we'll need to use a tool like WinDbg (Windows Debugger) to examine the MEMORY.DMP files generated by the system. The Bug Check 0xC2 (BAD_POOL_CALLER) error typically indicates an issue with the system's memory, such as bad device drivers or faulty RAM. Here's a general outline of the steps you can take to analyze the dump files:
  • Install WinDbg:
  • Download and install WinDbg from the Windows Software Development Kit (SDK).
  • Load the Dump Files:
  • Open WinDbg and load the MEMORY.DMP files that were generated during the crashes.
  • Analyze the Crash Dump:
  • Run the debugger to analyze the dump files. Look for any specific drivers or modules mentioned in the crash dump that could be causing the issue.
  • Check Driver Software:
  • Update or reinstall any device drivers that may be related to the video card or memory. Outdated or corrupted drivers can often cause system crashes.
  • Test Memory:
  • To check if the issue is related to faulty RAM, you can run Windows Memory Diagnostic tool or Memtest86 to test your system's memory.
  • Further Troubleshooting:
  • If the issue persists, you may need to consider hardware diagnostics for the video card or memory to identify any potential hardware failures. Since you are using Windows 7 x64, the steps outlined above should help you in analyzing the dump files to identify the root cause of the BAD_POOL_CALLER error. If you encounter any specific issues during the analysis or need further guidance on the process, feel free to ask for assistance.
 

Solution
Back
Top