Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

blue screen please help


  • Please log in to reply
4 replies to this topic

#1 euphaus

euphaus

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:24 AM

Posted 26 August 2009 - 09:41 PM

Starting this morning my laptop would get the blue screen of death after approximately five minutes of operation. This problem has persisted and i've deleted my only recently downloaded game, which was Snood and i downloaded it a couple days ago and did not have any problems at the time. The screen itself would only stay up for about 10 seconds at a time, but the gist of it was that my computer needed to shut down in order to avoid permanent damage. It said that if this was my first time reading this message to just let it restart, but if i had seen it more than once to check my disc space for drivers. Towards the end it begins mentioning BIOS updates and BIOS memory. To be honest, I'm way over my head, this is my first laptop, it runs on Windows Vista, and I have no idea what half of this stuff means anyways. But any help would really be appreciated. Thanks! I've tried to run Norton, but it never has time to finish a scan or anything.

BC AdBot (Login to Remove)

 


#2 rowal5555

rowal5555

    Just enough info to be armed & dangerous...


  • Members
  • 2,644 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:St Kilda, Dunedin. South Island. NZ
  • Local time:05:24 PM

Posted 26 August 2009 - 10:18 PM

There is a small program called BlueScreenView which I have found quite handy in tracking down the cause of a BSOD.

If you are able to get it installed, it may help you pinpoint the cause of the problem.

http://www.nirsoft.net/utils/blue_screen_view.html

Good luck.

rowal5555 (Rob )                                                             

Avid supporter of Bleeping Computer's
Team 38444

You can help find a cure


 


#3 euphaus

euphaus
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:24 AM

Posted 27 August 2009 - 05:13 PM

Thanks so much. The scan worked and I figured the cause of my crash was ntoskrnl.exe-- the problem is I'm not sure where to go from there. I looked it up online and it's essential to my startup system so I can't delete it. Any ideas?

#4 euphaus

euphaus
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:12:24 AM

Posted 27 August 2009 - 06:53 PM

Crash List


Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version
Mini082609-12.dmp 8/26/2009 10:23:00 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02214b81 fffffa60`021fc798 fffffa60`021fc170 ntoskrnl.exe ntoskrnl.exe+3c6b81
Mini082609-11.dmp 8/26/2009 10:11:17 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`021e1b81 fffffa60`021e7798 fffffa60`021e7170 mouclass.sys mouclass.sys+48e3430
Mini082609-10.dmp 8/26/2009 9:52:56 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`0227a3a1 fffffa60`021e77d8 fffffa60`021e71b0 adpu160m.sys adpu160m.sys+1502a10
Mini082609-09.dmp 8/26/2009 9:48:12 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022373aa fffffa60`021f57d8 fffffa60`021f51b0 adpu160m.sys adpu160m.sys+151ca10
Mini082609-08.dmp 8/26/2009 7:23:00 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022863b1 fffffa60`021d97d8 fffffa60`021d91b0 umbus.sys umbus.sys+141aa10
Mini082609-07.dmp 8/26/2009 7:16:54 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022863aa fffffa60`047437d8 fffffa60`047431b0 adpu160m.sys adpu160m.sys+3a5aa10
Mini082609-06.dmp 8/26/2009 7:10:49 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02226b81 fffffa60`021fc798 fffffa60`021fc170 ntoskrnl.exe ntoskrnl.exe+3c6b81
Mini082609-05.dmp 8/26/2009 6:54:24 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022373b1 fffffa60`021d27d8 fffffa60`021d21b0 adpu160m.sys adpu160m.sys+14f6a10
Mini082609-04.dmp 8/26/2009 4:57:18 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022763aa fffffa60`021fc7d8 fffffa60`021fc1b0 adpu160m.sys adpu160m.sys+152ca10
Mini082609-03.dmp 8/26/2009 4:51:27 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022843b1 fffffa60`021fc7d8 fffffa60`021fc1b0 adpu160m.sys adpu160m.sys+1527a10
Mini082609-02.dmp 8/26/2009 9:31:37 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`0228a3b1 fffffa60`048b57d8 fffffa60`048b51b0 adpu160m.sys adpu160m.sys+3bdfa10
Mini082609-01.dmp 8/26/2009 9:26:25 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`022923a1 fffffa60`021e77d8 fffffa60`021e71b0 adpu160m.sys adpu160m.sys+150da10

^^^^^^^Here's a summary of the basic information I got back if it helps

#5 rowal5555

rowal5555

    Just enough info to be armed & dangerous...


  • Members
  • 2,644 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:St Kilda, Dunedin. South Island. NZ
  • Local time:05:24 PM

Posted 28 August 2009 - 05:50 AM

All of those seem to Windows Operating System files so I would certainly not touch them.

At this stage, I would go to Control Panel/System and click on Device Manager. See if any of the items show a strange exclamation mark or question mark. If so, click on the + beside the item, highlight the device and right click/Update Driver.

Also, while you are in Control Panel/System, click on System Protection. In the System Properties box which comes up, click on ADVANCED and go down to Startup and Recovery/Settings. In System Failure, uncheck the Automatically Restart box. When the BSOD comes up now, you should be able to read and write down the error codes which you can check at the Microsoft site (or on Google) for solutions.

You can also check your Event Viewer to see what is causing the problem and click on the link provided for a possible solution. You will find Event Viewer in Control Panel/Administrative Tools.

That's about all I can think of at the moment. Good luck.

rowal5555 (Rob )                                                             

Avid supporter of Bleeping Computer's
Team 38444

You can help find a cure


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users