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


  • Please log in to reply

#1
gamie

gamie

    Member

  • Member
  • PipPip
  • 11 posts
Hello, I'm Irene.

I don't know what's the problem with my laptop exactly. Initially, it will restart without warning while I'm browsing the net.

However lately, whenever I login to my account, my laptop will automatically bluescreen and restart, and this process will go on repeatedly.

The blue screen message reads "A problem has been detected and windows has been shut down to prevent damage to your computer......... Beginning dump of physical memory" Something like that.

Thankfully, I'm still able to use my laptop and online by operating on safe mode with networking.

Please help me out. I'm not really good with computers so I hope you'll provide me with simple directions as to how to handle this :)

Thanks alot in advance! :)
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
FYI GTG does not recommend the use of Registry Cleaners as they have the potential to cause the registry to become unstable or unusable. If the system is getting BSOD then there should be a record of what caused the crash. Please do the following steps and attach the requested log.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#3
gamie

gamie

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Hi rshaffer61,

Here's the analysis by WhoCrashed.

Thank you. :)



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 7/1/2009 6:42:08 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE21EA090, 0xC0000005, 0x7C9101B3, 0x52F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/30/2009 12:33:43 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE2023BE8, 0xC0000005, 0x75E9AD23, 0x52F240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/30/2009 12:26:57 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1F254D8, 0xC0000005, 0x7C9101B3, 0x69DE88)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/30/2009 6:54:16 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E390D8, 0xC0000005, 0x75E9AD23, 0x10DF240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:23:05 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1D71398, 0xC0000005, 0x7C9101B3, 0x69ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:21:36 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1DC4118, 0xC0000005, 0x7C910F48, 0x69F96C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:19:51 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1BE6C00, 0xC0000005, 0x7C9101B3, 0x69DA18)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:16:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1F5F9A8, 0xC0000005, 0x75E9AD23, 0x69F240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:15:10 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1ED1468, 0xC0000005, 0x7C9101B3, 0xE8ED04)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:14:20 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE199BA00, 0xC0000005, 0x75E9AD23, 0x69F240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:12:12 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1D813F0, 0xC0000005, 0x7C910F48, 0x69F96C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:10:15 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1F6AC10, 0xC0000005, 0x7C9101B3, 0x52F36C)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/25/2009 1:16:55 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1F85180, 0xC0000005, 0x75E9AD23, 0x109F240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 6/25/2009 1:16:03 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE16E85E0, 0xC0000005, 0x75E9AD23, 0x52F240)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/23/2009 3:25:27 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1A0D2D0, 0xC0000005, 0x75E94874, 0x52F1B8)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/23/2009 3:19:34 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E48F80, 0xC0000005, 0x7C9106C3, 0x52DD88)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 6/23/2009 3:15:59 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC000021A (0xE1E90E50, 0xC0000005, 0x7C9111DE, 0x126F998)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK this tells me one thing. Your OS system is corrupt and you need to do a repair installation.
Being that this is a laptop you should have a recovery partition on your hard drive. What I would suggest is doing a repair installation on your windows if there is important data you need to save.
The better option would be to backup your data and do a full installation of your OS system.
I am going to ask one of the Malware techs to take a look at this topic also and see if he suspects a infection. Please be patient as this might take some time to accomplish.
  • 0

#5
gamie

gamie

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Hi rshaffer61,

The blue screen appears once I log into my user account and I have to restart. This occurs repeatedly and sometimes I have to operate with "safe mode with networking".

However there are also times when it will function on normal mode, but only after I've restarted it for a few times...

I've tried scanning with avg but to no avail...
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I have discussed this with a malware tech and he believes as I do and thta is your OS system is corrupt.
That being said the course of action is now to backup your important data. Since windows will not boot up then you can try Puppy Linux to get to the data.

Get Puppy Linux Download this file:
puppy-2.16-seamonkey-fulldrivers.iso
and burn it to cd
..
if you don't have a burning program that will burn .ISO files get burncdcc from my signature below ..a small FAST no frills iso burning program...

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start BurnCDCC
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its puppy-2.16-seamonkey-fulldrivers.iso
3. Select the ISO file
4. click on Start


make sure in the bios the cd drive is the first boot device....

put the cd in the cd drive..boot your computer....puppy will boot and run totally in ram...if your hardware is in good working order you will know...
after you get it running and your at the desktop...you take the puppy linux cd out and then you can use the burner to copy all yor data to cd/dvds
you can also use it to backup your data to a external usb harddrive..You must have it hooked to the computer when you boot up with puppy.
  • 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