Is that the only DMP file you have?
BTW these drivers need to be updated
Code:fffff880`07d6a000 fffff880`07d75000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`07eec000 fffff880`07ef2000 RTCore64 RTCore64.sys Wed May 25 02:39:12 2005 (42941D90) fffff880`07ef2000 fffff880`07eff000 GPU_Z GPU-Z.sys Mon Aug 06 10:47:00 2007 (46B73464)
hi ken,
i've got 3 other dmp files. the one that you have just analyzed was the one after i updated my bios. the other 3 that you see in this zip file were before i updated my bios.
hmm i've no idea where those drivers are from or what they do. but i'll find them and update them. Thanks ken! do keep me updated if you find more stuff in these dmp files.
thank you
Jereld
For test now, please remove Avast! even tho you have 0x124 hardware problem. This can only help sort things.
alright... i'll remove avast! and test out if my system crashes again. but that will have to wait till tomorrow.. its actually almost 4am where i am at. haha!
thanks alot guys! do keep me posted if you can think of anything else! i will check back again when i'm awake.
jereld
hi guys,
i've deleted avast and decided to see if anything i've done so far has solved the problem. i went into bad company 2 and 30mins later.. BSOD appears... =/
attached is the latest dmp file.
even though i ran furmark stability test last night, somehow i am still suspecting its a gfx card problem. can anybody verify from the dmp files i've uploaded so far please?
Thank you
Jereld
I am perplexed by this one. Your latest dump is still an Ox124 error. I reviewed your drivers and see that you have updated them.
Just by chance, I took a look at one of your drivers that I thought could possibly be a factor, GEARAspiWDM.sys. This driver has to do with Itunes and is notorious for causing BSOD's. Read this article, especially the sixth paragraph down.
You can try uninstalling Itunes and see if your BSOD's go away. Maybe ZigZag or Tews will see something I have missed and have additional insight.
Don't give up!
carl, i've uninstalled itunes as you have suggested... went back into BC2 to try it out and it crashed again after playing BC2 for about 45mins to an hour. once again i am suspecting the gfx card is causing the crashes except that i cannot be certain for sure cos like i mentioned, i ran furmark stability test for a good half hour without any problems.
i've read in some other thread that the ati driver caused some fella's system to go into BSOD as well... https://www.sevenforums.com/crashes-d...d-company.html
i'm gonna try that and see how it goes.. but in the meantime, here's the latest dmp file.
You guys have no idea how thankful for this forum and all your help!
Jereld
hi all,
unfortunately i'm back again... i cleaned out all my ati drivers and reinstalled the latest ones. the problem still persists...
here's the latest dmp file for your analysis.
i'm going mad man! rah!!
Jereld
hi all... sorry for spamming... but the crashes are still occuring.. this time i was running furmark stability test again. the last time i had it running for 20mins.. the temp stabilized at 75 deg (for about 15mins) and i closed it. this time i had it running longer and after 10min the temp stayed at 79deg +-1deg all the way until about the 40th minute. then came the BSOD.
this time the error log is different... it doesn't say 0x124 error.. its now says:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff80002c99831, 0xfffff88002f6b210, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-12308-01.
i've attached the dmp file as well... is this related in anyway to my previous 0x124 errors? or is it just simply me being an idiot and overheating my gpu?
all and any help is much much appreciated! THANK YOU!
Jereld
Good morning, Jereld. I am sure sorry the problem persists. The latest dump, the 3b, error is still a hardware error.
Let's try enabling Driver Verifier.Using Driver Verifier to identify issues with Drivers
Please follow these instructions in order to run it:
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/Windows 7 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 "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. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and 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.
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Quote