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

Random BSOD


  • Please log in to reply
11 replies to this topic

#1 cacophony

cacophony

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 07:07 PM

Today, after a power outage (no idea if this has to do with the problem) I've been getting random BSOD. I haven't recently changed hardware or installed any sort of program. Here are the reports from BlueScreenViewer:

==================================================
Dump File : 072710-21496-01.dmp
Crash Time : 7/27/2010 6:52:51 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`95c3551b
Parameter 2 : b3b7465e`e8402711
Parameter 3 : fffff800`030c1dc0
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+68900
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.20655 (win7_ldr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\072710-21496-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 072710-20732-01.dmp
Crash Time : 7/27/2010 4:53:36 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`964546a1
Parameter 2 : b3b7465e`e8c21897
Parameter 3 : fffff800`030c1480
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+68900
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.20655 (win7_ldr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\072710-20732-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 072710-30591-01.dmp
Crash Time : 7/27/2010 4:37:26 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`9662058f
Parameter 2 : b3b7465e`e8ded785
Parameter 3 : fffff800`030c1830
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.20655 (win7_ldr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\072710-30591-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================



I have run sfc/scannow, which was suggested in a google search but that has not done anything. Just said that CBS.log was corrupted, but I opened that up and it said it had been repaired (?). not sure if thats related to the BSOD though.

Any help would be greatly appreciated

Edited by cacophony, 27 July 2010 - 07:09 PM.


BC AdBot (Login to Remove)

 


#2 ectech1

ectech1

  • Members
  • 60 posts
  • OFFLINE
  •  
  • Local time:08:16 PM

Posted 27 July 2010 - 07:59 PM

Hi Cacophony,

What is the make & model of the machine?

#3 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:05:16 PM

Posted 27 July 2010 - 08:00 PM

Power outage, especially, if you don't have a good power surge protector may cause all kind of issues...

Try to run "sfc" again and when it's done, open CBS.log file delete all entries, except for those from a day, when you'll run "sfc", save the log as a new file and attach it to your next reply.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#4 cacophony

cacophony
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 08:19 PM

ok, I'm not sure if this is what you want but i didn't delete anything from the file because it all said it was from today... if it's not let me know

i dont know how to attach files here and its too big to post haha so..

http://www.sendspace.com/file/byjcd0


also, im using an intel i5, 4gb g.skill ram (2x2), windows 7

Edited by cacophony, 27 July 2010 - 08:20 PM.


#5 cacophony

cacophony
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 08:27 PM

it happened two more times and the errors seem to be different:

==================================================
Dump File : 072710-23680-01.dmp
Crash Time : 7/27/2010 8:04:29 PM
Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code : 0x0000004a
Parameter 1 : 00000000`7790034a
Parameter 2 : 00000000`00000001
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`07972ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+68900
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.20655 (win7_ldr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\072710-23680-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 072710-20295-01.dmp
Crash Time : 7/27/2010 7:46:30 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`96a1b6b9
Parameter 2 : b3b7465e`e91e88af
Parameter 3 : fffff800`030c1680
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+68900
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.20655 (win7_ldr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\072710-20295-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:05:16 PM

Posted 27 July 2010 - 08:36 PM

It looks like all repairs were successful.

Does BSOD happen when you're doing something in particular?

Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287 (or http://www.bleepingcomputer.com/forums/ind...ive+diagnostic)
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#7 cacophony

cacophony
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 08:50 PM

It just happens completely randomly. The past few times the only program I've had running was Firefox.


As for the HD, I ran a quick test and it passed. I'm running the extended test and it says it will take about an hour and a half. Hopefully I won't get BSOD in the middle of the scan though...

#8 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:05:16 PM

Posted 27 July 2010 - 08:54 PM

What are you using to test the drive?

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#9 cacophony

cacophony
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 08:57 PM

This: http://support.wdc.com/product/download.as...d=3&lang=en

#10 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:05:16 PM

Posted 27 July 2010 - 09:11 PM

OK then.
If it's interrupted with any BSOD, you can download .iso version, create bootable CD and boot your computer from it to run the test.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 


#11 cacophony

cacophony
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:07:16 PM

Posted 27 July 2010 - 10:57 PM

just finished and it passed..

any ideas for what else I could try?

thanks for the help by the way

#12 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,738 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:05:16 PM

Posted 27 July 2010 - 11:19 PM

You're welcome :huh:

I'd probably post in "Am I infected?" forum to see, if your computer is clean.

Another possible reason - RAM
If you want to....

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users