Brand New Computer Blue Screen

[Shyam333]

Hi everyone and thank you in advance for your help.

I am a total newb when it comes to computers so please let me know if you need additional information.

This is a brand new pc which I received 10 days ago and I get the blue screen of death once a day with the following error code: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002fb40f3, 0xfffff880033698b8, 0xfffff88003369120). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072810-11796-01.

If I just restart windows normally (don't even have to use safe mode) everything works totally fine and I have no problems. If I turn off the computer and start it within 5 minutes I have no problems. I turn it off in the night and restart it the next day and then again I get this blue screen with the same problem. Once I turn the pc off and on (select start windows normally) there are no problems. Really not a big deal at this point but I am afraid it may get worse over time and if there is a real issue I might as well get it fixed now while it is under warranty. I was told to do a complete wipe but am hoping to avoid that if possible.

System information:

KB-152-101 BLACK XTREME GEAR MULTIMEDIA/ INTERNE
MO-115-101 BLACK XTREME GEAR OPTICAL USB GAMING 1
HD-504-115 30GB KINGSTON 2.5 IN SATA SSD MLC 1
HD-403-108 1TB SATA II 3.0 GB 7200RPM HD 1
RM-317-501 2GB DDR3 / 1600 MHZ MEMORY 3
FA-WATER-101 ASETEK 510LC 120MM WATERCOOLER 1
FA-104-116 CASE FAN 120 MM 1
MR-104-101 12-IN-ONE INTERNAL CARD READER 1
CD-144-101 BLACK LG 24X DVDRW 1
CD-143-301 BLACK 18X DVD-ROM SATA DRIVE 1
CS-426-101 BLACK X-CRUISER 2 MID NO POWER 1
MISC NO SLI/CROSSFIRE 1 0.00 0.00
MB-340-114 MSI X58 PRO-E SLI / CROSSFIRE MOTHERB 1 -10.00 -10.00
USB-202-103 MSI STAR-USB3 2-PORT USB 3.0 PCI-E EX 1 20.00 20.00
PS-126-109 XTREMEGEAR 950 WATT POWER SUPPLY 1 -20.00 -20.00
MISC ONBOARD 7.1 SOUND 1 0.00 0.00
VC-191-102 ATI HD 5850 PCI-E 16X 1 GB 1
SW-170-101 WINDOWS 7 HOME PREMIUM LICENSE
SW-170-102 WINDOWS 7 HOME PREMIUM COA 1
SW-170-103 WINDOWS 7 HOME PREMIUM 64-BIT 1
SW-152-120 JUST CAUSE 2 GAME 1
BOX1 SYSTEM BOX AND FOAM 1 0.00 0.00
NL-102-102 BLUE COLD CATHOD LIGHT 12 1
CU-197-207 INTEL i7-930 2.80GHZ 8M LGA 1366 RETA

I have also attached the files. If anyone can recommend a solution I would really appreciate it. If I should just live with this small error and not worry about it please let me know, my only fear is it getting worse once the warranty/return period is over.

Thanks for the help,

Shyam

 

[AndyBremner]

It may be some sort of error within Windows, are you able to do a fresh install of windows 7?

 

[ttran]

I don't see any minidump file in the one you just uploaded, make sure you set system to create minidump:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Do you use any program such as CCleaner? they may clean out your minidump

 

[Jonathan_King]

In addition to ttran's advice, make sure your graphics card drivers are updated. My info is sketchy, but I wonder if they are out of date.

Also I wonder if the Photo Screensaver is the cause. That would be the second time I have seen BSODs during it.

I suggest changing the screensaver and see what happens.

 

[Shyam333]

Andy - I tried a windows restore and it did not work. I am trying to avoid a complete wipe as I had already spend many hours loading everything back up to it. May have to do it as the system is still pretty new.

Ttran - I set up my system to create the minidumps now. I have not purchased any CCleaner yet. Will look into doing that later.

Jonathan - This happened even before I set up the photo screensaver but I will try changing that and report back. My graphics card drivers are up to date.

Thanks for the help everyone.

Shyam

 

[Shyam333]

Updated File

Tried the cc cleaner and cleaned the registry and files. Still got the BSOD today. When I restart my computer I keep getting the new BSOD. If I power off and on everything works totally fine. What an odd problem.

Anyways I should have a minidump file now and attaching it now.

Any help would be much appreciated.

Shyam

 

[ttran]

Yep the one you just upload contain a lot of information but there are no dump file.
follow this instruction instead:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

 

[Shyam333]

Ok attached the dump files per ttrans instructions.

Thank you,

Shyam

 

[ttran]

I suspect this might be hardware case, different stop code, different things were blamed.
First of all, please check your Ram:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 6 or 7 passes.

Then please do a http://www.sevenforums.com/tutorials/433-disk-check.html and hard drive diagnostic test (download the test from manufacture site): HD Diagnostic

System file was blamed as the cause, so I might want you to run system file check as wells:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BUGCHECK SUMMARY:

BugCheck 24, {1904fb, fffff88007917b28, fffff88007917390, fffff8800123e3cb}

Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupAllocation+eb )

Followup: MachineOwner
---------
PROCESS_NAME:  wmpnscfg.exe
BugCheck 3B, {c0000005, fffff9600010c801, fffff880022801f0, 0}

Probably caused by : win32k.sys ( win32k!GetKeyboardLayout+25 )

Followup: MachineOwner
---------
PROCESS_NAME:  svchost.exe
BugCheck 50, {ffffbc80089e6a70, 0, fffff880018b955e, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
PROCESS_NAME:  svchost.exe
BugCheck 1000007E, {ffffffffc0000005, fffff80002fb40f3, fffff880033698b8, fffff88003369120}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )

Followup: MachineOwner
---------
PROCESS_NAME:  System
BugCheck 1A, {5002, fffff780c0000000, 56a, 100056bfffffffe}

Probably caused by : CI.dll ( CI!SHATransform+236 )

Followup: MachineOwner
---------
PROCESS_NAME:  System
BugCheck 1A, {5002, fffff70001080000, 4ba, 10004abfffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f82 )

Followup: MachineOwner
---------
PROCESS_NAME:  drvinst.exe

 

[Shyam333]

Ran all three tests and no problems were found.

Any other suggestions.

thanks

Shyam

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

[font=lucida console]
BugCheck 3B, {c0000005, fffff96000099498, fffff88005d72b30, 0}
Probably caused by : win32k.sys ( win32k!ttfdQueryFont+28 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {5002, fffff780c0000000, 56a, 100056bfffffffe}
Probably caused by : CI.dll ( CI!SHATransform+236 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {5002, fffff70001080000, 4ba, 10004abfffffffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f82 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff88007917b28, fffff88007917390, fffff8800123e3cb}
Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupAllocation+eb )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff9600010c801, fffff880022801f0, 0}
Probably caused by : win32k.sys ( win32k!GetKeyboardLayout+25 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffbc80089e6a70, 0, fffff880018b955e, 7}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff80002fb40f3, fffff880033698b8, fffff88003369120}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41790, fffffa80012c7b00, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Shyam333]

Ok none of the solutions listed above had worked but I found out what was wrong.

It was a hardware issue in that one of the three RAM Chips was causing that error. Soon as I removed it I have not been having any other problems. Metest 86+ had 8 passes with no problems detected so it is not always accurate of specific enough.

Hope this helps someone in the future. Just try taking out one RAM chip one at a time and see if your problem resolves.

Shyam

 

[ttran]

Thanks for reporting back my friend! The DMP say it is memory corruption but may be memtestx86 didn't find it, that's not a big surprise, but at least you found the cause, perfect!

Let us know if you need more help in the future

Tuan