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

Seemingly random restarts/BSOD


  • Please log in to reply
19 replies to this topic

#1 lumbage

lumbage

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 19 March 2011 - 07:05 PM

Hey yall, I'm getting a consistant BSOD. At first I thought there might be a problem with the case/jumpers so I unplugged all but the main power, but still got BSOD. Then I thought it might somehow be related to SP1, so I uninstalled it, but still got BSOD. Perhaps there is a physical problem with the power supply or MOBO?

Here is the BluescreenView: Any thoughts/solutions/help would be very much appreciated.

Thanks!

==================================================
Dump File : 031911-31215-01.dmp
Crash Time : 3/19/2011 4:54:37 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000031
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02f64180
Parameter 4 : 00000000`00000002
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.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031911-31215-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 275,240
==================================================

==================================================
Dump File : 031711-16879-01.dmp
Crash Time : 3/17/2011 1:10:07 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000031
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02f64180
Parameter 4 : 00000000`00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031711-16879-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,296
==================================================

==================================================
Dump File : 031611-20233-01.dmp
Crash Time : 3/16/2011 11:40:39 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`028bfe73
Parameter 3 : fffff880`0550a970
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031611-20233-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,296
==================================================

==================================================
Dump File : 031411-19344-01.dmp
Crash Time : 3/14/2011 10:59:12 AM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000031
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`02fd5180
Parameter 4 : 00000000`00000003
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\031411-19344-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,296
==================================================

BC AdBot (Login to Remove)

 


#2 Edisnaeco

Edisnaeco

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere in the US
  • Local time:11:34 AM

Posted 19 March 2011 - 08:01 PM

Here is some info that may help:
http://support.microsoft.com/kb/958233
http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

#3 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 19 March 2011 - 08:06 PM

Thanks, but I'm past the "general inquiry" stage. I have been able to reproduce the BSOD with fresh format/installs and up to date drivers.

Anything more specific?

#4 Edisnaeco

Edisnaeco

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere in the US
  • Local time:11:34 AM

Posted 19 March 2011 - 08:18 PM

Hmmm.. it could be a possible heat issue. I would check if your fan is running and make sure your drive is not overheating. I am trying to find more info for you. But please make sure your computer is not over-heating. And let me know after that.

Edited by Edisnaeco, 19 March 2011 - 08:18 PM.


#5 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 20 March 2011 - 02:42 PM

The CPU fan and the case fan are both running nicely. Temperatures seem pretty good, but check out this screen shot from SIW. It says that TMPIN2 is 73 degrees c. What is that?

http://i.imgur.com/Ckf2K.png

After looking around on the intrawebs it looks like quite a few people get similar readings...

EDIT: The hard drive feels happy and has a reading of 28 degrees c.

Edited by lumbage, 20 March 2011 - 02:46 PM.


#6 Edisnaeco

Edisnaeco

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere in the US
  • Local time:11:34 AM

Posted 20 March 2011 - 08:00 PM

Well TMPIN2 at 73C is not good. Considering water boils at 100C. If that answers the question. Maybe try cooling the system a bit more? Put any fan on it. Or go to a cooler room? I am still looking for possible fixes. But it seems that there is none yet. It may not even be the temp but from what i see it must be.

I found this answer and it seems very helpful.
http://answers.yahoo.com/question/index?qid=1006052024880

It says this:

"Sometimes depending on how far it will boot and what version of windows it is. You can hit the F8 key as it is first starting up and get into safe mode. From there you can get into "My Computer" and right click on the "c" select the tools tab and do a defrag and schedule a disk check - check both boxes in disk check - one says "check for errors" the other one say "attempt to repair" This will fix it about 60% of the time!!! Good Luck!!!!"

Let me know how things go :)

Edited by hamluis, 22 March 2011 - 11:36 AM.
Removed unnecessary quote.


#7 fueL

fueL

  • Members
  • 67 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Philadelphia, PA
  • Local time:12:34 PM

Posted 20 March 2011 - 08:37 PM

Could you upload your .dmp files somewhere and link here? The files are located in C:\Windows\Minidump

#8 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 21 March 2011 - 01:58 AM

A abnormally high TMPIN2 reading seems to be very common. From what I can see, the consensus seems to be that the reading is wrong and nothing to worry about.

Thanks FueL, I'll post the .dmp files tomorrow.

Thanks Edisnaeco, fyi- I've run HD, memory, and general stress tests and no problems detected.

Edited by lumbage, 21 March 2011 - 02:00 AM.


#9 Edisnaeco

Edisnaeco

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Somewhere in the US
  • Local time:11:34 AM

Posted 21 March 2011 - 06:01 AM

Thanks Edisnaeco, fyi- I've run HD, memory, and general stress tests and no problems detected.


Oh, ok. Well i'll watch this topic for now and post if i think of anything else.. And your welcome.

#10 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 21 March 2011 - 07:11 PM

My dumps. My dumps my dumps my dumps. Check it out:

https://www.box.net/shared/2ktbygc22b

In all but one BSOD instance "WhoCrashed" says that it "appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time."

I highly doubt that it is a thermal issue as I have been in that case and it is a pretty cool place to hang out...

Could this be the MOBO drivers?

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 56,095 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:34 AM

Posted 22 March 2011 - 11:45 AM

<<Hey yall, I'm getting a consistant BSOD.>>

Well...exactly what are you doing when the system BSODs?

The fact that ntoskrnl.exe is pointed to...is not necessarily significant in identifying the problem.

You say "restarts"...what are you doing when they occur?

Louis

#12 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 22 March 2011 - 12:09 PM

Thanks Louis,

The only correlation that I have been able to find is the fact that the "shut-downs/restarts" only occur when someone is working on, or is physically nearby the computer. I left the computer unattended for 36 hours and there was no problem reported.

When someone is working with/nearby the computer it shuts down about twice a day; Sometimes they will be working on the computer, and other times they may be just sitting nearby doing other work.

This is pure lay-person speculation, but I wonder if this pattern suggests an electrical problem (a static electric field generated by the activity of a human which is affecting a faulty mobo component? This theory may be non-sense).

Edited by lumbage, 22 March 2011 - 12:11 PM.


#13 hamluis

hamluis

    Moderator


  • Moderator
  • 56,095 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:34 AM

Posted 23 March 2011 - 09:53 AM

Just speculation on my part...

When I see a number of errors involving ntoskrnl.exe and/or ntkrnlpa.exe and/or other suspects which are all over the map...I tend to try to eliminate malware from consideration first. Not that malware is the only item that can result in these types of errors...I just like to eliminate the prospect of such.

As for your suspicion that there is some relationship between human presence and errors...well, I don't believe in inventing possible causes for computer problems, there are enough around that make more sense, IMO.

Louis

#14 lumbage

lumbage
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:11:34 AM

Posted 23 March 2011 - 10:52 AM

If it's malware then it must have gotten itself to the bios; This problem has persisted even after twice formatting the hard drive and reinstalling the OS.

This problem has yet to occur without someone being nearby to observe it. OMG - Quantum glitch!!?!?!? How's THAT for speculation?

#15 hamluis

hamluis

    Moderator


  • Moderator
  • 56,095 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:34 AM

Posted 23 March 2011 - 07:02 PM

Well...ignoring the possibility of overheating and hardware and malware, for the moment...let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users