Immediate restart w/ dump files but no BSOD

[benbrockn]

Have I asked you previously if you have a Kingston Data Traveler plugged into your system?

Yes, Sorry, I use it to transfer files between systems. Sometimes It's plugged in, sometimes not. I accidently had it plugged in when the program was run to collect info.

 

[Boozad]

That's not a problem, it just looks like it was causing issues. Do you know if it's been plugged in when your system has shut down before?

 

[benbrockn]

That's not a problem, it just looks like it was causing issues. Do you know if it's been plugged in when your system has shut down before?

Sometimes yes, sometimes no

 

[Boozad]

Seeing as all of the hardware has been tested and we're exhausting all possibilities here I'm wondering how adverse you'd be to performing a clean install of Windows? This may sound drastic, but I'd show you how to run a Macrium image of your C: drive first so you could restore your PC to it's current state in around thirty minutes or so.

I'm proposing this to rule out any software or driver problems as nothing on that front is obviously apparent, so running a clean install of Windows for a couple of days is the only way I can think now to prove that it's definitely software related. It's not a hard process, and with Macrium you know you can be back to exactly where you are at the moment in a short time with no hassle.

Let me know how you feel about this. It's not as extreme as it sounds.

 

[benbrockn]

Seeing as all of the hardware has been tested and we're exhausting all possibilities here I'm wondering how adverse you'd be to performing a clean install of Windows? This may sound drastic, but I'd show you how to run a Macrium image of your C: drive first so you could restore your PC to it's current state in around thirty minutes or so.

I'm proposing this to rule out any software or driver problems as nothing on that front is obviously apparent, so running a clean install of Windows for a couple of days is the only way I can think now to prove that it's definitely software related. It's not a hard process, and with Macrium you know you can be back to exactly where you are at the moment in a short time with no hassle.

Let me know how you feel about this. It's not as extreme as it sounds.

I've never used Macrium but I'm very familiar with Clonezilla, how are the two compared?

 

[Boozad]

I've never used Clonezilla or heard from anyone who has to be honest, but I presume it would do what Macrium does. I'm advising Macrium here though as I can guarantee the results, with Clonezilla I can't so don't want to be responsible for something going awry. Have a read up on Macrium, it's simple to use and quick to pick up. Plus it's free. http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html

 

[benbrockn]

I've never used Clonezilla or heard from anyone who has to be honest, but I presume it would do what Macrium does. I'm advising Macrium here though as I can guarantee the results, with Clonezilla I can't so don't want to be responsible for something going awry. Have a read up on Macrium, it's simple to use and quick to pick up. Plus it's free. http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html

Yeah, sorry. I've been really busy lately and haven't had time to work on the rig. Eventually, i will get to the point where I can reinstall windows.

One thing to note though, my computer restarted while I was playing a game through Steam and when it booted up, it went into chkdsk and only found file system errors for my D:\Steam folders. Nothing was wrong with my C: drive. So I'm wondering if maybe Steam could be the issue? I doubt it, but if so, reinstalling Windows wouldn't help since Steam is on a different drive. Also, the way I installed Steam was to run the installer to create the program files, and then I copied my whole Steam folder from another computer to the path it created on my gaming rig. Maybe it could have a software error because it was originally installed on different hardware? Do you think that that might be the problem?

 

[Boozad]

It's possible, I wouldn't rule anything out at the moment. If that's the case I'd recommend making an image of your D: drive with Macrium then formatting it. Run the HDD checks on the D: drive to see if anything shows up or gets fixed, reinstall Steam then install a game or two and test.

 

[benbrockn]

Hey, I was going to tackle reinstalling Windows today. So I'll get back to you when I'm done.

Did your friend ever look at those voltages though? (This is the same image from an earlier post)

 

[Boozad]

The voltages look OK. The 12V is a little low but allowable. If you need any guidance reinstalling Windows have a look here http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

 

[benbrockn]

The voltages look OK. The 12V is a little low but allowable. If you need any guidance reinstalling Windows have a look here http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Thanks, I don't need help reinstalling Windows, but I might need help trying to use the Windows repair tools. I popped the Windows installation CD in, and was going to try the repair option first before I reinstalled it. I got to this screen and my operating system isn't listed, weird. It says to load drivers, but where do I load them from? And which ones? The motherboard or graphics card is the only drivers I think I had for this pc.

 

[Boozad]

That looks like it isn't seeing your hard drive if it's asking you to load drivers. I'd go straight for the clean install route.

 

[benbrockn]

So far so good, no restart yet, but seeing as it happened randomly in the previous install, I'm not sure how long I should wait until I can call it "solved".

 

[Boozad]

Give it as long as you like, the thread will still be here. It's good to hear everything seems stable so far, any problems just let us know straight away. We'll be here.

 

[andrew129260]

Just to add here, Make a list of any software you had installed before, and then slowly add each software back, until you experience an issue. That is what I would do, just a suggestion. It looks like you already wiped though.

 

[benbrockn]

I added programs back one by one, creating a restore point between each one. It seems fine so far. I only had one actual BSOD, it was when I started up Perfect Dark for the first time. After I rebooted, all was well, and was able to start up the game. Attached is a link to the MEMORY.dmp file found in the Windows folder (not in minidump). The file originally is 608MB to which I am unable to upload on these forums so that is why I posted a link instead, the link goes to a Ultra-compressed 7zip file that is only 83MB. Also attached is an easier-to-read html report from bluescreenview.

http://www.mediafire .com/download/4b48534yed6wea6/MEMORY.7z

 

[Boozad]

It's a Kernel memory dump, can you configure to record small memory dumps.

1. Open Advanced System Settings
2. Click on Settings in Startup & Recovery
3. Make sure both boxes indicated below are checked
4. In the dropdown box ensure you're set to record Small Memory Dumps

 

[benbrockn]

It's a Kernel memory dump, can you configure to record small memory dumps.

1. Open Advanced System Settings
2. Click on Settings in Startup & Recovery
3. Make sure both boxes indicated below are checked
4. In the dropdown box ensure you're set to record Small Memory Dumps

Originally, it was on the Small Memory Dump. Windows Update ran a few times, I think it might have reset it to the Kernel Memory Dump. I'll change it back.

(1) Other than the size, what is the difference between the two memory dumps? Is one more useful? Does the bigger one have more needed information?

(2) Also, I'm going to delete the link. Could the Kernel Memory Dump contain files/passwords/other private or vulnerable information?

 

[Boozad]

Kernel dumps contain a lot more information than mini dumps, but it's debatable whether they can provide the information needed to solve the issue. I for one am pretty much useless at reading Kernel dumps. They don't contain personal information, don't worry about that, they just contain tons of info about what's going on inside the kernel itself.

The next time you get a BSOD upload new logs, given that you're still getting them following a clean installation of Windows and your hardware has passed all of the diagnostic and stress tests I'm beginning to think we're narrowing it down to your PSU or motherboard.

 

[benbrockn]

The PSU or motherboard? I doubt it is the PSU though, the motherboard - it's possible, I haven't tested out the USB 3.0 headers since the clean install. But so far the original restarts and reports of "hardware failure" are no longer happening. This current BSOD read that it was a possible driver error, and it hasn't resurfaced yet. I think that it was a bad install of Windows and the current one is unrelated, just happenstance.