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 of death


  • Please log in to reply
4 replies to this topic

#1 yedrellow

yedrellow

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:26 AM

Posted 23 June 2010 - 07:49 AM

Over the past three days, my computer has started to get blue screens of death quite regularly. Before this there was no instances of BSODs. No obvious software changes have occurred that would induce this.

Edit: The operating system is Windows Vista Ultimate 64 bit.

Following the advice in similar threads:

Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`97f39521
Parameter 2 : 00000000`00000000
Parameter 3 : 07c316b0`d89c60ae
Parameter 4 : 00000000`00000101
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini062310-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini062210-01.dmp
Crash Time : 6/22/2010 9:18:02 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`024d4c7c
Parameter 3 : fffffa60`0cc2dba0
Parameter 4 : 00000000`00000000
Caused By Driver : usbaudio.sys
Caused By Address : usbaudio.sys+5003ba0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini062210-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini062110-01.dmp
Crash Time : 6/21/2010 10:29:32 AM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`97f3b738
Parameter 2 : 00000000`00000000
Parameter 3 : 39962de5`143373ac
Parameter 4 : 00000000`00000101
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini062110-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini061810-01.dmp
Crash Time : 6/18/2010 8:35:26 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000022
Parameter 2 : 00800000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+4a26
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\Mini061810-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
==================================================

Edited by yedrellow, 23 June 2010 - 08:19 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,246 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:26 AM

Posted 23 June 2010 - 12:13 PM

I would try uninstalling the graphics drivers...and then reinstalling same.

I would also try running the sfc /scannow command, in an effort to replace missing/damaged system files.

How To Use Sfc.exe To Repair System Files - http://www.bleepingcomputer.com/forums/t/43051/how-to-use-sfcexe-to-repair-system-files/

System manufacturer and model?

Louis

#3 yedrellow

yedrellow
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:26 AM

Posted 23 June 2010 - 10:47 PM

I would do the above, the only issue is that I am unable to find i386. I ran the scan anyway, it stated that it did not find anything. I removed and reinstalled my graphics drivers, no help.


The system was built by a local computer store rather than a major manufacturer, it's under warranty, but only for hardware issues (not software). I am unable to take it to them unless I determine that it's a hardware rather than software issue.

Would a system restore to about a month ago help?

#4 yedrellow

yedrellow
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:26 AM

Posted 28 June 2010 - 08:32 AM

Did a system restore, thought it was fixed, but out of the blue another BSOD occurred today. None of the above tips to help with the blue screen have worked.

#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,246 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:26 AM

Posted 28 June 2010 - 11:52 AM

The i386 folder isn't necessary if you are running sfc /scannow with an updated XP CD. Replacement files are pulled from the CD.

All of your BSODs point to system files, which doesn't necessarily mean anything...other than the fact that something is causing various system files to appear troublesome or damaged.

A repair install of would replace all system files, leaving data files and program files intact.

I'm not a Vista user, but I believe this may be useful: http://www.bleepingcomputer.com/tutorials/repair-windows-with-windows-startup-repair/.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users