Tech Support Forum banner

Windows 7 x64bit BSOD

1999 Views 9 Replies 3 Participants Last post by  Jonathan_King
Windows 7 Home Premium x64

same as above
("upgrade disk" Used Windows XP Professional x64 to install, used disk clean up to remove old xp files)

Less than 1 year

~ 4 months ; Yes, I have re-installed a few times

AMD Phenom II x4 820 @2.8Ghz



Antec Earthwatts 650 watt

Hello all,
I've recently begun having infrequent BS'OD and have not been able to find a cause. The event viewer has issues displayed but, again, I've not been able to tell if said issues are causing the problems or simply a byproduct of user error.

The blue screens have shown no consistency, and do not happen frequently (though they do seem to be happening with increasing frequency).

I have run the latest version of memtest86 and found no problems.
Crystaldiskinfo, Chkdsk, and the Western Digital diagnostic tool shows no problems with my HDD.

Additional, possibly pertinent information:
I recently swapped nearly all system internals without reformatting and reinstalling my OS.

Items "upgraded"
CPU: Intel Core 2 Quad -> AMD Phenom II x4 820
Video: EVGA GTS 250 to ASUS GTX 560Ti (changed for upgrade not troubleshooting)

The reason for the switch was that, with the old cpu/mobo, I was getting frequent system hangs (system would become completely unresponsive, leaving no information to point to a cause). After trial and error I could still not find a solution so I opted to replace the system internals with something that was more cost conscious and provided a little future proofing.


See less See more
Not open for further replies.
1 - 10 of 10 Posts

Please run all three Prime95 tests: CPU - Stress Test with Prime95 - Windows 7 Forums

I found a string of 12,290 of these errors:
  Log Name: System
  Source: cdrom
  Date: 2011-03-30T19:39:02.765
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Obidion-Gate
The driver detected a controller error on \Device\CdRom0.
Were you trying to read a bad disc? If not, try removing the drive for the time being.

...Summary of the dumps:
[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 30 22:37:01.043 2011 (UTC - 4:00)
System Uptime: 0 days 2:15:07.307
Probably caused by : hardware ( nt!RtlpOwnerAcesPresent+b2 )
PROCESS_NAME:  explorer.exe
SystemProductName = System Product Name
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 30 18:28:56.737 2011 (UTC - 4:00)
System Uptime: 0 days 12:40:53.001
Probably caused by : memory_corruption ( nt!MiInPageSingleKernelStack+c8 )
FAILURE_BUCKET_ID:  X64_0x50_nt!MiInPageSingleKernelStack+c8
SystemProductName = System Product Name
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 29 21:53:30.209 2011 (UTC - 4:00)
System Uptime: 1 days 3:06:02.848
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+24a )
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+24a
SystemProductName = System Product Name
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Mar 28 10:20:11.244 2011 (UTC - 4:00)
System Uptime: 2 days 14:32:21.892
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+0 )
PROCESS_NAME:  steam.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+0
SystemProductName = System Product Name
See less See more
Thank you for the reply, I'll run prime95 while I'm at class (only 4 hours though).

As to the the drive, I can't recall but I'm fairly certain I haven't had a disk in the drive for all of the occurrences. I currently don't have a replacement for it, but I'll try to pick one up soon.

I'm possibly not interpreting the last section correctly; is this indicating that there's a problem with the OS?
Oh, another bit of information.

The blue-screens did not occur until I installed the latest version of MSI Afterburner (a graphics card control utility), while I did not overclock I did adjust fan speeds for gpu load to help reduce temperatures. The utility is technically designed for MSI but from everything I've read it's compatible of other manufacturer cards as well.

I'm not sure if it has anything to do with the BSOD's, but it was running in all instances and I haven't had any nmi's since the last reboot where I did not reinitialize it.
Hey there. Regarding MSI Afterburner, it might actually be the cause of your BSODs.
I used it recently to overclock my GPU(not an MSI one) and shortly afterwards, I got hit by a BSOD, so I thought Afterburner may have had something to do with it. I changed the clocks back to default and didn't use Afterburner again and had no more BSOD.

I realize you only changed the fan settings, but it's still related to Afterburner, so I suggest to get it back to it's default state (or use the nVidia control panel to change the settings) and remove Afterburner and see how it goes. Worth a try IMO.

Good Luck.
I second Mark's advice: if you can trace the start of a problem to a certain event, it's a good idea to try to revert.

As for my Dump Summaries, those are parts of the crash dumps that were created. They are usually more helpful to other BSOD analysts than the OP, but people often look through them.

You can see one dump blames hardware, the others point to system files. We disregard any dumps pointing to those, or rather, we often take clues that hardware is the cause.
I just got home from class and found that prime95 had no errors.

As to the MSI related comments, thank you for the feed back. I'm going to take the advice and refrain from using it, though I will miss the lower temps. If someone can suggest another utility for clock/fan control I'd appreciate it.

As to the BSOD related feedback, thank you again, I haven't found any failures in any of the tests I've run so I'm still not sure where to look, as mentioned in the op memtest came back clean, as did the disk checks, and I'm about to run Furmark to see if my graphics card has issues. Could the dvd-rw be the cause even if it isn't accessing anything?
Definitely, we do know that a bad drive can cause BSODs even it it's supposedly not being used. If can think of two likely reasons we'd see a string of 12,290 of these errors: trying to read a bad disc, and a bad drive.

Note that those errors occurred at around 7:40PM yesterday. Does that help you remember anything?
Actually, I believe I was writing some ISO's around that time, though I can't remember clearly. However, I don't remember getting a blue screen while doing it. Actually, I still haven't had one since I quit using the clock/fan utility. I'm going to keep doing what I've been doing for the next couple of days to make sure.

I would like to resolve these issues though. I don't know for certain that they're not related, but just to be on the safe side, is it kosher to continue troubleshooting them here? or should I start another post in a more appropriate area?
It's fine, we can resolve them here.

You didn't actually get a bluescreen at the time of those errors. We'll have to keep them in mind, and see if they happen again. If it only happened that one time, we might blame it on a bad CD, whatever.
1 - 10 of 10 Posts
Not open for further replies.