The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Need HELP- Random BSOD- Tried Everything

    Discussion in 'HP' started by Uxion, Jul 29, 2008.

  1. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    Hey guys, I've been getting a BSoD at random times and I have tried every possible thing to fix it with no avail. I ran Memtest 86 and my ram came out okay. I also updated all my drivers. What could be causing this?
     
  2. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    DO you remember what error code it showed..??
    Try a System restore....
     
  3. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    I've tried everything, From reformatting my computer to restore points. absolutely no luck.
     
  4. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    Any idea about the error code shown on the BSOD..??
    something like 0x00000000
    Check the Event Viewer for the BSODs....and disable the auto-restart feature for the BSOD..!!
     
  5. Vladk1000

    Vladk1000 Notebook Consultant

    Reputations:
    154
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    30
    Are you sure it's not overheating?
     
  6. Hep!

    Hep! sees beauty in everything

    Reputations:
    1,806
    Messages:
    5,921
    Likes Received:
    1
    Trophy Points:
    206
    Run a hard drive test with your manufacturer's testing tool, or use Gateway GWScan to see if the hard drive is having problems. As angad said, get the error code. If it's happening at random times it might also be different codes.

    The fact that you've reformatted means it is not a software problem, but a hardware one.
     
  7. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    I am absolutely sure my laptop is not overheating and I have already tried scanning the hard drive. Is there anything else I can do? I have the Minidump file but no idea how to read it.
     
  8. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    Did you check it through Event Viewer..??


    - download and install WinDBG
    - run WinDBG
    - go to File, Open Crash Dump, navigate to the minimdump you want to open.
    - specify the symbol path in the GUI, by going File, Symbol File
    Path, and entering the same command-line syntax
    - once you have the dump file loaded and the symbol path set, run the
    command "!analyze -v"

    This will chug away for a few minutes and then give you a summary report on
    the dump.
     
  9. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    okay thanks a bunch Angad. Will that tell me whats wrong?
     
  10. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    yeah it should....
     
  11. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    I ran the Program and I got this:

    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***

    and a bunch more of "unreadable errors". Then I came across this:

    Probably caused by : NETw4v32.sys ( NETw4v32+3f858 )
     
  12. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    Oh..!! ATM I can't remember much about using Event Viewer.. :eek:

    That file has something to do with the intel wireless driver..!!

    To be able to see the error codes in the BSOD in the future, disable the auto restart setting follow these steps:

    1. Go to Start -> Control Panel -> System
    2. Click on “Advanced” button
    3. Under the Startup and Recovery section, click “Settings”
    4. Under System Failure un-check “Automatically restart”
     
  13. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    Try and update the drivers or revert back to old ones....and disable the auto-restart feature too..!!
     
  14. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    alright
    I'll roll back my drivers
     
  15. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    Sorry for double post,
    However, I'm confused to as why it does not BSoD when I'm connected to the internet. It happens on occasion, regardless to whether or not I'm on the internet
     
  16. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    Can't really say, its been a while since I got a BSOD myself.. :D
    Can u upload that dump file as an attachment (zip), and I ll also have a look at it..!!
     
  17. Uxion

    Uxion Notebook Geek

    Reputations:
    0
    Messages:
    86
    Likes Received:
    0
    Trophy Points:
    15
    Here it is...Have fun!...Sorry it took me so long to upload it, I was rolling back my wi-fi drivers. I archived it into .zip because you can't post .dmp files as attachments.
     

    Attached Files:

  18. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    OK, I will have a look at it and get back to u....and if you get the BSOD again, try to see the STOP error code..!!
     
  19. Andy

    Andy Notebook Prophet

    Reputations:
    2,133
    Messages:
    6,399
    Likes Received:
    1
    Trophy Points:
    206
    As you know, the faulting driver is NETw4v32.sys, which is an Intel® Wireless WiFi Link Adapter Driver for Windows Vista 32-bit (x-86). I don't have your hardware specs, so I looked them up, and saw that your system may have an Intel Wireless WiFi Link 4965AGN. Try out the driver version 11.01.0000.0090, if this is not the one you were using at the time of the BSODs.
    If you have any Checkpoint Software or Zone Alarm, best to uninstall it for now, and see if the computer still suffers from BSODs....

    * Uninstall all Check Point Software Technologies, Inc., products including Zone Alarm
    * Update the NETw4v32.sys driver via Device Manager.

    Use CCleaner to uninstall Zone Alarm. Uninstall all Check Point/Zone Alarm entries.