Periodic Blue Screen

[OPJM]

The error has been happening for the last two days. I've gotten three stops usually late at night. The stops happen usually during video, but I have been able to play videos otherwise without incident. I've been looking through various help instructions and found an unknown device with an outdated driver. I have my suspicions that it's my USB mouse, but I can't identify the device, so I'm not sure.

Here's the basic information:

Windows 7 Home Premium x64
Original system OS
OEM
System hardware is about 1 year 2 months
I've reinstalled the OS fairly recently, so it's about 2 months old.

 

[zigzag3143]

The error has been happening for the last two days. I've gotten three stops usually late at night. The stops happen usually during video, but I have been able to play videos otherwise without incident. I've been looking through various help instructions and found an unknown device with an outdated driver. I have my suspicions that it's my USB mouse, but I can't identify the device, so I'm not sure.

Here's the basic information:

Windows 7 Home Premium x64
Original system OS
OEM
System hardware is about 1 year 2 months
I've reinstalled the OS fairly recently, so it's about 2 months old.

No minidumps uploaded try this method.

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[OPJM]

I just looked. There hasn't been a minidump, at least where you said. Minidumps are created when blue screen happens, right? I'm not sure why it's not there. I've set the auto reset off. I can give the stop code and exactly what I was doing during each crash, but there is no minidump.

 

[ttran]

Hi OPJM!
Make sure you have set system to create minidump file correctly
Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Also, please run system file check:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Regard,

Tuan

 

[OPJM]

All right, I've made the change to Small Memory Dump. I don't have an option for 64kb, only 256kb. I'm not sure if there's a significant difference. One of my scheduled virus scans just started, so I'll reboot after that finishes. If I get another blue screen, I'll upload the minidump. If I don't, well, good.

Thanks for all your help so far.

 

[Jonathan_King]

I found this error:

Event[504]:
  Log Name: System
  Source: volsnap
  Date: 2011-01-27T16:32:33.178
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The shadow copies of volume C: were aborted because of an IO failure on volume C:.


Event[509]:
  Log Name: System
  Source: volsnap
  Date: 2011-01-27T16:31:28.072
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The shadow copies of volume C: were aborted because of an IO failure on volume C:.

Event[551]:
  Log Name: System
  Source: volsnap
  Date: 2011-01-27T16:14:42.876
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The shadow copies of volume C: were aborted because of an IO failure on volume C:.

Related to this:

Event[511]:
  Log Name: System
  Source: atapi
  Date: 2011-01-27T16:30:57.474
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.

Event[512]:
  Log Name: System
  Source: atapi
  Date: 2011-01-27T16:30:57.474
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.

Event[513]:
  Log Name: System
  Source: atapi
  Date: 2011-01-27T16:30:57.474
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: OnePixelMachine
  Description: 
The driver detected a controller error on \Device\Ide\IdePort0.

That looks like a hard drive problem; run the Short DST and Long DST SeaTools tests.

 

[OPJM]

Yeah, I've been worrying that it might be a hard disk problem. I ran Sea Tools for Windows, both tests you told me about. Failed both. Ran Check Disk with repair to see if that might help since I don't want to have to buy a new HDD if I don't have to, but it was no good. I've been trying to burn the Sea Tools for DOS to a CD to see if that might do any good, but after trying it with the burn that Windows can do and trying Alcohol 120% on both a DVD-R and a CD-R, I always get an Invalid Opcode. I know troubleshooting that problem isn't really in the purview of this forum.

Should I go ahead and replace my HDD? This computer is a little over a year old, so I think the HDD should still be in warranty. If not, I have one set up to order from Newegg.

Also, I haven't had a blue screen up until this point and that unknown device is suddenly gone. I'm not sure why.

 

[Jonathan_King]

Yes, backup your data and replace the drive ASAP. Running chkdsk will move the data off the bad sectors, but it cannot repair them. As time goes on, more and more sectors may fail, and eventually you will see data loss. Until that drive is replaced, keep running chkdsk /r every day or so.

Keep in mind, the drive is liable to completely go at any time; it may be months, or it may be tomorrow morning.

 

[OPJM]

All right. I've replaced the drive. The new one runs a little warm, but it seems to be doing fine so far. Thanks for all your help.

 

[Jonathan_King]

Great, sounds good so far!

Let us know how it's doing in a few days, maybe we can mark this as solved.