Random 0x101s, 0x7f, 0x124 errors on new machine

[p51douglas]

Hi, I am posting to seek help with my new rig. Everything is brand new and has the latest drivers- as far as I know. Windows Updates as well and latest BIOS. Attached are my logs. I cannot pinpoint why I keep getting mostly 0x101 BSODs.
I have run IBT, Prime95 blend, Driver Veriifier, and MemTest as well as the Windows memory diagnostics. No errors are being reported. I need expert help to analyze my system logs to see where the fault may lie.
Very appreciative!

 

[p51douglas]

More logs attached, specifically what was requested for these forums

 

[Tekno Venus]

Hi there, and welcome to Sysnative!!

I see you have followed the BSOD posting instructions from another forum. Whilst I will assist you with the files given, could you please follow our posting instructions here: BSOD Posting Instructions because they collect more info than the one you ran. Thanks!

Anyway, on with the analysis!

Problem/Known BSOD Cause Drivers

Both these drivers are known BSOD causes, please uninstall the related software. For Daemon Tools, please uninstall the software using Add/Remove Programs then, once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, I recommend using PowerISO

dtsoftbus01.sys Thu Jan 13 08:15:01 2011 (4D2EB485)
Daemon Tools driver
Possible BSOD issues in Win7
https://www.sysnative.com/drivers/driver.php?id=dtsoftbus01.sys

AiChargerPlus.sys Thu Apr 19 02:17:35 2012 (4F8F67AF)
Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013)
https://www.sysnative.com/drivers/driver.php?id=AiChargerPlus.sys
​

BSOD Analysis

We're looking at a lot of 0x101 bugcheck BSOD's here:

Bugcheck code 00000101 
Bugcheck code 0000007F 
Bugcheck code 00000101  
Bugcheck code 00000101 
Bugcheck code 00000101 
Bugcheck code 00000124  
Bugcheck code 00000101 
Bugcheck code 00000101 
Bugcheck code 00000101  
Bugcheck code 0000009C 
Bugcheck code 00000124 
Bugcheck code 00000101  
Bugcheck code 0000000A 
Bugcheck code 00000124 
Bugcheck code 00000101  
Bugcheck code 00000101 
Bugcheck code 00000101 
Bugcheck code 00000101  
Bugcheck code 00000101 
Bugcheck code 0000003B 
Bugcheck code 00000101

101's are normally caused by a CPU fault, although other hardware problems can cause them.

Start off by posting your hardware temps here. Take a screenshot of hardware monitor --> HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

I need a kernel dump from you to perform full analysis. Please navigate to C:\Windows\ and copy the MEMORY.DMP file to your desktop. Zip it up and then upload it to a file storage site (I recommend SkyDrive or Dropbox) and paste a link in your next post.

Regards,
Stephen

EDIT - I just saw your latest post. I'm am literally about to leave the house, I'll get back later.

 

[Vir Gnarus]

How long are you running each of these hardware tests? Memtest should be done at least 7 passes and Prime95 should run at least 7 hours.

101 bugchecks cannot be debugged without access to at least a kernel dump (MEMORY.DMP in Windows directory). Make sure your latest crash was a 0x101 bugcheck, then upload MEMORY.DMP to a 3rd party site (e.g Mirrorcreator.com). Make sure to zip first as they compress very well.

The crashdumps that weren't 0x101 bugchecks seemed to be caused commonly while running some process named ROG_Video Intro. Googling it shows up some kind of a screen saver. Sounds kinda funny to me TBH. Best play it safe by removing it.

You say you have latest driver updates, But I recommend you check again since some do appear outdated. Also, any software that came with your motherboard should be uninstalled, like the AiCharger. They are very buggy and have known to even produce BSODs that look like hardware malfunctions. Get rid of all of them. Any overclocking should be done straight on the BIOS, and any hardware monitoring should be done using a 3rd party software. Any other gimmicks - like "enhancing USB power" - should also be avoided. Also, if you haven't updated firmware on stuff like your SSD, you should do so ASAP.

In addition, be aware that OCZ drives are notorious for being very unstable and buggy. Firmware updates can fix a good bit of them, but majority are just pushed out of the plants with defects. I've had to work with a lot of people with defective OCZ drives far more than any other SSD. Keep that in mind when dealing with OCZ drives; you're getting them for raw speed, not reliability. If you want a reliable drive, look into Samsung, Intel, or Corsair. Keep away from Sandforce controller drives - of which your Vertex 3 is - and consider that MLC (multi-level cell) drives are more reliable than TLC (triple-level cell) drives, but also more expensive.

Oh, and it goes without saying that if you happen to have anything overclocked, reset to SAFE defaults on your motherboard. I've seen some mobos comes with normal defaults that are actually overclocked settings. Safe commonly reverts them to nominal levels.

 

[p51douglas]

Hello, attached is the screenie of the CPU idle temperatures.

 

[p51douglas]

I have run IBT multiple times at Standard Settings for different passes, ranging from 3-10 passes each time. I have run IBT once at Very High setting for 10 passes. CPU passed.
I have run Prime95 blend overnight so 8-9 hours. No errors reported though one core showed a max temp of 86. I have water cooling.
Driver Verifier has run for over 24 hours with no errors.
Windows Memory Diagnostic Tool ran for 5 passes at standard setting with no errors.
MemTest was one of the first tests I did. Its been a week and I do not recall how many passes it went but I let it run for about 3 hours.

I have removed Daemon Tools and completely uninstalled the AI Suite of which the ROG Theme and AI Charger were a part of. I am not sure what sptd.sys uninstaller is but I downloaded and let it do its thing. It asked for a system restart but I could see no message of what it actually did or did not do.

My OCZ drive is my boot drive. I have nothing else on it but small programs. I have updated the firmware on it as well as part of this new build. It has run successfully for me for the past 18 months or so.

Last but not least, I have Driver Genius 12 and after your post I re-scanned for driver updates. Nothing was available. I did update mobo BIOS straight from the Asus website. All others were done using Driver Genius.

 

[Vir Gnarus]

Please do not use 3rd party driver "update" software like Driver Genius. They have a habit of installing broken, incomplete, outdated or even completely incorrect drivers. The best and tried and true method of updating drivers is to just make a checklist of all your hardware and then go to each hardware vendor site one-by-one and install updates for em. There's been a number of times where we've actually had to fix the mess that 3rd party driver update software like Driver Genius have caused on people's PCs. I'm almost tempted to recommend that you just reinstall Windows and then start from scratch updating drivers the way they should be updated.

Btw, how new are each of your parts? You said in first post that your hardware is all brand new, but you said the OCZ drive has been in use for over a year and a half.

 

[p51douglas]

Haha okay you caught me there. Of this new setup, there are two things that are technically not new. The OCZ ssd and my 2TB Hitachi hdd which I salvaged from my old rig. The new parts are:
i7-3790x CPU, Corsair Vengeance Pro 2133 DDR3 32gb, 2nd ssd Samsung 830, Rampage IV Extreme mobo, Corsair H100 WC, Seagate 1250W PSU, and twin GTX 770s in SLI mode.

I am willing to completely reinstall Windows if necessary. SFC /scannow does mention irreparable errors found anyway. Hmmm I suppose I can run KillDisk on the OCZ boot drive instead of just Quick Format to be sure its clean and ready for another Windows installation. What do ya'll think?

 

[Vir Gnarus]

The errors from SFC /Scannow means that Windows has been corrupted somehow, and there's one of two possibilities: a bad Windows update or Windows installation, or a filesystem issue most likely caused by drive failure. I'm kinda leaning on the latter.

There's no need to exert more pressure on the OCZ boot drive with KillDisk. You can just do a quick format and that should be enough. I wouldn't cross my fingers on this though, as some of the bugchecks as well as the symptoms displayed are evidence this is quite possibly a hardware failure than a software one. And speaking of hardware, I noticed you didn't list drive tests in your list of hardware diagnostics. I recommend doing some basic short tests with Seatools and follow up with CrystalDiskInfo to check on the SMART data for each drive. You'll want to send us a screenshot of each drive output for it. Such apps aren't 100% definitive on finding a bad drive, but they wouldn't hurt either.