BSOD on W7 PRO 64

zigzag3143 · 13 Jun 2010

pilotleston said:

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. https://www.sevenforums.com/crash-loc...-what-try.html

Meanwhile I will do the dmp

Ken

JMH · 13 Jun 2010

pilotleston said:

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 · 13 Jun 2010

zigzag3143 said:

If indeed it is a 124 bugcheck it is always hardware. use these instructions to find out what it means and what to try. https://www.sevenforums.com/crash-loc...-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 · 13 Jun 2010

JMH said:

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 · 13 Jun 2010

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 · 13 Jun 2010

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 · 13 Jun 2010

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 · 13 Jun 2010

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 · 13 Jun 2010

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

pilotleston · 13 Jun 2010

I will run the tests and let you know.

Thanks!