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

BSOD at first startup (cold start?)


  • Please log in to reply
2 replies to this topic

#1 mrbjorklund

mrbjorklund

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:06:05 AM

Posted 01 November 2010 - 12:15 PM

Hello again.

Been a few good months and now Ive stumbled upon another BSOD error.

Every day when I boot my computer I get a BSOD after windows have booted up, when I restart it never happens again.

The error i get is a MEMORY_MANAGEMENT, and Ive checked for bad RAM:s but memtest comes up with 0 error after several hours.


Whats the right way to go at this problem to find a solution, so far only a minor nusiance but it means something is wrong?

Best regards Mr B

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:05:05 AM

Posted 01 November 2010 - 12:16 PM

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

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

Compliments of Broni

#3 mrbjorklund

mrbjorklund
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:06:05 AM

Posted 01 November 2010 - 05:40 PM

Hello and thanks for replying cryptodan.

Here is the text from BlueScreenView:
==================================================
Dump File : 110110-13041-01.dmp
Crash Time : 11/1/2010 5:34:55 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041287
Parameter 2 : 00000000`00000030
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+b3d89
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\110110-13041-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 102910-13275-01.dmp
Crash Time : 10/29/2010 3:05:35 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000401
Parameter 2 : fffff6fb`80000890
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
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\102910-13275-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 102710-12168-01.dmp
Crash Time : 10/27/2010 4:29:54 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0163fef0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
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\102710-12168-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 102610-18813-01.dmp
Crash Time : 10/26/2010 4:39:56 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff780`c0000000
Parameter 3 : 00000000`00000c80
Parameter 4 : 00000c82`00001901
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-18813-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================


I´ve googled about it some and alot of people think it might be some kind of frequency/power in the bios that isn´t set correctly but I´ve checked with my limited knowledge and rams, cpu etc all seem to be on the "default" values.


Edit:
I´ve searched a bit both on theese forums and others and the bug checkcode 0x0000001a is in all BSOD:s an people claim it´s mostly likely a RAM issue somehow, I´ll do a new memcheck tonight and check result.

Another option would be to only have 1 stick of RAM in at the time and rule out 1 perhaps. Though I´d have to check what how long it must power of for a "cold boot" to happen first.

I´ve read up even more and everything points to faulty RAMs in one way or the other. I´ll doublecheck settings in bios to see that they get enough voltage per default as it might be a problem, not sure if I want to go up a notch as some say might solve it. Wish I had 2 other stick to try out with :huh:


Best regards Mr B

Edited by mrbjorklund, 02 November 2010 - 10:28 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users