Windows 7 - Bluescreen/reboot when playing DayZ

shortbus9 · 22 Jul 2012

Ok thanks for the reply. I did a disk check and found no errors after it was finished I missed the full message but I remember it said something about it being a NTFS and file clean. As for updating drivers I tried Uniblue DriverScanner 2013 but didn't have the money to upgrade to have it fix them did a search for free scanners and found SlimDriver on CNET and I've never had a problem with programs I have downloaded from there before so I went with it. Slimdriver found the same drivers needed to be updated as Uniblue and Downloaded and installed them for FREE :)

After which I was able to Play ARMA 2 with the DayZ mod for around 2hrs befor it BSODed again. I so was hoping it had worked but no. I them attempted to play again and this time I wasn't even able to load into the server before it crashed again. That's when I did the disk check. I am included the latest dump file after the last crash, maybe you can tell if the drivers you suggested have been fixed. I also ran the DuplexSecure program again and it said the SPTD file was not present. I am at a loss to what could be causing this could it be the game itself? really hoping its not a hardware issue as I've heard RMAing a CPU is troublesome. also wouldn't the stress tests I performed have caused a BSOD if it was a Hardware problem? Thanks again for your time it is greatly appreciated.

JaidynM · 22 Jul 2012

If you play the game without the DayZ mod does your computer still crash? Does your computer crash at any other time?

Drivers

The following drivers need to be updated:

Code:

hugoio64.sys Sat Apr 5 01:39:14 2008 (47F63D92)
tmpB2BB.tmp Sat Jul 26 23:29:37 2008 (488B26C1)

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

shortbus9 · 22 Jul 2012

Yes if I play the game with out the mod this also causes a crash. I also bought a new game from steam today, Batman Arkum Asylum and this too caused a crash. I does not crash any other time I even played Diablo 3 again for around an hour with no crash. As for the drives you listed the hugoio.sys is associated with i-Menu which is a desktop app that allows me to change screen settings but I never use it so I just un installed it. The tmpB2BB.tmp I could not find anything about it any where. As for other driver updates I rescanned using Uniblue and it still list drivers out of date even though the Slim driver does not, I'm not sure what to make of that as I don't have the money to buy the full program nor could I figure out where to get the drivers myself and install them. Is there any free driver updater software you can recommend?
Could this be another problem with steams DRM and my processor? When I bought Portal 2 I was unable to play it due to a BIOS bug that requiered an update once I flashed the newest BIOS I was able to play Portal 2.
I am again including the latest dump file.Thanks again for your time.

JaidynM · 23 Jul 2012

You have a 0x101 error which may point to hardware, BIOS or driver. Read the following thread and see if any of it's fixes work.
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Drivers

Enable Driver Verifier. Enabling this should hopefully crash your system and then point to the faulty driver that is causing problems. However before you do, it is advised that you create a system restore point and backup first.
Driver Verifier - Enable and Disable

Software

Driver update software such as SlimDrivers or DriverMax are generally not recommended as they often cause problems. Rather than using such software to update your drivers I personally would update them manually.

Hardware

Test your RAM using Memtest86+. Let it run until 6-8 passes have completed or errors have been found.
RAM - Test with Memtest86+

shortbus9 · 23 Jul 2012

just wondering should I do a system restore to before I used slim driver? just to remove the drivers that were installed using it befor using Driver Verifier? also the post u directed me to about
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
has another post link about kernel dumps are needed to fully diagnose 0x101 codes. would you need a kernel dump then?

JaidynM · 24 Jul 2012

It should be fine, it's unlikely that Slim Drivers caused much if any damage in such a short time.

The kernel dumps are already in the files you provided me.

shortbus9 · 24 Jul 2012

Oh ok well I will try Driver Verifier once im home from work. Also if it crashes multiple times should I provide a dmp for every crash?

JaidynM · 25 Jul 2012

Yes, just run the tool found in this thread again and it will gather all of the dumps for you.

shortbus9 · 25 Jul 2012

Even though you said it wasn't necessary I did do a system retore to before I used the driver software. Also I downloaded and installed the latest drivers from Gigabytes website. So after enabling Driver Verifier it crash right away and wont start up. so here are the files from SF Diag Tool v4

shortbus9 · 25 Jul 2012

after investigating the first crash I tried updating with no luck, but I found out it is possible to run with out the driver so I deleted it and re ran verifier. here are the files for the next crash.