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

PC Restarts and BSoD


  • Please log in to reply

#1
Rastik

Rastik

    New Member

  • Member
  • Pip
  • 4 posts
Hello, I have some issues with my Computer, ive read one topic about BSoD.
Ive cleaned pc and ive removed RAMs and cleaned them, thats the time when it started first, PC started to boot up slowly and i had some virus problems with missing parts of windows so ive reinstalled windows and all was looking fine until random pc crashing.So i have some reports from Who Crashed:

On Thu 30.7.2009 15:12:22 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xBA33, 0x2, 0x1, 0x806E6A8E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Operační systém Microsoft® Windows®
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 25.6.2009 16:07:19 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8060D7DB, 0xA8EC0B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Operační systém Microsoft® Windows®
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.

(Its weird because it happend in Thu 5 days later!)

Attached Files


  • 0

Advertisements


#2
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
check your device manager for any yellow ! or ? marks ...
to check... Click on Start and then Run...Type in devmgmt.msc and then press Enter
  • 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