Vista Forums - View Single Post

**usasma** · 07-03-2009

Still STOP 0x124 errors - 2 occurred in Firefox, and the other 3 in games (online I presume). If that's the case, then this is likely to be network related.

And...there are components of both your wired and wireless network drivers that are old (from 2007). Also, there's a component of your storage controller drivers that's from 2007 also.

Here's the summary of the dump files:

Code:

Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 30 14:50:45.221 2009 (GMT-4)
System Uptime: 0 days 0:13:21.930
BugCheck 124, {0, fffffa8005af8030, b2000000, 115}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 30 15:04:34.030 2009 (GMT-4)
System Uptime: 0 days 0:13:15.716
BugCheck 124, {0, fffffa8005a88030, f2000000, 115}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Wed Jul  1 04:13:42.952 2009 (GMT-4)
System Uptime: 0 days 0:11:42.715
BugCheck 124, {0, fffffa8005ad3030, f2000000, 115}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jul  2 14:08:19.481 2009 (GMT-4)
System Uptime: 0 days 0:56:47.281
BugCheck 124, {0, fffffa8005a90030, b2000000, 115}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  RelicCOH.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Debug session time: Thu Jul  2 15:06:04.220 2009 (GMT-4)
System Uptime: 0 days 0:57:10.168
BugCheck 124, {0, fffffa8005a6f030, b2000008, 2000e0f}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe

And here's the drivers that I'm concerned about:

Quote:

nvstor.sys Wed Jun 06 16:34:00 2007
rtlprot.sys Fri Apr 20 05:16:48 2007
wg111v3.sys Fri Dec 28 01:59:29 2007

Personally I lean towards believing it's an incompatibility with your network drivers - but the storage drivers could also be doing this.

I'd suggest running Driver Verifier (some people question it's usefullness with STOP 0x124 errors - but I wonder if it can force the driver to misbehave in Windows, before it hits the CPU and causes the error).

Please read the following instructions carefully BEFORE you start. This procedure can make your system unbootable, so it's essential to prepare for that first.

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.

Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

Good luck!

07-03-2009	#18 (permalink)
usasma Vista Ultimate x64; Win 7 x64 and x32 596 posts	Re: BSoD recuuring problems please help Still STOP 0x124 errors - 2 occurred in Firefox, and the other 3 in games (online I presume). If that's the case, then this is likely to be network related. And...there are components of both your wired and wireless network drivers that are old (from 2007). Also, there's a component of your storage controller drivers that's from 2007 also. Here's the summary of the dump files: Code: Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Debug session time: Tue Jun 30 14:50:45.221 2009 (GMT-4) System Uptime: 0 days 0:13:21.930 BugCheck 124, {0, fffffa8005af8030, b2000000, 115} Probably caused by : hardware DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Debug session time: Tue Jun 30 15:04:34.030 2009 (GMT-4) System Uptime: 0 days 0:13:15.716 BugCheck 124, {0, fffffa8005a88030, f2000000, 115} Probably caused by : hardware DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Debug session time: Wed Jul 1 04:13:42.952 2009 (GMT-4) System Uptime: 0 days 0:11:42.715 BugCheck 124, {0, fffffa8005ad3030, f2000000, 115} Probably caused by : hardware DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: CoDWaWmp.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Debug session time: Thu Jul 2 14:08:19.481 2009 (GMT-4) System Uptime: 0 days 0:56:47.281 BugCheck 124, {0, fffffa8005a90030, b2000000, 115} Probably caused by : hardware DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: RelicCOH.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Debug session time: Thu Jul 2 15:06:04.220 2009 (GMT-4) System Uptime: 0 days 0:57:10.168 BugCheck 124, {0, fffffa8005a6f030, b2000008, 2000e0f} Probably caused by : hardware DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: CoDWaWmp.exe And here's the drivers that I'm concerned about: Quote: nvstor.sys Wed Jun 06 16:34:00 2007 rtlprot.sys Fri Apr 20 05:16:48 2007 wg111v3.sys Fri Dec 28 01:59:29 2007 Personally I lean towards believing it's an incompatibility with your network drivers - but the storage drivers could also be doing this. I'd suggest running Driver Verifier (some people question it's usefullness with STOP 0x124 errors - but I wonder if it can force the driver to misbehave in Windows, before it hits the CPU and causes the error). Please read the following instructions carefully BEFORE you start. This procedure can make your system unbootable, so it's essential to prepare for that first. Quote: Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier. So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature). Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Automatically select unsigned drivers" and click "Next" If no drivers show up, then select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post. If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. If that doesn't work, post back and we'll have to see about fixing the registry entry off-line. Good luck!
My System Specs