Win 7 BSOD 124 hardware issues?

[Widescope]

Hi.
I'm new to this forum but have been following various threads for over two months now.
I have a Packard Bell ixtreme machine using the EG43M board.
I bought it in November and since then have had BSOD crashes.

THe PC was brand new with Windows 7 home premium x64.
The processor is 2.50 gigahertz Intel Core2 Quad Q8300 with 6GB DDR2 ram.
I use two monitors through a NVidia GeForce GT220 card (1GB) - VGA


All of the mini dmps show 124 errors that I think is Hardware related although I've read on here that this could be a false positive.
I have patched the drivers up to the hilt for every piece of hardware on the machine.

Some times I can use the machine for less than half an hour before it crashes, other times longer. I don't play any games other than Football Manager 2010 and the only software I use is Office 2003 and the Adobe Web Premium suite.

Before each crash, the machine slows down, with the mouse pointer becoming more difficult to control. If I am using anything that has sound IE - a movie on youtube or on Football Manager there is a sound that is similar to a Fat Boy Slim remix (as if it is stuck). The crashes either happen when using IE, football manager, office or the adobe suite. I have set all of these to run in Windows XP service pack 3 compatibility mode incase the fact they are 32bit programmes makes a difference.

The weird thing, (perhaps just a coincidence - but pretty much every time) is that once it has crashed, if I restart I can generally use the machine until I close it down again without issue. Which is the main reason I'm persisting with this as it doesn't make sense.

I could take it back as it is in warranty (I've always built my own but had to get one quickly when my last beast broke due to some work I was doing at the time). I am however loathe to do so because I hate things like this beating me.

I thought at first it was AVG 9, which I uninstalled and replaced with AVG 8.5. I then replaced that with Estat Nod32. I read a post by COLDSHIVER and followed the majority of the suggestions made by himself and others on this forum.

These include;
Followed instructions to speed up windows 7 (general housekeeping to get rid of stuff like transparent boxes, switched off indexing, altered power plan to high performance etc)
I have ran various tests on the Ram modules (windows 7 memory diagnostic and Memtest86+) 10 passes - no errors.
Ran SFC /scannow - everything is fine.
Installed CPUID, everything looks ok.
I thought it was overheating so moved it to make sure vents are clear.
Installed SpeedFan and checked that the processors don't spike (get too hot) just before the crash. The Graphics card seems to run at a constant 68 to 71 degrees.
The four processors (core?) run between 28c and 40c which i don't think is too hot.

Is there something I am missing here? I have acquired a Geforce 8400 PCI card to try instead of the GT220 incase the card isn't actually compatitble but thats a major step down and I think that might void the warranty.

Is this one worth battling guys as although I can take it back I would rather sort it with your help?

Thanks
Steve

 

[usasma]

STOP 0x124 is a hardware error that's reported by your CPU to Windows. As such they don't contain much useful information for the average user.

A STOP 0x124 error is usually a hardware error (something's broken) or a compatibility issue. This link contains the most commonly recommended troubleshooting steps: [2-Int] Stop 0x124 - what it means and what to try

The dump files that I analyzed didn't have any significant info in the extra parameters, nor did it list any older drivers.

Please provide this info so we can have a deeper look into things: http://www.sevenforums.com/crash-lockup-debug-how/66913-sf-diagnostic-tool.html

 

[zigzag3143]

Hi.
I'm new to this forum but have been following various threads for over two months now.
I have a Packard Bell ixtreme machine using the EG43M board.
I bought it in November and since then have had BSOD crashes.

THe PC was brand new with Windows 7 home premium x64.
The processor is 2.50 gigahertz Intel Core2 Quad Q8300 with 6GB DDR2 ram.
I use two monitors through a NVidia GeForce GT220 card (1GB) - VGA


All of the mini dmps show 124 errors that I think is Hardware related although I've read on here that this could be a false positive.
I have patched the drivers up to the hilt for every piece of hardware on the machine.

Some times I can use the machine for less than half an hour before it crashes, other times longer. I don't play any games other than Football Manager 2010 and the only software I use is Office 2003 and the Adobe Web Premium suite.

Before each crash, the machine slows down, with the mouse pointer becoming more difficult to control. If I am using anything that has sound IE - a movie on youtube or on Football Manager there is a sound that is similar to a Fat Boy Slim remix (as if it is stuck). The crashes either happen when using IE, football manager, office or the adobe suite. I have set all of these to run in Windows XP service pack 3 compatibility mode incase the fact they are 32bit programmes makes a difference.

The weird thing, (perhaps just a coincidence - but pretty much every time) is that once it has crashed, if I restart I can generally use the machine until I close it down again without issue. Which is the main reason I'm persisting with this as it doesn't make sense.

I could take it back as it is in warranty (I've always built my own but had to get one quickly when my last beast broke due to some work I was doing at the time). I am however loathe to do so because I hate things like this beating me.

I thought at first it was AVG 9, which I uninstalled and replaced with AVG 8.5. I then replaced that with Estat Nod32. I read a post by COLDSHIVER and followed the majority of the suggestions made by himself and others on this forum.

These include;
Followed instructions to speed up windows 7 (general housekeeping to get rid of stuff like transparent boxes, switched off indexing, altered power plan to high performance etc)
I have ran various tests on the Ram modules (windows 7 memory diagnostic and Memtest86+) 10 passes - no errors.
Ran SFC /scannow - everything is fine.
Installed CPUID, everything looks ok.
I thought it was overheating so moved it to make sure vents are clear.
Installed SpeedFan and checked that the processors don't spike (get too hot) just before the crash. The Graphics card seems to run at a constant 68 to 71 degrees.
The four processors (core?) run between 28c and 40c which i don't think is too hot.

Is there something I am missing here? I have acquired a Geforce 8400 PCI card to try instead of the GT220 incase the card isn't actually compatitble but thats a major step down and I think that might void the warranty.

Is this one worth battling guys as although I can take it back I would rather sort it with your help?

Thanks
Steve

Steve have you by chance run a chkdsk on the HD. 0124 is hardware, but can manifest in HD, memory, USB, or anything.

Ken

 

[Widescope]

usasma - just trying that now
ken - scan disk hasn't found anything but I suppose I could try a full surface scan.

As an aside - I've somehow managed to associate my .dmp files with notepad - anyone know what I need to associate them with so I can open them....

 

[Widescope]

Ken have just ran chkdsk. Everything is fine.

usasma - the zip file is over 100mb don't think I'm going to be able to upload that..... any suggestions

Cheers
Steve

 

[Widescope]

just checked - the majority of the issue for uploading is with the MEMORY.DMP file which is over 390mb itself. Any point in uploading everything else or do you need that as well?

 

[Widescope]

I've uploaded the folder without the MEMORY.dmp.

Let me know if there is anything else I should try.

Thanks
Steve

 

[usasma]

As we already have some of the minidumps, I wouldn't expect that we'd need the MEMORY.dmp file. If you want to upload it (I don't think that it'll show anything new) you can zip it up and upload it to a free file hosting service (don't use rapidshare as most analysts here won't be able to access it).

This CLSID is the source of a lot of errors: {D3DCB472-7261-43CE-924B-0704BD730D5F}
And this APPID goes with it: {D3DCB472-7261-43CE-924B-0704BD730D5F}
This tracks down (on my system) to fdphost.exe - which is responsible for the Web Services Dynamic Discovery in Windows ( WS-Discovery - Wikipedia, the free encyclopedia ).

So, we're looking for something that's associated with that function. We'll also have to look for something that's not compatible with Windows 7 - which is more difficult.

Wandering through the results of the MSINFO32 report, I notice that there's 2 profiles on the system. Does this error happen in both profiles - or just in one? That'll eliminate the most of the stuff if it only involves one profile.

Beyond that, compare the discussion in the wikipedia link above with all of your installed programs to see what you can eliminate. Test the programs one at a time in order to determine what's at fault. This'll be anything that was installed on the computer by you (we presume that the system manufacturer only installed Win7 compatible applications.)

Here's a couple of links on how to open memory dump files:
http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html
http://www.carrona.org/dbgrpt.html

 

[myzr7]

[QUOTE

As an aside - I've somehow managed to associate my .dmp files with notepad - anyone know what I need to associate them with so I can open them....[/QUOTE]
This link can get you started to reading your own crash dumps if that was the intent of your aside. Good luck to you with your problem and welcome to SevenForums!
http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html

 

[Widescope]

This CLSID is the source of a lot of errors: {D3DCB472-7261-43CE-924B-0704BD730D5F}
And this APPID goes with it: {D3DCB472-7261-43CE-924B-0704BD730D5F}
This tracks down (on my system) to fdphost.exe - which is responsible for the Web Services Dynamic Discovery in Windows ( WS-Discovery - Wikipedia, the free encyclopedia ).

So, we're looking for something that's associated with that function. We'll also have to look for something that's not compatible with Windows 7 - which is more difficult.

Hi again. So you think it is a software issue rather than anything else. That's great if it is I can do something about that although I'm not sure what. You mention that the APPID on your system tracks down to fdphost.exe, can you tell me how I find the same thing on mine - where do I need to look.

Thanks for your help, its really appreciated.

Kind Regards
Steve

 

[Widescope]

As an aside - I've somehow managed to associate my .dmp files with notepad - anyone know what I need to associate them with so I can open them.
This link can get you started to reading your own crash dumps if that was the intent of your aside. Good luck to you with your problem and welcome to SevenForums!
http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html

Thanks myzr7. I'm new to windows 7 so I intend to stick around on the forums.

 

[Widescope]

Hi regarding the file association, I'm not sure I explained it right. I could open the minidump files but accidently associated notepad with them. I therefore don't think I need to download and install. I just wondered if there was some file I needed to associate it with so I can view them again. I apologise if I'm wrong as I'm new with Windows 7, just thought I'd better check before I go an create a DVD for it.

Cheers
Steve

 

[Widescope]

This CLSID is the source of a lot of errors: {D3DCB472-7261-43CE-924B-0704BD730D5F}
And this APPID goes with it: {D3DCB472-7261-43CE-924B-0704BD730D5F}
This tracks down (on my system) to fdphost.exe - which is responsible for the Web Services Dynamic Discovery in Windows ( WS-Discovery - Wikipedia, the free encyclopedia ).

Hi - fdpHost.exe is the same for mine. With the only other reference in the registry being WS-Discovery Provider Class. I have a few tools that start up when the machine comes on (have checked that also appears in the other profile which crashes also according to my son) so I'll start by switching those off. Thanks for helping me. If you have any other pointers just let me know.

Steve

 

[usasma]

File type association: http://www.sevenforums.com/tutorials/9154-default-programs-associate-file-type-protocol.html

Search for the CLSID in the registry. You should get references to the WS-Discovery Provider and to the FDPHost service.

Since it occurs in both profiles - then I'd suspect it's something that loads from the Public directory (see the Program stuff in the MSINFO32 report (it's in the last category). Or, it can be something like an add-on for a program like Internet Explorer or Firefox.

I suspect it's a software issue - but can't be sure. This could be an issue with a sound or network device also.

 

[Capt.Jack Sparrow]

Hi regarding the file association, I'm not sure I explained it right. I could open the minidump files but accidently associated notepad with them. I therefore don't think I need to download and install. I just wondered if there was some file I needed to associate it with so I can view them again. I apologise if I'm wrong as I'm new with Windows 7, just thought I'd better check before I go an create a DVD for it.

Cheers
Steve

To associate with WinDB its there in Debug theard anyway i'll post it here once more

Another entirely optional step that makes life easier. By registering WinDBG (the main debugger you'll want to use) as the default handler for common dump file types, you'll be able to double-click on a dump and have it open in WinDBG without having to go through the "File | Open..." menu operation every time. This registration needs to be performed from an elevated CMD prompt (run CMD as administrator):

C:\>cd debuggers - (Its the path where you have Installed WinDB it its under default location instead of cd debuggers type cd <path> )

C:\debuggers>windbg.exe -IA
​

In response, WinDBG should pop up a dialog box that says this:

---------------------------
WinDbg:6.11.0001.402 AMD64
---------------------------
WinDbg successfully registered file assocations for .DMP, .HDMP, .MDMP, .KDMP and .WEW.
---------------------------
OK
---------------------------
​

Hope this helps,
Captain