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

Computer (pc) crashing and locking up-Windows 7


  • Please log in to reply

#1
martens24

martens24

    Member

  • Member
  • PipPip
  • 27 posts
For the past few weeks my computer has begun locking up and crashing periodically. Sometimes it will go all day with no problems. Some times it will randomly freeze up causing me to hard reset. Other times it will crash where the screen is quickly pixelated, goes to black, then a blue screen with a bunch of text where it says it's dumping my hard drive or something like that. That screen isn't up long so I've never been able to read the full text.

I'm running Windows 7. I've tried running a virus scan through McAfee and it shows up clean. Another odd problem which seemed to happen simultaneously is that Chrome has started periodically crashing with a pop up that reads "Whoa! Google Chrome has crashed. Relaunch now?".

A year or less I replaced the hard drive while the computer was still under warranty. I'm not extremely computer savvy so I definitely need some detailed direction. ANY help would be appreciated!

Thanks!!! :-)

Edited by martens24, 04 October 2013 - 12:19 PM.

  • 0

Advertisements


#2
zep516

zep516

    Trusted Helper

  • Malware Removal
  • 5,521 posts
Windows 7 is configured by default to restart immediately after a Blue Screen of Death (BSOD) or other major system problem. This reboot usually happens too fast to see the error message on screen.


How To Disable the Automatic Restart on System Failure in Windows 7

http://pcsupport.abo...t-windows-7.htm

Now you should be able to view the blue screen. The stop error being most important.

In the mean time,

Lets see if we can see what's causing the Blue Screen

Download WhoCrashed
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
martens24

martens24

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
Thanks or helping out so quickly! I've disabled the automatic restart and downloaded WhoCrashed. Here's the report:


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 4.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PHILLIP-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom™ II X6 1045T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 5367971840 total
VM: 2147352576, free: 1934352384




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 10/4/2013 2:42:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFE8A002915628, 0x0, 0xFFFFF80003758F81, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/4/2013 2:42:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFE8A002915628, 0x0, 0xFFFFF80003758F81, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 10/3/2013 3:36:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-19593-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF88001212E14)
Bugcheck code: 0x50 (0xFFFFE8800124B4C0, 0x0, 0xFFFFF88001212E14, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 10/1/2013 11:52:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100113-15943-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804028EAB28, 0xE, 0x0, 0xFFFFF800028EAAEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/1/2013 11:43:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100113-23290-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034E9F4D, 0xFFFFF8800A47FED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/27/2013 2:54:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092713-18766-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034B3B30, 0xE, 0x0, 0xFFFFF800034B3AEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/25/2013 12:49:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092413-18111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034B0B30, 0xE, 0x0, 0xFFFFF800034B0AEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/20/2013 10:17:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092013-15927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFE88000001DE8, 0x0, 0xFFFFF8000347A84C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/20/2013 6:38:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092013-18205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034B0B30, 0xE, 0x0, 0xFFFFF800034B0AEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/18/2013 1:38:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-36707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034EBB30, 0xE, 0x0, 0xFFFFF800034EBAEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 9/16/2013 3:37:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091613-22510-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804028DEB30, 0xE, 0x0, 0xFFFFF800028DEAEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/4/2013 5:15:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090313-18470-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034E7B30, 0xE, 0x0, 0xFFFFF800034E7AEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 9/4/2013 4:58:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090313-34647-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028EFF4D, 0xFFFFF8800B693ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 8/30/2013 2:34:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083013-20046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF804034EAB30, 0xE, 0x0, 0xFFFFF800034EAAEE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/29/2013 12:17:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-23368-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000288A97C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

16 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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
zep516

zep516

    Trusted Helper

  • Malware Removal
  • 5,521 posts
Hi,

No offending third party drivers have been found. :(

That's as far as I go with blue screens. I'm not an analyst. We need someone more knowledge in this area. Usually I can deal with a 3ed Party driver issue. It just becomes a matter of up dating the offending 3ed party program usually. Someone should come along. I'll keep my eyes on it.

Joe

Edited by zep516, 04 October 2013 - 07:53 PM.

  • 0

#5
martens24

martens24

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
Any help out there??? :surrender:
  • 0

#6
zep516

zep516

    Trusted Helper

  • Malware Removal
  • 5,521 posts
Sorry about that,

See if any help here,

http://www.sysnative.com/forums/

They specialize in Blue screens. Tell them zep sent you.

Provide a link to this thread for them.

Joe

Edited by zep516, 12 October 2013 - 07:24 AM.

  • 0

#7
Brazened

Brazened

    Member

  • Member
  • PipPipPip
  • 184 posts
Do you have your Windows disk? Try the repair console in it. The file is in the boot sector and may be corrupted.
  • 0

#8
martens24

martens24

    Member

  • Topic Starter
  • Member
  • PipPip
  • 27 posts
No, I don't have the windows disk. It came loaded on the computer when I bought it. :-/
  • 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