Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen - Dumping Physical Memory


  • Please log in to reply
26 replies to this topic

#1 LazyMan826

LazyMan826

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 03 January 2012 - 04:37 PM

Hello,

My computer will randomly decide to put up this Blue Screen and tell me it is dumping the physical memory.
It says that I should make sure I did not download any new software and to make sure everything is updated.

So...
I had not put anything new on my computer recently so kind of ignored that part.
I went through and updated the programs I was using while it crashed (mozilla firefox, internet explorer, itunes) and yet it still keeps crashing.
It just crashed a few minutes ago while loading up a game. I was trying to isolate what program is doing this but it seems any of them pretty much bring it on.

Also, it seems Mozilla now freezes randomly when opening a new tab or trying to load a page for about 10-15 seconds and show a white screen saying (Not responding) on top. It usually fixes itself but this will sometimes lead to the blue screen.

There is a mention of the BIOS memory and I should take off caching and shadowing

Not sure what to do and how would I access the BIOS memory if this is the next step?

Edited by LazyMan826, 03 January 2012 - 04:41 PM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:39 PM

Posted 03 January 2012 - 04:57 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 03 January 2012 - 05:04 PM

Usually when it crashes I get annoyed and just show it down and reboot and don't let it take the time to go through its whole blue screen thing so there are only 7 crashes listed here.

==================================================
Dump File : 010312-22994-01.dmp
Crash Time : 1/3/2012 3:26:36 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000020
Parameter 2 : ffffffff`c000009d
Parameter 3 : fffffa80`062947c8
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010312-22994-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 289,320
==================================================

==================================================
Dump File : 123011-36675-01.dmp
Crash Time : 12/30/2011 9:27:33 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0644eb30
Parameter 3 : fffffa80`0644ee10
Parameter 4 : fffff800`02fd1300
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\123011-36675-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 278,576
==================================================

==================================================
Dump File : 123011-36426-01.dmp
Crash Time : 12/30/2011 9:01:10 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`060e2b30
Parameter 3 : fffffa80`060e2e10
Parameter 4 : fffff800`02fd3300
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\123011-36426-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 281,608
==================================================

==================================================
Dump File : 102911-30732-01.dmp
Crash Time : 10/29/2011 7:33:31 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0640f720
Parameter 3 : fffffa80`0640fa00
Parameter 4 : fffff800`02f7d300
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102911-30732-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 277,744
==================================================

==================================================
Dump File : 102911-39905-01.dmp
Crash Time : 10/29/2011 7:15:24 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`06330b30
Parameter 3 : fffffa80`06330e10
Parameter 4 : fffff800`02f81300
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102911-39905-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 277,648
==================================================

==================================================
Dump File : 102911-23493-01.dmp
Crash Time : 10/29/2011 3:33:35 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`4000d960
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`31efe860
Parameter 4 : fffff880`01b2cc7c
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+f1c7c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70700
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102911-23493-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 289,320
==================================================

==================================================
Dump File : 012211-17440-01.dmp
Crash Time : 1/22/2011 8:35:54 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02c858b6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012211-17440-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 281,624
==================================================

#4 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:39 PM

Posted 03 January 2012 - 05:55 PM

What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

#5 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 03 January 2012 - 06:02 PM

I literally can't think of anything that I added or changed to my computer. I use it just to type of worksheets for school, go on the internet, and play a web-based game every once and a while.

I wonder if I should just load it backup to before October 29th. I can do something like that right?

#6 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:39 PM

Posted 03 January 2012 - 06:17 PM

Let's test some hardware before we decide what to do.

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

#7 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 03 January 2012 - 06:23 PM

Ummm....really not that good with computers so that didn't really make sense to me.
Can we try something else that is a little more easier for an average joe like me?

Appreciate the help so far though!!!!!

#8 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:39 PM

Posted 03 January 2012 - 06:26 PM

What is it you don't understand? The instructions are pretty straightforward and designed for non-technical people.

#9 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 03 January 2012 - 08:49 PM

How do I make sure the cd drive is at the top of the bios utility?

Also, where is the command prompt icon?

#10 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:39 PM

Posted 04 January 2012 - 08:38 AM

http://pcsupport.about.com/od/fixtheproblem/ss/bootorderchange.htm

http://windows.microsoft.com/en-US/windows7/Command-Prompt-frequently-asked-questions

#11 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 05 January 2012 - 09:40 PM

I think this is too difficult for me.

I downloaded the memtest thing to my desktop.
Then I downloaded the first utility iso thing that you gave me from the website. It says I should right click on the memtest and then click on file name and choose burn to cd. That is not an option on mine and I don't know what to do! I took a print screen to show you but then I don't know how to upload a picture on here so yeah...

Help please! I am so lost and frustrated! I have some iso thing and the memtest thing both sitting on my desktop. The iso thing just asks if I want to repair or uninstall and I tried opening the memtest with the iso thing by browsing the files and then my computer went berserk and millions of black screens kept popping up so I had to shut it down.

#12 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 06 January 2012 - 12:37 AM

After using like 4 different burning software, I finally got it onto the disk (after 3 disks were apparently full or corrupt and I never used them before!!!)

It is currently running memtest with a blue screen. It has been going for like 30 minutes now so I will just let it keep going and let you know what happens.

#13 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 06 January 2012 - 01:59 AM

My computer has ran for about an hour and 45 minutes with 2 passes and found 0 errors.
Does this mean that nothing is wrong with my memory?

My computer is still pretty sluggish and all my programs (internet, itunes, games, etc) will randomly stop responding and take 10-15 seconds to work again.

#14 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:12:39 PM

Posted 06 January 2012 - 08:53 PM

Since this error specifies that the pagefile on the hard drive could not serve up a piece of data, I suggest testing the hard drive next.

First, please follow the chkdsk instructions from Allan and relate your results.

Click the Start Orb and type cmd. In search results, right-click cmd and select Run as Administrator.

In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.


Perform diagnostics on your hard drive.
  • Click the Start Orb and type in "device manager." In the search results, double-click device manager.
  • Double-click Disk Drives. The first drive listed is most likely the one you want to test.
  • Take note of its manufacturer (Samsung, Western Digital (WD), Seagate (ST), Toshiba, etc.)
    • If are still uncertain about your hard drive's manufacturer, include what you see there in your next reply and await further instructions.
  • Download the appropriate diagnostic tool from here.
    • Some tools can be installed and run from within Windows, others will need to be burned to CD and booted from. Instructions
    • If you do not see your manufacturer listed, or are confused or overwhelmed (this is perfectly OK), use SeaTools for Windows. If Windows is highly unstable or won't boot, use SeaTools for DOS.
  • Direct the program to perform a 'short-test'. If it passes, perform a 'long-test'. This will likely take a few hours.
  • Report the results in your next reply.

Edited by LucheLibre, 06 January 2012 - 09:03 PM.

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#15 LazyMan826

LazyMan826
  • Topic Starter

  • Members
  • 75 posts
  • OFFLINE
  •  
  • Local time:10:39 AM

Posted 15 January 2012 - 06:38 PM

I did a regular chkdsk and it found nothing wrong.

I also did a chkdsk /r and when it restarted, it took about 4 hours and it had only gotten about halfway. I went to bed and let it run. When I got up the next morning, it was done but my comptuer was sleeping and when I woke it up, nothing was on there so I have no clue if it was good or bad....but why did it take so long after restarting to run? This concerns me.

I just did the short test and it passed.

I am going to do the long test right now and see what happens.

I have been away and busy the last week so I haven't had time to work on the laptop. Appreciate all your help though and I will let you know what happens next.

Since this error specifies that the pagefile on the hard drive could not serve up a piece of data, I suggest testing the hard drive next.

First, please follow the chkdsk instructions from Allan and relate your results.

Click the Start Orb and type cmd. In search results, right-click cmd and select Run as Administrator.

In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.


Perform diagnostics on your hard drive.
  • Click the Start Orb and type in "device manager." In the search results, double-click device manager.
  • Double-click Disk Drives. The first drive listed is most likely the one you want to test.
  • Take note of its manufacturer (Samsung, Western Digital (WD), Seagate (ST), Toshiba, etc.)
    • If are still uncertain about your hard drive's manufacturer, include what you see there in your next reply and await further instructions.
  • Download the appropriate diagnostic tool from here.
    • Some tools can be installed and run from within Windows, others will need to be burned to CD and booted from. Instructions
    • If you do not see your manufacturer listed, or are confused or overwhelmed (this is perfectly OK), use SeaTools for Windows. If Windows is highly unstable or won't boot, use SeaTools for DOS.
  • Direct the program to perform a 'short-test'. If it passes, perform a 'long-test'. This will likely take a few hours.
  • Report the results in your next reply.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users