BSOD AND RESTART - error 0x00000124

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

i added them!

Code:

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	3496	8	200	1380	06/04/2012 13:45	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 07:21
avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	4176	8	200	1380	06/04/2012 13:45	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 07:21
avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	5296	8	200	1380	06/04/2012 13:50	12.0.0.1786	507.34 KB (519,520 bytes)	15/08/2011 07:21
avgemca.exe	c:\program files (x86)\avg\avg2012\avgemca.exe	3216	8	200	1380	06/04/2012 13:45	12.0.0.1854	1.52 MB (1,593,696 bytes)	10/10/2011 07:23
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2608	8	200	1380	06/04/2012 13:44	12.0.0.1855	4.23 MB (4,433,248 bytes)	12/10/2011 07:25
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	2476	8	200	1380	06/04/2012 13:45	12.0.0.1883	1.90 MB (1,987,424 bytes)	28/11/2011 01:19
avgrsa.exe	c:\program files (x86)\avg\avg2012\avgrsa.exe	3224	8	200	1380	06/04/2012 13:45	12.0.0.1806	1.31 MB (1,370,464 bytes)	08/09/2011 21:53
avgscana.exe	c:\program files (x86)\avg\avg2012\avgscana.exe	5480	8	200	1380	06/04/2012 13:50	12.0.0.1773	1.60 MB (1,681,248 bytes)	02/08/2011 07:08
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	4212	8	200	1380	06/04/2012 13:45	12.0.0.1912	2.30 MB (2,416,480 bytes)	24/01/2012 17:24
avgui.exe	c:\program files (x86)\avg\avg2012\avgui.exe	3436	8	200	1380	06/04/2012 13:50	12.0.0.1912	4.01 MB (4,200,800 bytes)	24/01/2012 17:24
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	2004	8	200	1380	06/04/2012 13:44	12.0.0.1773	188.26 KB (192,776 bytes)	02/08/2011 07:09
mbamgui.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamgui.exe	4396	8	200	1380	06/04/2012 13:45	Not Available	Not Available	Not Available
mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	1708	8	80	80	06/04/2012 13:47	Not Available	Not Available	Not Available
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	1008	8	200	1380	06/04/2012 13:44	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 18:21
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	3484	8	200	1380	06/04/2012 13:45	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 18:21
msseces.exe	c:\program files\microsoft security client\msseces.exe	3372	8	200	1380	06/04/2012 13:45	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 15:35
adawarebp.exe	c:\programdata\ad-aware browsing protection\adawarebp.exe	4456	8	200	1380	06/04/2012 13:45	1.0.1.31	193.39 KB (198,032 bytes)	21/10/2011 10:09
adaware.exe	c:\progra~2\ad-awa~1\adaware.exe	3456	8	200	1380	06/04/2012 13:45	10.0.185.3207	19.71 MB (20,670,304 bytes)	29/03/2012 12:43
fix-it_professional_9023.exe	c:\users\ivan\downloads\avanquest fix-it utilities  v9.0.2.3 pro+keygen\fix-it_professional_9023.exe	5332	8	200	1380	06/04/2012 14:00	9.0.2.3	101.36 MB (106,282,848 bytes)	06/04/2012 13:55

Remove the fix it utilities by avanquest Also remove adaware, AVG, and Malwarebytes trial/full version. Re-install Malwarebytes, but do not start the trial or full version; the standalone scanner is enough. Having multiple security programs does not provide more security but instead causes system files to be accessed at the same time by multiple protection suites and results in instability of the system.

The reason I suggest uninstalling avanquest...

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

When you are finished with the above, you will only have Microsoft Security Essentials and Malwarebytes standalone free scanner installed. That is what many of the gurus on here run on their systems.

Please send the new reports via the https://www.sevenforums.com/crashes-d...tructions.html

okay :)

Are you using CCleaner and/or Windows disk cleanup? They will usually delete the .dmp files needed for analysis...


I see that you are getting the 0x124 bugcheck in your event viewer logs, but without the .dmp files I cannot offer specific troubleshooting...


For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.

new dmp file

Same as before. Where are you with the steps given in the previous post? Any progress?