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
6 replies to this topic

#1 Chairmanyang

Chairmanyang

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:41 AM

Posted 26 October 2010 - 03:12 PM

I've been having this problem recently, have done a lot of research but cant find a clear cut solution to the problem. I get BSOD in random instances, there is no consistency to it whatsoever ( ex. once at startup, on youtube, idle, etc.) Seems like the more advanced tech guys shy away from these but I figured I post it and see if I can get a solution. The whole ntoskrnl.exe thing seems like it could be anything. I tried system restore, updating drivers, running diagnostic software ( especially memory as i've read thats a major concern). I dont overclock and havent installed anything since around july either. I did build this computer in February but have never had this issue before. Finally, i have monitored temps and voltages constantly since i built it and nothing is out of the ordinary. I only have 2 dumps as well because of the system restore. The others were 3b instead of 7f but i dont know if that makes any difference whatsoever.
==================================================
Dump File : 102610-16364-01.dmp
Crash Time : 10/26/2010 12:30:55 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`02ecde59
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\102610-16364-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 081710-15475-01.dmp
Crash Time : 8/17/2010 1:54:16 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0550b8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a587c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\081710-15475-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

Edited by hamluis, 27 October 2010 - 03:11 PM.
Moved from Win 7 forum to Am I Infected ~ Hamluis.


BC AdBot (Login to Remove)

 


#2 killerx525

killerx525

    Bleepin' Aussie


  • Members
  • 7,220 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Melbourne, Australia
  • Local time:08:41 PM

Posted 26 October 2010 - 03:52 PM

Have you tried SFC scan yet?

>Michael 
System1: CPU- Intel Core i7-5820K @ 4.4GHz, CPU Cooler- Noctua NH-D14, RAM- G.Skill Ripjaws 16GB Kit(4Gx4) DDR3 2133MHz, SSD/HDD- Samsung 850 EVO 250GB/Western Digital Caviar Black 1TB/Seagate Barracuada 3TB, GPU- 2x EVGA GTX980 Superclocked @1360/MHz1900MHz, Motherboard- Asus X99 Deluxe, Case- Custom Mac G5, PSU- EVGA P2-1000W, Soundcard- Realtek High Definition Audio, OS- Windows 10 Pro 64-Bit
Games: APB: Reloaded, Hours played: 3100+  System2: Late 2011 Macbook Pro 15inch   OFw63FY.png


#3 Chairmanyang

Chairmanyang
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:41 AM

Posted 26 October 2010 - 04:04 PM

No I haven't, not quite sure how safe it is to use nor do I even know how to use it. What exactly does it do and what are the risks in using it?

#4 pominator

pominator

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:41 AM

Posted 26 October 2010 - 05:02 PM

The command "sfc /scannow" (without quote) scan the integrity of all system files. If a problem is found, the corrupted file is automatically replaced with a good copy. The command has to be run in a command prompt with elevated privilege under Windows 7. Open start menu, type cmd, right click cmd.exe and run as admin. Run from there. More information can be found here.

#5 Chairmanyang

Chairmanyang
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:41 AM

Posted 26 October 2010 - 06:14 PM

i tried it but everything came out ok. i think it could be hardware related but am not sure how I could find out. I almost wish it would happen more often which would allow me to maybe pinpoint the problem.

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,614 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:02:41 AM

Posted 26 October 2010 - 10:10 PM

I'd start with creating new topic in "Am I Infected?" forum to make sure, your computer is clean.

My Website

p4433470.gif

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


 


#7 dodes

dodes

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:41 AM

Posted 30 October 2010 - 08:38 AM

In your original post,

Full Path : C:\Windows\Minidump\102610-16364-01.dmp
and
Full Path : C:\Windows\Minidump\081710-15475-01.dmp

are what we're interested in here. If there doesn't seem to be any consistency in regards to these BSOD's then we can try to find the culprit(s) by analyzing files your computer saves, or "dumps," when crashes like yours occur. These files, just like the file path suggests, are called "minidumps."

First, navigate to this page:
http://go.microsoft.com/fwlink/?LinkID=191420
and download the Windows 7 SDK. Install it on your computer (or another computer if your computer isn't stable enough).
Navigate through the installer until you reach Installation Options - you're interested in the Debugging Tools redistributable package.

Once it's installed, you want to run a program called "windbg.exe", which, under a default installation, should be located in:
x86: %programfiles%\Debugging Tools for Windows\
x64: %programfiles%\Debugging Tools for Windows (x64)\

When you open WinDbg, the first thing you'll need to do before you can analyze one of these minidump files is to point WinDbg to a location where it can read "symbol files", which for our purposes here are just files that contain important information WinDbg needs to be able to analyze the minidump.

Click on the File menu
Click on "Symbol File Path ..."
paste this into the Symbol File Path box and click OK:
srv*c:\symbols*http://msdl.microsoft.com/download/symbols

If you don't have internet access, navigate to this page on another computer:
www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
and download the symbol file package that corresponds to the affected operating system. Transfer the installer over to the computer you installed the Debugging Tools on and run the package. The default install path for the symbol files should be:
%windir%\symbols

If you downloaded and installed the Symbol File package instead, you'll need to point WinDbg to the above path.

Once WinDbg knows where to read symbol files, open up your minidump file and analyze it. These minidump files are saved in:
%systemroot%\minidump\

It's helpful to first open up an explorer window where the minidump files are saved so you can:
a.) see what you're dealing with (how many minidump files are in this folder)
b.) what they're dated (it helps to sort them by most recent)

Go back to WinDbg, click File > Open Crash Dump, and navigate to the directory where the minidump files are saved. Choose the most recent minidump available.

Wait for WinDbg to download/collect symbol files, and when it's ready enter:
!analyze -v
and press enter.

WinDbg will output an analysis of the minidump file in question.

You can copy and paste the output in WinDbg as a reply in this topic so we can analyze it for you. It This output may help us determine if your problem is malware related or not. It may be more helpful to analyze at least a few of these minidump files and upload their contents (but please don't go overboard with the amount of logs you post - I'm new at this forum and am currently not aware of any posting limits enforced on this site). If it looks to be malware related, get with a Malware Response Team member and they should be able to assist you.

Edited by dodes, 30 October 2010 - 10:04 AM.

Windows 7 Pro x64
Biostar TH55B-HD
WD Corsair Black 500GB | Samsung Spinpoint F3 1TB
G-Skill 2x2GB 1066 DDR3 SDRAM
NVIDIA GeForce GT 240




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users