Bsod

[ReptiPro]

I have been having bsod issues for about 2 weeks now and have tried everything to resolve them. The issues started when i installed my 2 new monitors and only occur when running 2 monitors from what i can tell.

I have since bought a new xfx ati radeon hd 4650 graphics card and installed it. Still getting the bsod. I have also run every memory test and updated every driver in the book. Tried every config i know of for the monitors.......this is wearing me out.

This is info the computer gives me

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800989A258
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\091610-22183-01.dmp
C:\Users\Baker\AppData\Local\Temp\WER-65598-0.sysdata.xml

And Here is what the Bluescreen says-

A Clock interrupt was not received on a secondary processor within the allotted time

I have attached a copy of the dmp file named above as well as a photo of the bluescreen. Any help in this matter would be greatly appreciated.

 

[usasma]

Most likely a hardware problem, with compatibility issues next most common.

2 different BSOD's - one's a STOP 0x124 and the other is a STOP 0x101
Info on troubleshooting them is here:
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://<a href="http://www.carrona....blank">http://www.carrona.org/dvrref.html</a>http://www.carrona.org/dvrref.html ).
Please pay particular attention to any dated 2008 or earlier:

000.fcl      Fri Sep 26 09:11:22 2008 - CyberLink FCL Driver - http://www.carrona.org/dvrref.html#000.fcl
adfs.SYS     Thu Jun 26 16:52:37 2008 - Adobe File System Driver - http://www.carrona.org/dvrref.html#adfs.SYS
SSPORT.sys   Thu Aug 11 19:07:32 2005 - Samsung printer driver - http://www.carrona.org/dvrref.html#SSPORT.sys
WinRing0x64.sys Sat Jul 26 09:29:37 2008 -    many different programs that center around the using of the WinRing   libraries - http://www.carrona.org/dvrref.html#WinRing0x64.sys

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 17 23:54:53.223 2010 (UTC - 4:00)
System Uptime: 0 days 2:40:30.425
BugCheck 101, {19, 0, fffff88002f64180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/FONT]

 

[ReptiPro]

I have updated or removed all the old drivers on my cpu, removed any old programs, and also uninstalled avg av and replaced with mse. I thought that the mse had solved the problem as the computer ran all day without an issue unit just a few min ago when i came back in the room the computer was at the welcome screen and then gave me the error message.

Any suggestions on what else to look at?

Also another thing i should mention is that whenever i get a bsod all of my desktop icons are moved back to where i had them a couple weeks ago except for newly added ones that are all just on the left side. Think this could be an explorer issue?

 

[ReptiPro]

More Info

I also stress tested my gpu with furmark and my cpu with prime95. No errors on each with both running about 4 hours each.

The highest recorded temp on my gpu was 76 c and cpu was 78 c.

I have just uninstalled a screensaver that gave me an error so we will wait and see if that helps.

 

[usasma]

Please post the information from this page:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
That way we can look at the reboot that occurred around 8:20 pm on the 20th (?1 hr off?)

 

[ReptiPro]

Update

Here are the docs you requested.

Thanks for the help.

 

[zigzag3143]

Here are the docs you requested.

Thanks for the help.

Reptipro

while we are waiting for USASMA, I just thought I would tell you about a driver that needs updating.

It is
SSPORT.SYS is related to Serial Solutions Driver for Windows 2000 / XP. Manufacturer: Brain Boxes Limited Brainboxes - Connect, Configure, Control Your RS232 and RS422/485 Serial Devices using bluetooth, PC card, ethernet, PCI, uPCI, USB and ExpressCard - Brainboxes - RS232 RS422/485 Serial Experts.. Dated 2005 I dont even know why it is on the computer.

If you dont need the associated software I would remove it.


Also

I would see if there is a newer version of tuneuputilities64, or remove it.

The DMP is hardware related and USAMSA can tell you what to try and what it means.

Ken J

 

[ReptiPro]

The ssport.sys file is being used by my samsung all in one laser printer.

I will update my tune up utilities and see if that helps. I updated my drivers for microsoft virtual wifi miniport adapter and have not had a crash since. Keeping my fingers crossed. That seemed to speed up my outlook email send receive as well as my network response. Maybe they were conflicting.

I get an error from tuneup utilities that the winring driver is not working correctly. How do i update that driveras i cannot find out what device is using it?

 

[usasma]

Here's 2 errors from the perfmon report:

The device, Hauppauge WinTV HVR-1800 (Model 78xxx, Combo ATSC/QAM), is disabled
The device, WinRing0_1_2_0, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved

Uninstall the Hauppauge software and remove the WinTV HVR-1800 card from the system.

Here's the location of the WinRing driver: C:\Users\Baker\AppData\Local\Microsoft\Windows Sidebar\Gadgets\IntelCoreSeries24.gadget\WinRing0x64.sys I'd suggest removing the IntelCoreSeries24.gadget

Remove the Samsung printer driver if you can't find an update for it. You can reinstall it after we finish troubleshooting your problems.

Remove TuneUpUtilities as zigzag3143 suggested.

I would suggest waiting for another BSOD - as the one's that you've uploaded aren't very helpful. They are STOP 0x124 and these are errors that the CPU passes to Windows. As such the information that they provide doesn't give us much detail. I suggest you have a look at these links:

Info on STOP 0x124: BSOD Index

Troubleshooting STOP 0x124: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 21:32:19.376 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:10.467
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`09865038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 19:04:04.660 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.862
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`09899038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 08:02:11.269 2010 (UTC - 4:00)
System Uptime: 0 days 9:09:20.471
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`098b2028 00000000`be000000 00000000`00800400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 19:53:56.872 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:13.074
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`086e08f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 15:20:58.568 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:07.770
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`09801038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 14:38:55.208 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.410
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`09942038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 12:06:13.387 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:13.589
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`086b18f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

 

[ReptiPro]

I have removed tune up utilities and cannot find an update for my printer. I will install it on the network tomorrow so that it is no longer on this machine. I have been meaning to do that anyways.

As far as the winring file i still cannot find it. I searched for the directory that you listed above and that directory did not exist. I have removed all gadgets in any way related to a performance monitor just in case but did not see that file in any of them.

Please let me know if there is somewhere else that it may be located as i suspect that is the problem.

I have also turned off my monitor sleep functions as somehow that seems to alleviate the bsods for the most part. Once the bsods cease i will enable that again and wait to see.

Thanks again,

Chris

Thanks

 

[usasma]

I've got a Samsung printer myself. You will still have the driver installed even if it's a network printer. Just leave it uninstalled for a couple of days while we troubleshoot this - then you can reinstall it without worrying.

Do you have the viewing of hidden and system files enabled in Explorer.exe? (Tools...Folder Options...View...Advanced settings) FYI - I don't have the directory either (in my copy of Win7), but mine is a clean install - not an upgrade from Vista.

Turning off power management will fix quite a few of these sort of errors - but that limits what you can do with your system. FYI - I had an Asus mobo that wouldn't go into sleep and wasn't able to fix it for almost a year. Finally I got a new motherboard and I can now use sleep and hibernation. Wow!!! Did I miss being able to use those features!

 

[ReptiPro]

I do have the hidden and system files shown but that entire directory is not there. I will uninstall that printer now and let you know if I run into anything else.

Is there a way that i can search for that winring. I have used all the search functions i know of and none showed it even when searching all of c:

 

[usasma]

Let's not worry about it now. If it continues to show up in the error reports, then we'll deal with it then.
Does it show up in Device Manager?

 

[ReptiPro]

No i have checked everything in device manager and it is not listed in the driver details for any device there.

When i run perfmon /report this is what it says-
Symptom:
Device is not present, not working properly, or does not have all of its drivers installed. Cause: A device has a configuration problem that prevents it from working properly. Details: The device, WinRing0_1_2_0, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_WINRING0_1_2_0\0000.

PlugAndPlay Device Configured Fail Count 244 1 PlugAndPlay devices. PlugAndPlay Device Status Fail Count 244 0 PlugAndPlay devices.

 

[ReptiPro]

another bsod

I just had another bsod that was identical to the first image i posted. This problem with this one is that it froze up during the memory dump.

I have uploaded the dmp files but the last one was from this morning. It seems that this last one was never generated.

 

[usasma]

The good news is that WinRing isn't loaded in this dump file.
The bad news is that it still doesn't tell us anything about the cause of this error.

I would suggest checking this link for suggestions: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Then I would check ALL of your hardware and software against this compatibility list: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

And if that doesn't isolate it, then try stripping the system down to see what causes the issue. Here's a generic sequence that I posted a while back: Hardware Troubleshooting Via System Stripdown

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 07:34:41.279 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:22.481
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`098a48f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[ReptiPro]

Ok so i have done everything under the sun that i can conjure up to fix this issue. I installed a new 750w powersupply, new cooling for the cpu and the case, as well as the new graphics driver. I also removed all the drivers that were mentioned and still getting the same bluescreen.

I have reinstalled the drivers as well as tune up utilities because they were needed and obviously not the issue.

I truly believe that the issue is the winring0 that is the problem but i am still unable to find the file. i deleted all the temp files and other references to any cpu monitors but could not find a trace of the intel core series gadget. I also cleaned the registry to see if there were any references there for it and none showed up.

Any other ideas?

I have a new asus rampage 3 motherboard coming in a day or two. Will see if that helps.

 

[ReptiPro]

Ok so i got the winring error to go away by reinstalling the sidebar gadget intelcoreseries 2.4 . Now my system does not report any errors. Will wait to see if that solved the problem. If so i will just leave it installed and contact the developer to let him know.