Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account

BSOD question

  • Please log in to reply




  • Member
  • PipPip
  • 20 posts
hi geeks, i got a BSOD yesterday.... that is the first time i had with this computer, but after i reboot everything is fine and back to normal. My question is, is it normal???

On Sat 6/8/2011 12:16:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-34398-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x50, 0x2, 0x0, 0xFFFFF80002CA3C62)
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 which cannot be ide

Is it something that really happens to a PC once in a while??? Im not asking for you guys to troubleshoot my PC because it is working fine now...
again my pc is working fine now, im just a bit worried that i had my first BSOD with this pc and sooner or later it will get worse....... thanks for helping...
  • 0




    Member 5k

  • Technician
  • 7,091 posts
Download and run WhoCrashed. It may provide more information. If not, watch for additional problems. Post back here with results and if more questions.

Most BSODs are caused my defective/corrupted drivers or failing hardware. If you get another, see what WhoCrashed says about it as well.
  • 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