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

Blue Screen of Death on laptop


  • Please log in to reply

#1
Rani

Rani

    Member

  • Member
  • PipPip
  • 40 posts
Hi,

Over the past few months I've had the blue screen of death come up on my laptop. It comes up once every few months I think. I haven't been the user on the laptop when it has come up so I haven't been able to make a note of the error that actually comes up.

I understand it can be because of a clash in software?

I hope someone can help as my laptop is only a few years old and I think it still has a lot of life left in it...

Thanks!
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#3
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Hi,

Thank you for your reply and sorry for the delay in responding. Below is the log from the scan which was run as instructed:

==================================================
Dump File : 052011-19921-01.dmp
Crash Time : 20/05/2011 19:23:37
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`40007330
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`917f0860
Parameter 4 : fffff880`00e66f40
Caused By Driver : partmgr.sys
Caused By Address : partmgr.sys+df40
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052011-19921-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 370,336
==================================================

==================================================
Dump File : 041311-30763-01.dmp
Crash Time : 13/04/2011 21:57:52
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`50000a70
Parameter 2 : ffffffff`c00000c0
Parameter 3 : 00000000`19124880
Parameter 4 : fffff8a0`0014eb44
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.16792 (win7_gdr.110408-1633)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\041311-30763-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 362,568
==================================================

==================================================
Dump File : 040711-21949-01.dmp
Crash Time : 07/04/2011 21:21:48
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`40009818
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`70b8b860
Parameter 4 : fffff880`01303c7c
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+f1c7c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\040711-21949-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 370,280
==================================================

==================================================
Dump File : 031111-21044-01.dmp
Crash Time : 11/03/2011 23:20:22
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`044f5340
Parameter 3 : fffffa80`044f5620
Parameter 4 : fffff800`02fd22d0
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.16792 (win7_gdr.110408-1633)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031111-21044-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 362,568
==================================================

==================================================
Dump File : 031111-21777-01.dmp
Crash Time : 11/03/2011 23:16:44
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`044f2b30
Parameter 3 : fffffa80`044f2e10
Parameter 4 : fffff800`02f852d0
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.16792 (win7_gdr.110408-1633)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031111-21777-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 362,568
==================================================
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x0000007A: KERNEL_DATA_INPAGE_ERROR
(Click to consult the online MSDN article.)
A page of kernel data was not found in the pagefile and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.




0x000000F4: CRITICAL_OBJECT_TERMINATION
(Click to consult the online MSDN article.)
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive;







Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to [b]Winlogon]/b] and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.
  • 0

#5
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Hi,

Sorry for the late reply, but given the length of time the scan takes thought it was best I did it on a weekend. I'm currently trying to do this. I have Windows 7 so I don't have 'Run' on my start menu. I did however type in Chkdsk /r in the search field and pressed enter. A black box came up saying 'the type of the file system is NTFS. Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?' I pressed Y, it didn't reboot so manually rebooted but when it restarted the laptop was running as normal...
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
So chkdsk did not run? If not reboot and see if it will run then.
  • 0

#7
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
No chkdsk did not run, rebooted twice...
  • 0

#8
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f


I notice in your above post you initially said to do Chkdsk /r and then right at the end said that the scan that starts after the system reboot will take longer than chkdsk /f. Was chkdsk /r a typo and should I be typing chkdsk /f?
  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
no chkdsk /r is what you want to run.
It is longer then the other and it's there just in case we have someone run the other before.
Is this system XP, Vista or win 7 ?
  • 0

#10
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Windows 7.
  • 0

Advertisements


#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Ahh OK that makes a difference on how you initiate it. Try it this way and I bet it will work then. :)

Tutorial for running chkdsk in Vista\Win 7 located HERE.
  • 0

#12
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Sorry for the late reply. As per the link you provided I used the first method as the second wasn't entirely clear to me (how do you get a command prompt up on Win 7??). I kept 'automatically fix file system errors' clicked but didn't click 'scan for and attempt recovery of bad sectors'. Should I have done so? Clicked start. Nothing happened. Restarted the laptop and still nothing happened... Please could you advise? Thanks.
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You did it right. It looks like a repair is needed so lets try the first step.

Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
  • 0

#14
Rani

Rani

    Member

  • Topic Starter
  • Member
  • PipPip
  • 40 posts
Hello, it says that Windows Resource Protection did not find any integrity violations. I've only run this once though, and I note the website says sometimes it can take 3 tries to find anything wrong.
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
try it again. I don't think it would take that any times and on most systems it finds issues right away. Heck I'm willing to give it another try though.
:)
  • 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