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

Mysterious Bluescreens


  • Please log in to reply
4 replies to this topic

#1 Ryan 3000

Ryan 3000

  • Members
  • 834 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland
  • Local time:09:41 AM

Posted 02 July 2010 - 01:31 PM

I'm having some strange errors on my custom computer, and I was hoping that you guys could shed some light on why they are happening. Here's the situation:
I am a gamer and I frequently take my computer to my friends' houses to play on LAN. After bringing it home, I sometimes don't set it back up for a week or two. So it's just sitting in a box at my house. After these long waits, the computer consistently bluescreens for a solid day after being reconnected. The next day, it works perfectly. Despite my efforts to checkdisk, run antivirus software, and other fixes, the computer will not be working until the second day of reconnection. As far as I can tell, these errors are caused by a super-cold boot. Has anyone had experience with similar problems?

msi P55M-GD45 mobo
evga GTS-250
g.skill 2GB DDR3-1600
OCZ 500w power supply
intel Core i5-750
..........edited to update stats.
all factory clocks.

Edited by Ryan 3000, 02 July 2010 - 01:32 PM.

No pessimist ever discovered the secrets of the stars, or sailed to an uncharted land.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,241 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:41 AM

Posted 02 July 2010 - 02:11 PM

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

#3 Ryan 3000

Ryan 3000
  • Topic Starter

  • Members
  • 834 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland
  • Local time:09:41 AM

Posted 03 July 2010 - 12:41 PM

I see that most of the bluescreens were caused by a single program. I'm not even close to being an expert, but I still think it's a hardware problem, and ntoskernel.exe may have been the bluescreen-thrower that caught the memory issues. But again I have no clue, that's why I'm here.
Here you are:
==================================================
Dump File		 : 070210-25381-01.dmp
Crash Time		: 7/2/2010 2:20:23 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code	: 0x0000001a
Parameter 1	   : 00000000`00041790
Parameter 2	   : fffffa80`01beb920
Parameter 3	   : 00000000`0000ffff
Parameter 4	   : 00000000`00000000
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.16539 (win7_gdr.100226-1909)
Processor		 : x64
Computer Name	 : 
Full Path		 : C:\Windows\Minidump\070210-25381-01.dmp
Processors Count  : 4
Major Version	 : 15
Minor Version	 : 7600
==================================================

==================================================
Dump File		 : 070110-32526-01.dmp
Crash Time		: 7/1/2010 11:41:22 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code	: 0x0000004e
Parameter 1	   : 00000000`00000099
Parameter 2	   : 00000000`001010a3
Parameter 3	   : 00000000`00000002
Parameter 4	   : 00000000`00102469
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.16539 (win7_gdr.100226-1909)
Processor		 : x64
Computer Name	 : 
Full Path		 : C:\Windows\Minidump\070110-32526-01.dmp
Processors Count  : 4
Major Version	 : 15
Minor Version	 : 7600
==================================================

==================================================
Dump File		 : 070110-34070-01.dmp
Crash Time		: 7/1/2010 10:02:59 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code	: 0x0000001a
Parameter 1	   : 00000000`00041201
Parameter 2	   : fffff683`ff7c9ed8
Parameter 3	   : cfb00001`0c9d4847
Parameter 4	   : fffffa80`0764cce0
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.16539 (win7_gdr.100226-1909)
Processor		 : x64
Computer Name	 : 
Full Path		 : C:\Windows\Minidump\070110-34070-01.dmp
Processors Count  : 4
Major Version	 : 15
Minor Version	 : 7600
==================================================

==================================================
Dump File		 : 070110-29187-01.dmp
Crash Time		: 7/1/2010 9:46:20 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code	: 0x0000004e
Parameter 1	   : 00000000`00000099
Parameter 2	   : 00000000`0009481f
Parameter 3	   : 00000000`00000003
Parameter 4	   : 00000000`00120720
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+1b52
File Description  : 
Product Name	  : 
Company		   : 
File Version	  : 
Processor		 : x64
Computer Name	 : 
Full Path		 : C:\Windows\Minidump\070110-29187-01.dmp
Processors Count  : 4
Major Version	 : 15
Minor Version	 : 7600
==================================================

Edited by Ryan 3000, 03 July 2010 - 12:43 PM.

No pessimist ever discovered the secrets of the stars, or sailed to an uncharted land.

#4 Ryan 3000

Ryan 3000
  • Topic Starter

  • Members
  • 834 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland
  • Local time:09:41 AM

Posted 05 July 2010 - 11:04 AM

I was told by a friend that possibly the CMOS battery is bad. Although this motherboard is less than six months old, the symptoms do seem reasonable: if the CMOS battery fails, some BIOS settings may be corrupted. Possibly this is happening to me, and something is getting overclocked without my knowledge. I'm not a hardcore overclocker, so I don't know any more than this. Can anyone comment on this possibility?
No pessimist ever discovered the secrets of the stars, or sailed to an uncharted land.

#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,241 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:41 AM

Posted 05 July 2010 - 11:09 AM

Well...a bad/failing CMOS battery typically (IME) can cause strange problems.

Costs less than $5 to replace and is easily done. If that doesn't solve...it won't hurt the system in any way.

If you put a new battery in, be sure to enter the BIOS and reset the date/time settings and save those...before booting into XP.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users