locked
Newly built computer blue screening! RRS feed

  • Question

  • I need some help with this as I don't know what is the real cause for all these blue screens but I'm thinking it might be the motherboard itself.  I'm receiving different errors each time with bug checks having 0x0000003b, 0x000000f4, 0x0000004e, 0x0000001a, and 0x00000024.  I've tried to use bluescreenview to look at the minidumps but it always points to ntoskrnl.exe as the culprit.
    Friday, August 20, 2010 7:47 AM

Answers

  • BugCheck 3B, {c0000005, fffff80002d66dcf, fffff880076e9070, 0}

    Probably caused by : memory_corruption

    CRITICAL_OBJECT_TERMINATION (f4)

    EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - Heap Corruption

    BugCheck 4E, {99, 2069d6, 0, 1ed3d6}

    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

    I've checked the last 3 dumps from August and I think the RAM is damaged.

    Please download memtest86+ [1], burn a new bootable CD from the ISO, reboot your PC and scan your RAM 4-5hours for errors.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Dale Qiao Thursday, August 26, 2010 4:17 AM
    Friday, August 20, 2010 3:25 PM

All replies

  • Any error logs reported as well in the Event viewer ? Under system / check with a filter for Critical.

     


    "Do it yourself, before you think someone else will" - Mani Babbar - 18.08.10
    Friday, August 20, 2010 8:05 AM
  • Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, August 20, 2010 1:06 PM
  • Hi Mani and Andre,

     

    Here is the link to the minidumps in my skydrive.  I hope I'm doing this correctly.  I've set this to share with everyone.

     

    http://cid-c2db261508d25780.office.live.com/browse.aspx/Minidump?uc=1

    Friday, August 20, 2010 2:36 PM
  • The only critical events that I see are event 41 task (63) which are system rebooting without cleanly shutting down first.
    Friday, August 20, 2010 2:40 PM
  • BugCheck 3B, {c0000005, fffff80002d66dcf, fffff880076e9070, 0}

    Probably caused by : memory_corruption

    CRITICAL_OBJECT_TERMINATION (f4)

    EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - Heap Corruption

    BugCheck 4E, {99, 2069d6, 0, 1ed3d6}

    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

    I've checked the last 3 dumps from August and I think the RAM is damaged.

    Please download memtest86+ [1], burn a new bootable CD from the ISO, reboot your PC and scan your RAM 4-5hours for errors.

    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Dale Qiao Thursday, August 26, 2010 4:17 AM
    Friday, August 20, 2010 3:25 PM
  • I ran memtest on all 4 sticks of ram in the computer and initially it showed errors.  I took out 2 sticks and ran those for about 5 hours and no problem was found.  I ran the other 2 sticks on slot 1&2 and no problem just like before.  I ran all 4 sticks on all 4 slots again and no problem.  Would it be possible that there is something wrong with the memory slot itself?
    Saturday, August 21, 2010 10:57 PM
  • Would it be possible that there is something wrong with the memory slot itself?
    yes, this is also possible.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, August 22, 2010 12:41 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

    Best Regards

    Dale Qiao
    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Thursday, August 26, 2010 4:17 AM
  • I'd like to thank everyone for the help.  The issue has not been resolved yet but I'm hoping that sending the motherboard in to MSI a second time will result in a new replacement.  At least if this happens it'll rule the motherboard out but I'm having my doubt that they'll actually give me a replacement.
    Thursday, August 26, 2010 4:38 AM