Solved BSOD on first boot, no keyboard/mouse control

[Ashrah]

Ever since I built this computer a few weeks ago, the first time I boot it up I'll get a stop error while starting Windows. Upon restarting, I have no keyboard or mouse control when Windows attempts to repair the problem. I've found that if I restart it enough, eventually keyboard/mouse control comes back, I can decline the system repair, and on the next reboot it boots normally. Subsequent restarts work fine, and even if I shut it down for several hours it will boot up fine. I've yet to boot normally on the first boot of the day , however.

I've run Prime95 blend test for several hours and had no errors.
Typically the bug check code is 0x000007e, and the affected driver is ntoskrnl.exe.

Any help is greatly appreciated.

 

[koolkat77]

Welcome to Seven Forums.

Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Sat Sep 21 23:15:19.788 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:06.584
BugCheck 1000007E, {ffffffffc0000005, fffff80002c92045, fffff88002ea4588, fffff88002ea3de0}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+1cd )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Fri Sep 20 05:40:08.878 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:08.675
BugCheck 1000007E, {ffffffffc0000005, fffff8800420bec0, fffff88003ec76b8, fffff88003ec6f10}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProfilePerformanceTick+728 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Fri Sep 20 05:38:05.729 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:53.525
BugCheck 24, {1904fb, fffff8800274e798, fffff8800274dff0, fffff880012e0de0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1a0 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Fri Sep 20 01:07:57.016 2013 (UTC + 6:00)
System Uptime: 0 days 0:06:24.812
BugCheck 24, {1904fb, fffff880033465d8, fffff88003345e30, fffff80002f3f3ae}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlTeardownPerStreamContexts+de )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Fri Sep 20 00:49:43.269 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:11.066
BugCheck A, {0, 2, 1, fffff80002c5867f}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Thu Sep 19 08:31:12.091 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:02.887
BugCheck 1000007E, {ffffffffc0000005, fffff80002cb58be, fffff880033a07d8, fffff880033a0030}
Probably caused by : memory_corruption ( nt!MiRemoveMappedView+19e )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

4. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

• Remove All MSI software.
  NTIOLib_X64.sys Thu Oct 25 16:27:58 2012 (5089142E)
  MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
  Driver Reference Table - NTIOLib_X64.sys

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.​

Let us know the results.

 

[Ashrah]

Thanks so much for the reply.

I did #4 and didn't find any violations after the 2nd pass, and I did a clean start up this morning. I got the same error however. After this happened, I reset the CMOS and it booted normally. I even had keyboard control at the bios boot screen. I'll leave it as is and try the same tomorrow. Does resetting the CMOS do anything that requires attention? All I did was change the boot option back to my SSD.

Thanks for the help!

 

[koolkat77]

Its OK, let the SSD boot first, and let us know how it is going after all the suggested actions are taken.

 

[Ashrah]

I tested each 8GB memory stick individually with Memtest86. One of them both caused a blue screen when loading Windows and had multiple errors. The other 3 seem fine and did not cause blue screens. I'm fairly certain this was the problem. Thanks for your help!

 

[koolkat77]

Thanks for letting us know
Do post if they happen again