BSOD, repaired computer for 9th time, still bsod

[sab123]

hi i am sab, i work in china, i moved her couple of years ago. i bought this computer like 1 years ago. it was working fine but from last few months i frequently get BSOD, i went to fix the computer for 9th times, still stucked with same problem. i guess its the language problem, i can't explain them what happens, there was a time my computer used to freeze and the only way out of it was to hit the power button, i already did clean installation for 10+ times, i still get BSOD. I thought it was a hardware problem but those guys said your hardware is fine, i too did memory diagnostic "No problems were found"


few days ago i did clean installation of windows 7 ultimate x86. After i finished installation i changed the startup and recovery settings- write debugging information - small memory dump (128 KB)
i have attached the dump file,my computer information, installed software so far.
can't wait to solve the problem.
( i am writing this after i did system restore (because i had BSOD) and updated my norton antivirus and restarted PC since after i used system restored it was out of dated )

 

[usasma]

You only have 2 updates since SP1 - most systems have between 75 and 120. Please visit Windows Updates and get all available updates.

The memory dumps suggest (but do not directly blame) your Norton, please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

I've seen one person suggest that memory settings were an issue when using "Auto" in the BIOS on the Asus M4 series of boards. The "fix" is to get the exact settings that the RAM manufacturer recommends - and use them in the BIOS.

Please update your chipset drivers using the latest version from nVidia: NVIDIA DRIVERS 15.49WHQL (they are very old, so there may not be any significant improvement by using them).

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

[font=lucida console]
ASACPI.sys              Wed Jul 15 23:28:28 2009 (4A5E9E5C)
AsIO.sys                Mon Aug 03 03:02:32 2009 (4A768B88)
BHDrvx86.sys            Wed May 16 21:41:23 2012 (4FB45743)
EraserUtilRebootDrv.sys Tue May 15 20:33:04 2012 (4FB2F5C0)
IDSvix86.sys            Fri Mar 09 16:55:47 2012 (4F5A7C63)
IDSvix86.sys            Thu May 24 20:08:07 2012 (4FBECD67)
Ironx86.SYS             Tue Apr 27 20:47:15 2010 (4BD78593)
NAVENG.SYS              Wed Apr 25 04:38:43 2012 (4F97B813)
NAVEX15.SYS             Wed Apr 25 04:36:43 2012 (4F97B79B)
SRTSP.SYS               Wed Feb 24 18:54:51 2010 (4B85BC4B)
SRTSPX.SYS              Wed Feb 24 18:55:07 2010 (4B85BC5B)
SYMDS.SYS               Mon Aug 17 19:34:39 2009 (4A89E90F)
SYMEFA.SYS              Wed Apr 21 17:46:52 2010 (4BCF724C)
SYMEVENT.SYS            Thu Aug 13 18:22:41 2009 (4A849231)
SYMTDIV.SYS             Tue May 04 00:29:10 2010 (4BDFA296)
amdxata.sys             Fri Mar 19 12:19:01 2010 (4BA3A3F5)
ccHPx86.sys             Fri Feb 05 15:57:22 2010 (4B6C8632)
dump_nvstor32.sys       Tue Aug 04 20:27:05 2009 (4A78D1D9)
dump_storport.sys       Sat Nov 20 04:50:47 2010 (4CE799F7)
eeCtrl.sys              Tue May 15 20:33:04 2012 (4FB2F5C0)
nvBridge.kmd            Sat Jul 31 09:41:25 2010 (4C542805)
nvhda32v.sys            Mon Jun 21 18:07:07 2010 (4C1FE28B)
nvlddmkm.sys            Sat Jul 31 09:45:06 2010 (4C5428E2)
nvmf6232.sys            Thu Jul 30 19:47:55 2009 (4A72312B)
nvstor.sys              Fri Mar 19 16:51:52 2010 (4BA3E3E8)
nvstor32.sys            Tue Aug 04 20:27:05 2009 (4A78D1D9)
viahduaa.sys            Mon Jan 11 05:02:43 2010 (4B4AF743)
[/font]

http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx86.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=IDSvix86.sys
http://www.carrona.org/drivers/driver.php?id=Ironx86.SYS
http://www.carrona.org/drivers/driver.php?id=NAVENG.SYS
http://www.carrona.org/drivers/driver.php?id=NAVEX15.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX.SYS
http://www.carrona.org/drivers/driver.php?id=SYMDS.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFA.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT.SYS
http://www.carrona.org/drivers/driver.php?id=SYMTDIV.SYS
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=ccHPx86.sys
http://www.carrona.org/drivers/driver.php?id=dump_nvstor32.sys
http://www.carrona.org/drivers/driver.php?id=dump_storport.sys
http://www.carrona.org/drivers/driver.php?id=eeCtrl.sys
http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd
http://www.carrona.org/drivers/driver.php?id=nvhda32v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvmf6232.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvstor32.sys
http://www.carrona.org/drivers/driver.php?id=viahduaa.sys

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062212-17487-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Fri Jun 22 01:09:59.915 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:34.398
BugCheck F4, {3, 88131580, 881316ec, 82e6ecf0}
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_e
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  0xF4_e_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000003 88131580 881316ec 82e6ecf0
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062212-23368-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Fri Jun 22 06:08:38.377 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:42.611
BugCheck 4E, {99, 3e53, 0, 3e5b}
Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  ccsvchst.exe
FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24
Bugcheck code 0000004E
Arguments 00000099 00003e53 00000000 00003e5b
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

 

[sab123]

Thanks a lot Mr. John for a quick reply

I did everything like you said,
1. updated my BIOS from 7.06 version to latest version 11.02
2. Updated my windows, however windows failed to update 2 updates
a. security update for windows 7 (KB2584146)
b. Update for windows 7 (KB2533552)
3. [clean]uninstalled Norton internet security and installed Microsoft security essentials
4. updated chipset drivers to latest version
5. Under Memory timming & voltage: i changed Memory clock mode to 535.8 MHz from AUTO. (i don't know the recommended value, the options provided were 400, 533, 667, 800) MHz however i haven't made any changes in DRAM timming mode (because i don't have any idea about what DCT 0 , DCT 1) & also haven't changed anything in Memory over voltage

During this process System freezed exactly 7 times and didn't have any BSOD , after i finished installing cheapset drivers, haven't seen any problem so far... & i did disk cleanup.
If something comes up i will let you know.
i have attached user manual. what next do you suggest me to do ? Thanks again.

computer got restarted itself and got freezed on windows logo also freezed couple of times after startup

 

[usasma]

This isn't uncommon. I think it's because you've partly fixed the BSOD issue - which leaves the other part to cause the freezes.

Now we try to track down the cause of the freezing (more difficult than a BSOD IMO).
Please post a fresh copy of the jcgriff2 reports so we can look for problems in the most recent event viewer entries.

 

[sab123]

I have attached startup and recovery setting screenshot, I don't know if i am doing it right.
Mr. john, today i didn't get BSOD that means dump files aren't created, and whatever i did with startup and recovery settings is that correct? my computer freezes and the only way out is to press POWER button (i don't have restart button).However, i have attached a fresh copy of the jcgriff2 reports as you asked for. And can you recommend me memory timming and voltage settings DRAM timming mode, memory clock mode..

 

[sab123]

i just had BSOD, i have attached jcgriff2 files created & computer keeps on freezing constantly - _-. Hope jcgriff2 files help to figure out the problems. X_X


i have attached another BSOD dump file, which i just had.. and also the image of file caused the BSOD

 

[usasma]

I can't help with the memory settings in the BIOS as I'm not a hardware tweaker, nor do I know very much about how memory works in the BIOS.
I can tell you that you'll be able to find the memory settings/timings/voltages at the memory manufacturer's website.
And, that there's got to be a guide in your motherboard manual for how to set the memory settings there.

I'd suggest contacting the support site of your motherboard manufacturer for more specific instructions (or check with an overclocking site as they have more experience with this).

You have only 51 updates since SP1 - most systems have 75 to 130 or so. Please check Windows Update again for more updates. Sometimes it takes several visits there to get all the updates.

I wonder about overheating due to some of the unexpected shutdowns. Please use a free temperature monitoring software to see if the system is overheating (I like the free version of: HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools )

Also, I wonder if there's a hard drive problem, as I saw paging errors on one of your hard drives. Please run this free hard drive diagnostic on ALL hard drives (internal and external).

 

[sab123]

Hi john,
1. I now have 150+ updates
2. I checked my hard drive using " Data Lifeguard Diagnostic for Windows " (which is for my hard drive) My hard drive didn't show any problem.
3. I used temperature monitoring software to see if the system is overheating. I think temperature are nomal. I have attached the report generated by HWinFO32
4. I still haven't got any reply from ASUS support site and forum for timings.

My computer was working fine, like it used to work 3-4 months ago but i just had BSOD and system freezes~ Freezing might be caused by BSOD error. After i had BSOD, i started getting random freeze

 

[usasma]

You can download your mobo manual from the Manual section here: ASUS - Motherboards- ASUS M4N68T-M LE
You'll need the settings/timings/voltages from the manufacturer of your memory (RAM).

Did you run the long/extended test of the Data Lifeguard Diagnostics? If not, then please run that - the short test only spot checks the drive.

I can't see any temperatures in the HWINFO report - do you recall what they were?

BSOD errors are caused by a number of factors - and any changes to the system can cause them to start popping up seemingly out of nowhere.