BSOD on W7 PRO 64

[pilotleston]

Hi, since last night I started getting BSODs on my computer.
LAst night I left the computer running the daily antivirus scan (ESET NOD32 4.2.40.0) and also Jdownloader was getting some files. When I got up today I found the computer had rebooted (was at the welcome screen). After that, it started showing BSODs, mainly when I use Chrome (last version) and, apparently, in relation to Flash content.

The error is of a 0x124 type (I managed to take a couple of pictures of the BSODs).

I zipped the Minidump content and attached it here.

Computer details are in my profile.

 

[ttran]

The result suggest this is hardware issue. I recommend to check to HD, it can be any parts of your computer, please see this article on your bugcheck:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI01.901\061210-20748-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50
Debug session time: Sat Jun 12 08:11:25.014 2010 (UTC - 7:00)
System Uptime: 0 days 0:03:17.044
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004e20028, be000000, 200119}
Probably caused by : hardware
Followup: MachineOwner
---------

 

[pilotleston]

Hi ttran, thanks for your time.

I am glad to tell you that you were right. The secondary HD seems to be the problem. I unplugged it and everything works well now.

What do you recommend? It was connected with one of those old S-ATA cables that didn't have a lock to keep it tight (contrary to the main HD which has a new S-ATA cable). Can the disk be rescued?


UPDATE: it wasn't solved.

 

[usasma]

You'll have to run a diagnostic on the hard drive to see if it's able to be used.
I'd first suggest another cable for it - even if it doesn't lock (I don't have locks on any of mine).

Then use this link to test the hard drive: HD Diagnostic (read the details at the link)
If it passes, then try this:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

 

[pilotleston]

Unfortunately it has just given a BSOD again.... (without the secondary HD plugged-in).

I am attaching the .dmp file that has been created. Can anybody tell me if it is of the same characteristics?

 

[usasma]

I am running the memory dump file right now.
Please run the above diagnostics on all hard drives.

 

[usasma]

It's another STOP 0x124 as ttran has said. Please review the info at the link that ttran provided.
Please check your system for compatibility (both hardware devices and software programs). You can check using this link: Windows 7 Compatibility: Software Programs and Hardware Devices: Find Updates, Drivers, and Downloads

Here's a list of the loaded 3rd party drivers - I would definitely check them to ensure that the version that you have is compatible:

[FONT=lucida console]fffff880`00ea4000 fffff880`00eaf000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff960`008e0000 fffff960`00941000   ATMFD    ATMFD.DLL    Thu May 27 00:11:31 2010 (4BFDF0F3)
fffff880`04246000 fffff880`0428f000   e1k62x64 e1k62x64.sys Thu Dec 10 12:37:53 2009 (4B2131F1)
fffff880`04632000 fffff880`0471a000   eamonm   eamonm.sys   Wed Mar 24 15:18:28 2010 (4BAA6584)
fffff880`01800000 fffff880`01825000   ehdrv    ehdrv.sys    Wed Mar 24 15:19:13 2010 (4BAA65B1)
fffff880`06671000 fffff880`06692000   epfwwfpr epfwwfpr.sys Wed Mar 24 15:13:05 2010 (4BAA6441)
fffff880`042c4000 fffff880`042d1000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff880`0486c000 fffff880`04880000   LHidFilt LHidFilt.Sys Tue Nov 10 06:46:17 2009 (4AF95289)
fffff880`0489b000 fffff880`048af000   LMouFilt LMouFilt.Sys Tue Nov 10 06:46:23 2009 (4AF9528F)
fffff880`10b51000 fffff880`10b52180   nvBridge nvBridge.kmd Fri Apr 16 16:14:52 2010 (4BC8C53C)
fffff880`0fe11000 fffff880`10b50800   nvlddmkm nvlddmkm.sys Fri Apr 16 16:38:16 2010 (4BC8CAB8)
fffff880`04c4b000 fffff880`04df8d80   RTKVHD64 RTKVHD64.sys Mon Apr 27 07:22:45 2009 (49F59585)
fffff880`06d69000 fffff880`06d7a000   usbaapl64 usbaapl64.sys Mon Oct 05 15:29:55 2009 (4ACA4933)
fffff880`06d7a000 fffff880`06d8b000   WinUsb   WinUsb.sys   Mon Jul 13 20:06:28 2009 (4A5BCC04)
[/FONT]

 

[pilotleston]

Thank you, I will get going.

 

[pilotleston]

I haven't been able to complete a long HD test yet as it gives a BSOD before finishing. I guess I should use a DOS HD test software version.

Any thought on how to check for each driver and how?

 

[pilotleston]

I have checked the HD with the original software in DOS version (WD LifeGuard) after burning it in a CD rom. It said that the disc is OK, without any problem (after a 2 hour test).

Then I tried the "CHKDSK /R /F" as stated above, but it instantly says "Volume is clean" (after rebooting) and does not give any log in the wininit item (the date of the wininit entry is from a couple of weeks ago).

Is that the right way to do it in W7 PRO 64? I have just started another test going to the HD properties and asking to do an error-check which was programmed for the next restart. It is being done now (I am wrtiting from another computer).

 

[zigzag3143]

Hi, since last night I started getting BSODs on my computer.
LAst night I left the computer running the daily antivirus scan (ESET NOD32 4.2.40.0) and also Jdownloader was getting some files. When I got up today I found the computer had rebooted (was at the welcome screen). After that, it started showing BSODs, mainly when I use Chrome (last version) and, apparently, in relation to Flash content.

The error is of a 0x124 type (I managed to take a couple of pictures of the BSODs).

I zipped the Minidump content and attached it here.

Computer details are in my profile.

If indeed it is a 124 bugcheck it is always hardware. use these instructions to find out what it means and what to try. http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Meanwhile I will do the dmp

Ken

 

[JMH]

I have checked the HD with the original software in DOS version (WD LifeGuard) after burning it in a CD rom. It said that the disc is OK, without any problem (after a 2 hour test).

Then I tried the "CHKDSK /R /F" as stated above, but it instantly says "Volume is clean" (after rebooting) and does not give any log in the wininit item (the date of the wininit entry is from a couple of weeks ago).

Is that the right way to do it in W7 PRO 64? I have just started another test going to the HD properties and asking to do an error-check which was programmed for the next restart. It is being done now (I am wrtiting from another computer).

pilotleston Hello and welcome

I wonder if the original DOS software might not have installed a driver on the Hard drive and Windows 7 may not be able to use it or identify it.


Can you tell us more about the software and what it does?

Thank you in advance

Jan

 

[pilotleston]

If indeed it is a 124 bugcheck it is always hardware. use these instructions to find out what it means and what to try. http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Meanwhile I will do the dmp

Ken

Hi Ken, some of the guys already decoded the dmp. I am finishing checkin the HD (primary, the secondary has been unplugged and remained like that since then).

Can you add anything else to the problem? Next step, if the HD is alright (it seems it is), would be checking the RAM with MDSCHED or Memtest86, can both these be used in my OS?

I really don't have any extra components to exchange to test processor and or RAM, I only can try one RAM DIMM at a time (I have a 2-unit kit).

 

[pilotleston]

pilotleston Hello and welcome

I wonder if the original DOS software might not have installed a driver on the Hard drive and Windows 7 may not be able to use it or identify it.


Can You tell us more about the software and what it does?

Thank you in advance

Jan

Hello Jan, if you are asking about the behaviour after typing "CHKDSK /R /F", it schedules the check but as soon as it appears to start the check (after rebooting) it says: "Volume is clean".

The check I scheduled in the HD properties is not the same than the CHKDSK?

 

[pilotleston]

The check was arriving at the middle of stage 5 of 5 when it gave a BSOD!

Does it indicate something? I thought that those tests were done "outside" the Windows enviroment.

 

[pilotleston]

Well guys, I decided to test a fresh install on a new HD (a 250 GB Maxtor I have around). I put the Windows 7 DVD and just after choosing the regional configuration and language for the install it gave a BSOD with the 124 code!

What do you suggest? It is obviosly to soft/driver/HD related.

Computer is almost new, 1 month old, assembled to my specs on a shop.

 

[Jonathan_King]

Let's try a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

 

[pilotleston]

Hi Jonathan, I haven't done that yet, but what I did was take out of the motherboard each of the DIMMs at a time and the problems persists (actually I put each on socket 0 from chanel A).

Do you think it is worth doing the test? I think the only possible cause is that BOTH DIMMs are wrong (in case it is the RAM).

 

[Jonathan_King]

Could be a timing issue as well. We'll see I guess.

 

[pilotleston]

I will run the tests and let you know.

Thanks!