BSOD during Windows startup + Random Crashes

[XBABA]

Newbie here, I usually just looking at the forum to solve my pc problems or my friends'. I considered myself as someone who at least know generally what to do to fix pc problems. But for this case I give up and hope the good folks here could give me some clues.

There are 2 major issues here:

1. BSOD during Windows Startup
The problem
So after the loading screen loads up for some time (where you see the windows logo) it will then go straight to BSOD. This happens in random occurrence and happens like 70% of the time. Sometimes it won't go to windows at all, just keep on restarting for like 4 hours.
The error message is 0x101 "A clock interrupt was not received on a secondary processor..."
Some of the monitoring tools like hwmonitor sometimes also caused the same BSOD.
I think all the minidump files come from this error.

My solution
What I usually do is either let it reboot and pray that it goes through to windows
or I go through safe mode, uninstall the NVIDIA driver (using Display Driver Uninstaller), reboot to normal windows (it always reboot when the display driver is uninstalled), re-install the display driver and reboot. The 2nd method usually has increased chance of successfully going in to windows.

Possible root cause
- something wrong with GPU (bad copy), although I have used it around couple of months without problems whatsoever
- old PSU, unstable
- old processor

Possibly dismissed root cause
- This first happened when I started to try windows 8, thought that OS is the problem then I move back to windows 7. Unfortunately the problem still persists.
- I played around with flashing the bios of SLI mobo version to my non-SLI mobo. Have successfully re-flashed it back to the latest version of non-SLI. Problem still persists.
- There was time that disabling HT feature makes the error go away, but it doesn't really affect anything now. Possibly placebo effect.
- Have tried changing the TdrDelay to 8 secs. Doesn't help.

2. Random Crashes
The problem
During normal usage there are times that the pc just freeze, either with the loop sound like 'errrrr' or just freeze. This happens randomly, either when I had only used the PC for mere 1 hour or even doesn't even showed up after my streak of gaming along the weekend. So no temperature issues as just last weekend I managed to play all day. Only restart the PC once or twice when the PC was sluggish (of course reboot means facing the 1st problem). A rare occurrence will be the pc automatically reboot itself.

My solution
Hard restart

Possible root cause
- For me to be able to use all the 6 DIMM slots and run stable I have to bump the vcore to 1.63V. I've read that this is a common issue in X58 based chipset. There are possibilities that this stability issue still causing random freeze. (I used 2 different memory brand btw)
- Something to do with problem 1
- again unstable PSU
- again old processor
- fail HD

*Test done (early September):
- tried to run windows memory diagnostic (with the same current configuration + problems above) no error found
- tried prime95 in 2 occasions (small FFT for 3-4 hours, blend for 10+ hours) nothing happened
- Tried furmark overnight to see if GPU faulty...nothing

Appreciate if anyone have some clues of what broken here and if possible to fix.
I plan to upgrade to X99 in near future, however would like to keep the GPU if possible and sell the rest to 2nd hand market so it won't sit in my house useless (too many old PC already). However can't do the plan if there are still some issues with it.

 

[ICIT2LOL]

Hello and welcome XBABA mate am no expert and only see obvious bugcheck stuff and I cannot find anything that sticks out to me. But just for my curiosity this is your machine you are talking about ? If so and you can slip into safe mode run these if you haven't already

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html < use the /f and /r options in Option2 if necessary
Then have read of my ditty here

UsingHW Info PSU

Download HW Info and pick the right bit version - HWiNFO, HWiNFO32/64 -Download - (or copy andpaste this site into the search bar) If you do not need the running informationin the smaller right hand panel close it. In the left hand window click on the+ for the individual device groupings and they will open out to the variouscomponents.

Go on opening out further until you get to the device itself. click on it and itwill highlight. In the right hand window there will be a very detailed descriptionof that device as in brand, speeds model number etc etc These are very detailedand are just what is needed for searching for drivers etc.

To get the PSU volts you need to select the Sensor button circled in yellow inthe pic for PSU testing do the same and scroll down the readout as in my pic towhere it has Nuvoton = yours might be a different section name / title. Postback apic of that please.

If you want a more definitive test see this http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html but pleaseonly use a digital multimeter and not an analogue as they inject typically 9vinto a circuit to test and into a 3.3v or 5v rail - not a good idea!!see thepartial pic of the correct sort of meter in that tutorial. details if youscroll down that listing.

Now a good reference article is this
Voltage Rails - Power Supply 101: AReference Of Specifications it will explain in detail what thevoltages are and functions of the PSU

The section for the PSU rails has the reference for Vbatt - my pic shows my Ivy bridge Asus board and the section is titled Nuvoton.
I am only suggesting you look at the PSU rails as a matter of elimination because sometimes it can be the simplest thing and one components often overlooked is the PSU.

 

[Boozad]

I plan to upgrade to X99 in near future

I'd upgrade your Windows to a genuine copy first, your current installation is counterfeit. You have an ACER PID on a retail MSI motherboard.

  [FONT=&quot]Host Name:                 BLACKBOX[/FONT]
  [FONT=&quot]OS Name:                   Microsoft Windows 7 Ultimate [/FONT]
  [FONT=&quot]OS Version:                6.1.7601 Service Pack 1 Build 7601[/FONT]
  [FONT=&quot]OS Manufacturer:           Microsoft Corporation[/FONT]
  [FONT=&quot]OS Configuration:          Standalone Workstation[/FONT]
  [FONT=&quot]OS Build Type:             Multiprocessor Free[/FONT]
  [FONT=&quot]Registered Owner:          Vincent[/FONT]
  [FONT=&quot]Registered Organization:   [/FONT]
  [FONT=&quot]Product ID:                [COLOR=Red][B]00426-OEM-8992662-00006 ---> ACER PID
[/B][/COLOR][/FONT]
  [FONT=&quot]Original Install Date:     8/30/2014, 2:38:13 AM[/FONT]
  [FONT=&quot]System Boot Time:          10/21/2014, 10:55:15 PM[/FONT]
  [FONT=&quot]System Manufacturer:       MSI[/FONT]
  [FONT=&quot]System Model:              MS-7522[/FONT]
  [FONT=&quot]System Type:               x64-based PC[/FONT]
  [FONT=&quot]Processor(s):              1 Processor(s) Installed.[/FONT]
  [FONT=&quot]                           [01]: Intel64 Family 6 Model 26 Stepping 5 GenuineIntel ~1574 Mhz[/FONT]
  [FONT=&quot]BIOS Version:              American Megatrends Inc. V1.5, 4/20/2009[/FONT]

Counterfeit installations such as yours can contain heavily modified code that can cause the installation to behave in unexpected ways. Analysing BSODs and determining their causes on these sorts of installations is completely unreliable, and for this reason most analysts won't attempt it.

My recommendation is to install a genuine copy of Windows 7. This will minimise the problems you are experiencing and make subsequent diagnosis of BSODs far more reliable. Once you are running a genuine Windows 7 installation and are still experiencing BSODs, upload your new logs we will be happy to help you solve them.