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 - dumping physical memory

25 Jun 2010   #1
Kerpal

Windows 7 x64
 
 
BSOD - dumping physical memory

Help me, my computer is crashing.

Sometimes the screen goes all black without any response from keystrokes, other times i get lines of different colors and weird patterns. And other times i get the BSOD.

here is my dump file:
Attachment 80946

Windows 7 x64
Asus Crosshair III Formula AM3
AMD Phenom II X4 965
4 x OCZ PC3-12800 Black Edition Ready CL8 Dual
Ati Sapphire Radeon HD 5870

Edit: Just wanted to say Hello!


My System SpecsSystem Spec
.
25 Jun 2010   #2
Kerpal

Windows 7 x64
 
 

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


Loading Dump File [C:\Users\xxxx\Desktop\062510-20046-01\062510-20046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02811000 PsLoadedModuleList = 0xfffff800`02a4ee50
Debug session time: Fri Jun 25 02:07:09.429 2010 (GMT+2)
System Uptime: 0 days 0:10:22.162
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 5560001, 0, 0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+70600 )

Followup: MachineOwner
---------
whats ntoskrnl.exe?
My System SpecsSystem Spec
27 Jun 2010   #3
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote:
whats ntoskrnl.exe?
It is a Windows system core file.

ntoskrnl.exe - Wikipedia, the free encyclopedia

It is most likely NOT the cause of your problem.

Read this thread, update your system specs and attach your actual mini dump files to your next post. We will be glad to help you.

[1 - Novice] How to ask for help with a BSOD problem
Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy
.
My System SpecsSystem Spec
.

Reply

 BSOD - dumping physical memory




Thread Tools




Similar help and support threads
Thread Forum
BSOD Dumping Physical Memory
Guys...Help...I have been using my Laptop for almost 4 years & never had any issue.Just one year back, I had a BSOD.So, I removed all of my external USB Devices & it was fixed.Now, the BSOD appears when the Windows starts & Starts dumping physical Memory.I tried Startup Repair & it found no errors....
BSOD Help and Support
BSOD dumping physical memory
I get a new Graphics card NVIDIA GeForce 7100 GS and it runs good but when i install the Driver it's showing me BSOD in attachments i upload the scan of SF diagnostic tool. my CPU Intel Celeron i also have an integrated Intel Graphics card RAM 1Gb DDR3 if you need more info tell me... ...
BSOD Help and Support
BSOD : Dumping physical memory to disk : 100
My laptop reboots again and again after 5 mins. A bule Screen appears with lot of information but at the end of blue screen it shows some thing like this ans restarts. Collecting Data for crash dump ... Initializing disk for crash dump ... Beginning dump of physical memory .. Dumping physical...
BSOD Help and Support
BSOD dumping physical memory...
Hello, i've been getting this error a lot, for a little over two months now, and i've had just about enough with it now -.- the blue screen just shows up randomly, i don't necessarily need to be doing anything specific, just the usual: browsing the internet, listening to a lecture, typing in ms...
BSOD Help and Support
BSOD: dumping physical memory to disk
I was just browsing the internet when it first happedned; I hit power switch in panic... I keep getting the prior read title message (in BSOD) whenever I get to the user screen unless I run in safe mode and I got no idea what to do. can any1 help? :cry: Edit: I have Attached the Zip...
BSOD Help and Support
BSOD: dumping physical memory to disk
BSOD: dumping physical memory to disk I was just browsing the internet when it first happedned; I hit power switch in panic... I keep getting the prior read title message (in BSOD) whenever I get to the user screen unless I run in safe mode and I got no idea what to do. can any1 help? :cry:...
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 23:06.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App