Spread the love! TechSpot Tech Gift Shortlist 2017

BSODs after installing XP SP2

By jcapas ยท 12 replies
Dec 5, 2005
  1. Hi
    I've just found this site and hope that someone can help me. I have read lots of threads and tried lots of different things, but still get random BSODs since upgrading to XP SP2. BSODs are one of three:
    I have upgrade my main drivers, except for the BIOS as am unsure if I have the exact correct one (Columbia II for Packard Bell iMedia 5094 Legend PC, P4 2.53, 512 RAM). I have done most of the suggestions posted, but do not know how to:
    - check the temperature of the CPU
    - downclock the ram
    - check bios setting about memory timing
    I have run memtest86 OK, run chkdsk OK.
    I have Macafee antivirus, Zone Alarm, and numerous other applications!
    If it is bad RAM, how come everything was fine before SP2? I know I could uninstall SP2, but I need it for certain applications (MS Pub 2003 being one).
    I would like to attach a zipped minidump but am unable to upload it (616kb - is it too large?)! I have ordered two new 512mb memory chips but am not sure if this is the problem. Could it be a device driver that SP2 doesnt like, but which one??????? Any help greatly appreciated.
  2. iss

    iss TechSpot Chancellor Posts: 1,994

    it is unclear from your post if installing XPSP2 was done on an existing XP installation or if the upgrade was over another Operating system or if it was a Clean reformat and install of XP SP2.
  3. jcapas

    jcapas TS Rookie Topic Starter

    Thanks for your quick response. I installed SP2 over an existing XP SP1 installation! I have attached some minidumps incase anyone can interpret them!

    Attached Files:

  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    I find two culprits. The first culprit is ZoneAlarm as I find the footprint of ZA at the stack trace of one of the minidump. Faulty ram is another culprit as one minidump is crashes with bugcheck 1A and one minidump is crashed with memory access fault.

    De-install ZA and install other firewall. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    Make sure that the CPU fan works properly
    2. Reseat the memory stick to another memory slot. Reseat video card as well.
    3. Downclock the ram. Check to default setting if you video card is overclocked.
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    6. Check the bios setting about memory timing and make sure that it is on
    For example : DIMM1 and DIMM2 do not have the same timing.
    DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
    DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
    DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
    7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
    8. Run chkdsk /r at command prompt
    9. Run 3DMark 2005 to test your video card
    10. Upgrade BIOS

    If it still crashes, diagnostic which memory stick is faulty
    Take out one memory stick. If windows does not crash, the removed memory stick is faulty.

    STACK_TEXT of one your minidumps
    b9b47a48 804e5451 e28646e0 e34c6128 806ee278 nt!KiInsertQueueApc+0x6c
    b9b47a68 8058bec4 82b309d8 0000010c e34c6128 nt!KeInsertQueueApc+0x40
    b9b47a98 8058abad e28646e0 00000000 00000004 nt!CmpPostNotify+0x17f
    b9b47acc 80578dff e2a7dea8 e102e008 00abb008 nt!CmpReportNotifyHelper+0xa8
    b9b47af4 80574a61 e2a7dea8 e2abb008 80001710 nt!CmpReportNotify+0x87
    b9b47b64 80574d11 e2a7dea8 b9b47bbc 00000004 nt!CmSetValueKey+0x24b
    b9b47bf8 f857f316 000004b4 00dffc94 00000000 nt!NtSetValueKey+0x228
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b9b47c70 f62090e5 000004b4 00dffc94 00000000 SSI+0x7316
    b9b47d44 804de7ec 000004b4 00dffc94 00000000 vsdatant+0x320e5 <--- ZoneAlarm
    b9b47d44 7c90eb94 000004b4 00dffc94 00000000 nt!KiFastCallEntry+0xf8
    00dffc6c 00000000 00000000 00000000 00000000 0x7c90eb94
  5. jcapas

    jcapas TS Rookie Topic Starter

    Thanks cpc2004,
    I installed 2 new 512MB memory chips 2 days ago, hoping this would solve my BSOD problem. However, it came again whilst copying some files! I attach the minidump for your kind investigation. I have disabled Zone Alarm and activated Windows Firewall. If Zone Alarm is the culprit, would you recommend just using the Windows Firewall (there is nothing on the Zone Alarm website about problems with SP2!). I have checked the CPU temperature which is 38oC, CPU Fan Speed is 1854RPM. I do not know how to downclock the ram or how to check if my video card is overclocked! BIOS settings for memory simply state "Memory size 1024MB, DDR266, so now sure about memory timing? How to I run 3DMark 2005 to test my video card? My BIOS Version is 8SIMLNF V2.OH, VGA BIOS V1.11.02 - I have not upgraded the BIOS - not sure if I would have the correct version (need to check with Packard Bell first!). Could it be a nvidia driver problem as I have read elsewhere that the latest driver is unstable?
    I would really appreciate your help, as these BSODs have been doing my head in for the last 3 weeks, ever since I installed XPSP2! Everything was fine before that! My memory chips are new, so should not be faulty! How can I pin point the exact culprit? Maybe, because my PC has crashed so many times during installations, defrag, other checks, my Windows has become corrupted??? One thing I have noticed is that it seems to crash when working hard, i.e. doing a virus or spyware check or copying lots of files.
    Here's hoping you can fine something from the last minidump, as I am paranoid that the PC will BSOD on me at any time! I have bought a new 80GB WD hard drive and will re-install everthing when I have some time, but if there is a faulty driver or program I am using, the same thing could happen again!!?? I am even considering buying a new PC which should at least come with all the correct device drivers for SP2 (I wish SP2 had never existed!).
    Thanks in advance for any help as I have wasted enough time on this and my husband is threatening to throw the PC out of the window!!!!
  6. jcapas

    jcapas TS Rookie Topic Starter

    Hi, it's me again. Just had another BSOD when I tried to open Outlook! I had left the PC on and unattended for 20 minutes, returned and it crashed when I clicked on the program icon. Here is the minidump. What is wrong?!!!!! Thanks in advance again!
  7. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    Your windows still crashes with memory corruption. Try reseat the ram or downclock the ram.

    Mini120505-03.dmp BugCheck 1A, {780, c0378900, 81f20b18, cd0a94d0}
    Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+3cd )

    Mini120705-01.dmp BugCheck 1A, {778, c033d800, 0, 0}
    Owning Process ff7643c0 Image: OUTLOOK.EXE
    Probably caused by : naiavf5x.sys ( naiavf5x+1d94 )
  8. jcapas

    jcapas TS Rookie Topic Starter

    Please can you tell me how to downclock the RAM?!!!
  9. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    It is BIOS setting. Reboot windows and press 'del' button and you will see the BIOS panel. Find the option to change clock frequency of the ram.
  10. jcapas

    jcapas TS Rookie Topic Starter

    Still having intermittent BSODs. It appears to be due to naiavf5x.sys (I am running V7.1.0). I attach a few minidumps and would be grateful if someone could confirm this. If naiavf5x.sys is the culprit, how do I get rid of it without losing my antivirus program? Thanks!
  11. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    The system may have mutiple culprit. Faulty ram is defintely one of the culprit. A lot of system crashes are at Anti-Virus Mini-Firewall Driver (McAfee)
    . As the crashes of Mini-Firewall Driver is inconsistent. They maybe caused by faulty ram or software error at Mini) Firewall.

    1. De-install McAfee mini firewall to. If the BSOD still occurs, it is hardware problem.
    2. Downclock the ram or replace the ram.

    Your debug report.
    Mini010106-01.dmp BugCheck 100000D1, {87c27efc, 2, 0, f336dbb7}
    Probably caused by : naiavf5x.sys ( naiavf5x+cbb7 )

    Mini010106-02.dmp BugCheck 100000D1, {87ba7bfc, 2, 0, f2e43bb7}
    Probably caused by : naiavf5x.sys ( naiavf5x+cbb7 )

    Mini120705-01.dmp BugCheck 1A, {778, c033d800, 0, 0}
    Probably caused by : naiavf5x.sys ( naiavf5x+1d94 )

    Mini120905-01.dmp BugCheck 10000050, {87d6c794, 0, 8056c02d, 0}
    Probably caused by : vsdatant.sys ( vsdatant+18c88 )

    Mini121005-01.dmp BugCheck 1000000A, {87d2b744, 2, 0, 804dc33a}
    Probably caused by : ntoskrnl.exe ( nt!KiTimerExpiration+6d )

    Mini121105-01.dmp BugCheck 1A, {780, c0368b00, 81e7c7a8, ce5614d6}
    Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+3cd )

    Mini121205-01.dmp BugCheck 1A, {781, c0379200, 0, e1872200}
    Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+3cd )

    Mini121605-01.dmp BugCheck 50, {c7b86000, 0, 0, 0} <- faulty ram
    Probably caused by : naiavf5x.sys ( naiavf5x+1d94 )

    Mini121705-01.dmp BugCheck A, {5, 2, 0, 804e39a7}
    Probably caused by : naiavf5x.sys ( naiavf5x+74a0 )

    Mini121805-01.dmp BugCheck 1000000A, {87b0129c, 2, 1, 804e48fe}
    Probably caused by : ntoskrnl.exe ( nt!KeReleaseMutant+6e )

    Mini122305-01.dmp BugCheck 10000050, {87baa8b0, 0, f30bd897, 0}
    Probably caused by : naiavf5x.sys ( naiavf5x+897 )
  12. mastervince

    mastervince TS Rookie


    i nid mPGA 478B drivers for IBM netvista pc i searched all day is there any hero among us to save my day?pliz
  13. LookinAround

    LookinAround Ex Tech Spotter Posts: 6,491   +184

Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...