BSOD still after doing windows repair install

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 16
    Windows 7 Home Premium
    Thread Starter
       #11

    Thanks.

    Installed it. Its updated the right one:

    802.11 USB Wireless LAN Card - (15/09/2009) - now (06/09/2013)

    When installing it asked if i wanted to install something else, some Ralink thing - I choses to 'install driver only'.

    You want me to just wait now and see if i get anymore BSOD?.. I havent had any in the past couple of days.

    Cheerz
      My Computer


  2. Posts : 3,056
    Windows 10
       #12

    Orgo said:
    Thanks.

    Installed it. Its updated the right one:

    802.11 USB Wireless LAN Card - (15/09/2009) - now (06/09/2013)

    When installing it asked if i wanted to install something else, some Ralink thing - I choses to 'install driver only'.

    You want me to just wait now and see if i get anymore BSOD?.. I havent had any in the past couple of days.

    Cheerz
    Good choice! no need for 3rd party software on top of the drivers :) .
    Yes that is correct asses the situation for a couple of days and post back.
      My Computer


  3. Posts : 16
    Windows 7 Home Premium
    Thread Starter
       #13

    Hi again.

    Unfortunately I got another BSOD today. I had a feeling it would do it again eventually.

    "Windows couldn’t start"; the same thing it was doing before. I had to force to shut off the laptop when it says it’s automatically fixing problems because it will just do that forever and not actually fix anything. I forced it to try and start normally a few times and it worked the 3rd or 4th time.

    Here’s the computer gibberish – there’s 3 dump files and the 3rd one down (123013-17253-01) is the new one, the other 2 you’ve already seen.

    Oh yeah, i managed to jot down the error i got from the diagnostic program this time:
    "unhandled exception has occured in your aplication. could not find C:\Windows\EventApp.txt."
    I just grabbed them all individually, most of it seems to be there.

    Cheers
      My Computer


  4. Posts : 3,056
    Windows 10
       #14

    Three weeks is not to be disregarded, none the less, the netr28ux was not updated and is now
    the same as it was three weeks ago.

    If you have the option to borrow an alternative recent wireless adapter or switch to Ethernet
    for a while and see how the system handles itself.
    Other then that Avast appears to be causing problems as well if you don't mind I would uninstall
    it and install Microsoft Security Essentials and see how much more stable the system gets.
      My Computer


  5. Posts : 16
    Windows 7 Home Premium
    Thread Starter
       #15

    Hi, whats netr28ux?.. Part of the driver i installed? I changed which USB plug the WiFi was connected to on my USB hub the other day and it said it was installing the driver (auto windows driver thing), i checked to see if it had put the old one back on but the date is 2013 like it should be.

    Maybe i should revert back to old one from device manerger and then reinstall that new driver?..
    (EDIT: Just uninstalled and reinstalld it, how can i check if its updated the netr28ux properly this time?)

    Cant use any other WiFi, im in a caravan outside.

    Ugg, i want to keep Avast but if i cant find out why its casueing BSOD il have to go back to Avira i guess.
      My Computer


  6. Posts : 3,056
    Windows 10
       #16

    Orgo said:
    Hi, whats netr28ux?.. Part of the driver i installed? I changed which USB plug the WiFi was connected to on my USB hub the other day and it said it was installing the driver (auto windows driver thing), i checked to see if it had put the old one back on but the date is 2013 like it should be.

    Maybe i should revert back to old one from device manerger and then reinstall that new driver?..
    (EDIT: Just uninstalled and reinstalld it, how can i check if its updated the netr28ux properly this time?)

    Cant use any other WiFi, im in a caravan outside.

    Ugg, i want to keep Avast but if i cant find out why its casueing BSOD il have to go back to Avira i guess.
    The way to verify it's date of creation rather then the date it was installed on the PC is to navigate
    to C:\Windows\System32\drivers, right clicking the driver choosing Properties
    and looking at the Date modified under the Details tab.
    Attachment 299983
       Note
    This is just an example using an nVidia driver you'll have to look for netr28ux.
      My Computer


  7. Posts : 1,449
    Windows 7 ultimate 64-bit
       #17

    Orgo said:
    Hi, whats netr28ux?.. Part of the driver i installed? I changed which USB plug the WiFi was connected to on my USB hub the other day and it said it was installing the driver (auto windows driver thing), i checked to see if it had put the old one back on but the date is 2013 like it should be.

    Maybe i should revert back to old one from device manerger and then reinstall that new driver?..
    (EDIT: Just uninstalled and reinstalld it, how can i check if its updated the netr28ux properly this time?)

    Cant use any other WiFi, im in a caravan outside.

    Ugg, i want to keep Avast but if i cant find out why its casueing BSOD il have to go back to Avira i guess.
    Unfortunately; some of these antivirus programs seem to interfere with other processes etc; so you may have to find another one if looking for another one solves the issues.
      My Computer


  8. Posts : 16
    Windows 7 Home Premium
    Thread Starter
       #18


    Does that look right?
    It didnt start up properly just now - no BSOD though, i think it maybe becasue theres a game disk in the dvd drive, but that shouldnt stop it starting up should it?.. I posted on the Avast forum seeing if they could find out what was casusing it but no one wants to have a look at the dump files. They said to try a repair of Avast. Ive done that but i doubt it will help. The next BSOD i get, if it says anything about Avast i will remove it and put something else on...

    Cheerz
      My Computer


  9. Posts : 3,056
    Windows 10
       #19

    Yes it does.
    Just to sort things out I had another look at the dumps and I didn't notice that the two other dumps
    are from the 26th & 28th are of November! which are the older dumps.
    So the newest dump, December 30th, is showing the updated 2013 driver and is pointing
    towards Avast as stated above.
    Sorry about the confusion.

    Since it's a single crash in nearly a month I would think much of it, but if it starts to become a regular
    thing (of course I would like to see the dump files) but I would consider removing Avast
    and going with Microsoft Security Essentialsinstead at least for troubleshooting purposes.
      My Computer


  10. Posts : 16
    Windows 7 Home Premium
    Thread Starter
       #20

    OK, thanks i appreciate the help - im guna have to have a think what to do about Avast - it seems to be great at blocking viriuses but it's causing loads of BSOD for people; and they cant seem to fix it. The last virus i got (ZeroAccess) was really nasty and took days to clean up, and Avira didnt stop it. But i didnt have Comodo at the time either - maybe the 2 together would have stopped it. I read somewhere that even MS is recomending people use 3rd party antivirus becasue MSE is so bad at blocking viruses.. lol.
    Goodbye Microsoft Security Essentials: Microsoft Now Recommends You Use a Third-Party Antivirus » MyComputerMan IT Support Services

    I dont know, definailty if it BSOD again Avast is gone. I might put Avira back on to test if it stops the BSOD, and hope Avast finally fixes the issue properly so i can put that back on, but they've had a while to fix it and havent managed it so far.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:44.
Find Us