Page 1 of 1
BSOD error..... HELP!!!
#1
Posted 29 April 2009 - 02:45 PM
hey, i've been getting these BSOD's over the past month, and i have no idea what they mean or what to do about them.
I'm running vista premium, by the way.
this is the most frequent one (comes up at startup)
A problem has been detected and windows has been shut down to prevent damage to your computer.
DRIVERIRQLNOTLESSOR_EQUAL
If this is the first time you have seen this stop error screen, restart your computer. if this screen appears again, follow these steps:
blahblahblahblahblahblah...........................
Technical information:
* STOP: 0x000000d1 (0x000000B0,0x00000002, 0x00000001, 0x8C879e6e)
* tcp1p.sys - Address 8C879e6e base at 8c80F000, Datestamp 4812c4f1
Collecting data for crash dump...
blahblahblah
_
This one has just started to come up-
A problem has been detected and windows has been shut down to prevent damage to your computer.
PAGEFAULTINNONPAGEDAREA
blahb lahblahblahblah...
Technocal infornation-
* STOP: 0x0000008e (0xC0000005, 0x85405381, 0x87f32458, 0x00000000)
* wimFsf.sys - Address 85405381 base at85401000, DateStamp 4549ad99
collecting data for crash dump...
blahblahblahblahblahblah
can anyone help me? any info as to the problem and/or solution would be appreciated. Thanks
I'm running vista premium, by the way.
this is the most frequent one (comes up at startup)
A problem has been detected and windows has been shut down to prevent damage to your computer.
DRIVERIRQLNOTLESSOR_EQUAL
If this is the first time you have seen this stop error screen, restart your computer. if this screen appears again, follow these steps:
blahblahblahblahblahblah...........................
Technical information:
* STOP: 0x000000d1 (0x000000B0,0x00000002, 0x00000001, 0x8C879e6e)
* tcp1p.sys - Address 8C879e6e base at 8c80F000, Datestamp 4812c4f1
Collecting data for crash dump...
blahblahblah
_
This one has just started to come up-
A problem has been detected and windows has been shut down to prevent damage to your computer.
PAGEFAULTINNONPAGEDAREA
blahb lahblahblahblah...
Technocal infornation-
* STOP: 0x0000008e (0xC0000005, 0x85405381, 0x87f32458, 0x00000000)
* wimFsf.sys - Address 85405381 base at85401000, DateStamp 4549ad99
collecting data for crash dump...
blahblahblahblahblahblah
can anyone help me? any info as to the problem and/or solution would be appreciated. Thanks
#2
Posted 29 April 2009 - 06:17 PM
a couple questions-
how old is your computer?
how much ram is in the system?
are you running 32 bit or 64 bit?
the first one might be related to the network card driver...
(boot into safe mode and uninstall/update the driver)
the second one, might be an issue with your ram, or your hdd has bad sectors (is this one random or does it happen when you do something specific?)
if you have alot of ram, pop out one of the sticks and boot up,(if you get the bsod still, swap out the ram)
how old is your computer?
how much ram is in the system?
are you running 32 bit or 64 bit?
the first one might be related to the network card driver...
(boot into safe mode and uninstall/update the driver)
the second one, might be an issue with your ram, or your hdd has bad sectors (is this one random or does it happen when you do something specific?)
if you have alot of ram, pop out one of the sticks and boot up,(if you get the bsod still, swap out the ram)
#3
Posted 29 April 2009 - 07:09 PM
Sleuth said:
hey, i've been getting these BSOD's over the past month, and i have no idea what they mean or what to do about them.
I'm running vista premium, by the way.
this is the most frequent one (comes up at startup)
A problem has been detected and windows has been shut down to prevent damage to your computer.
DRIVERIRQLNOTLESSOR_EQUAL
If this is the first time you have seen this stop error screen, restart your computer. if this screen appears again, follow these steps:
blahblahblahblahblahblah...........................
Technical information:
* STOP: 0x000000d1 (0x000000B0,0x00000002, 0x00000001, 0x8C879e6e)
* tcp1p.sys - Address 8C879e6e base at 8c80F000, Datestamp 4812c4f1
Collecting data for crash dump...
blahblahblah
I'm running vista premium, by the way.
this is the most frequent one (comes up at startup)
A problem has been detected and windows has been shut down to prevent damage to your computer.
DRIVERIRQLNOTLESSOR_EQUAL
If this is the first time you have seen this stop error screen, restart your computer. if this screen appears again, follow these steps:
blahblahblahblahblahblah...........................
Technical information:
* STOP: 0x000000d1 (0x000000B0,0x00000002, 0x00000001, 0x8C879e6e)
* tcp1p.sys - Address 8C879e6e base at 8c80F000, Datestamp 4812c4f1
Collecting data for crash dump...
blahblahblah
Might see if this helps with this one: http://aumha.org/a/stop.php#0xd1
Quote
_
This one has just started to come up-
A problem has been detected and windows has been shut down to prevent damage to your computer.
PAGEFAULTINNONPAGEDAREA
blahb lahblahblahblah...
Technocal infornation-
* STOP: 0x0000008e (0xC0000005, 0x85405381, 0x87f32458, 0x00000000)
* wimFsf.sys - Address 85405381 base at85401000, DateStamp 4549ad99
collecting data for crash dump...
blahblahblahblahblahblah
can anyone help me? any info as to the problem and/or solution would be appreciated. Thanks
This one has just started to come up-
A problem has been detected and windows has been shut down to prevent damage to your computer.
PAGEFAULTINNONPAGEDAREA
blahb lahblahblahblah...
Technocal infornation-
* STOP: 0x0000008e (0xC0000005, 0x85405381, 0x87f32458, 0x00000000)
* wimFsf.sys - Address 85405381 base at85401000, DateStamp 4549ad99
collecting data for crash dump...
blahblahblahblahblahblah
can anyone help me? any info as to the problem and/or solution would be appreciated. Thanks
Might see if this one helps the second one: http://aumha.org/a/stop.php#0x50
#10
Posted 13 May 2009 - 02:50 PM
Might be too much junk ....and many broken-invalid registies.....?
Try a simple cleaning first ...: www.ccleaner.com/download ....
Try a simple cleaning first ...: www.ccleaner.com/download ....
#12
Posted 16 May 2009 - 03:37 PM
The problem is likely to be failing Ram, especially if -
- BSODs occur at random, even when the PC is idle.
- the BSOD messages are also random rather than repetitive i.e. you tend to see different messages related to different drivers each time the PC crashes.
- it tends to occur more often (or can be triggered) when the Ram is in heavy use (eg. gaming).
It could also be a failing hard drive, but that's less likely to cause random system lockups. In that case you're more likely see a BSOD being related to a particular activity or software that fails due to unreadable areas on the drive (bad sectors on the drive). However, a hard drive failure may appear just like a Ram failure if areas of the hard drive being used to store the virtual memory are affected by unreadable bad sectors. Failing hard drives also tend to make a clicking noise at times. To rule out a hard drive failure, do a complete error-checking scan of your main drive (usually C:), making sure to select the option to scan for and attempt recovery of bad sectors. If you find bad drive sectors during the scan, your drive may indeed be failing.
To determine if you have failing Ram, you need to download memory testing software... you can get it here-
http://www.memtest.org/
The site provides an ISO of the software, which you will have to burn to a CD. Then you will have to restart your PC with the disc in the tray, making sure to set your PC's Bios to attempt to boot to the CD before booting the hard drive. The software will give you the option to perform various tests on your Ram and it may take hours so you may want to do this overnight. If you have two sticks on Ram in your PC, you should test them one at a time, so that you can determine if only one is failing. But to be honest, if one is failing and they're from the same brand and were installed simultaneously, you should just replace both (there's a good chance the other will fail soon)
One last thing. If you added new hardware to your PC recently, you should uninstall it to see if its driver was causing the problem. Alternately, you could update the drivers for any newly installed device.
- BSODs occur at random, even when the PC is idle.
- the BSOD messages are also random rather than repetitive i.e. you tend to see different messages related to different drivers each time the PC crashes.
- it tends to occur more often (or can be triggered) when the Ram is in heavy use (eg. gaming).
It could also be a failing hard drive, but that's less likely to cause random system lockups. In that case you're more likely see a BSOD being related to a particular activity or software that fails due to unreadable areas on the drive (bad sectors on the drive). However, a hard drive failure may appear just like a Ram failure if areas of the hard drive being used to store the virtual memory are affected by unreadable bad sectors. Failing hard drives also tend to make a clicking noise at times. To rule out a hard drive failure, do a complete error-checking scan of your main drive (usually C:), making sure to select the option to scan for and attempt recovery of bad sectors. If you find bad drive sectors during the scan, your drive may indeed be failing.
To determine if you have failing Ram, you need to download memory testing software... you can get it here-
http://www.memtest.org/
The site provides an ISO of the software, which you will have to burn to a CD. Then you will have to restart your PC with the disc in the tray, making sure to set your PC's Bios to attempt to boot to the CD before booting the hard drive. The software will give you the option to perform various tests on your Ram and it may take hours so you may want to do this overnight. If you have two sticks on Ram in your PC, you should test them one at a time, so that you can determine if only one is failing. But to be honest, if one is failing and they're from the same brand and were installed simultaneously, you should just replace both (there's a good chance the other will fail soon)
One last thing. If you added new hardware to your PC recently, you should uninstall it to see if its driver was causing the problem. Alternately, you could update the drivers for any newly installed device.
#13
Posted 16 May 2009 - 05:27 PM
Hey Sleuth !!
Welcome to PCWorld Community !
It might be helpful to run this little app. WhoCrashed . Click on the blue words.
From the link above you can read about the program and what it does.
From this link , you can download and install IF you so desire :
|
http://forums.pcworld.com/%2]|[WhoCrashed 1.01
Comprehensible crash dump analysis tool
for Windows Vista/XP/2008/2003/2000 (x86 and x64)|Download free home edition
Buy Professional Edition|
| |
Use only the Free Home Edition as this is all you'll need.
Once the app. finishes reading the Mini Dumps, you can
Copy and Paste the results in you next post. This might give
us a better insight at what the problem is.
FLASHORN. !http://forums.pcworld.com/legacyimages/
1!
Welcome to PCWorld Community !
It might be helpful to run this little app. WhoCrashed . Click on the blue words.
From the link above you can read about the program and what it does.
From this link , you can download and install IF you so desire :
|
http://forums.pcworld.com/%2]|[WhoCrashed 1.01Comprehensible crash dump analysis tool
for Windows Vista/XP/2008/2003/2000 (x86 and x64)|Download free home edition
Buy Professional Edition|
| |
Use only the Free Home Edition as this is all you'll need.
Once the app. finishes reading the Mini Dumps, you can
Copy and Paste the results in you next post. This might give
us a better insight at what the problem is.
FLASHORN. !http://forums.pcworld.com/legacyimages/
1!
#14
Posted 18 May 2009 - 04:38 PM
Thanks for all the help, I really appreciate it.
I downloaded memtest86+ v2.11 ISO and ran it, and at pass 0, test 4 (moving inversions, random pattern) the bottom of the screen flooded with red error messages. there were 35,840 of them. these error messages stopped after test 4.
Kind of a stupid question to ask considering all of the errors, but does this mean that my ram is malfunctioning? i'm inexperienced when it comes to these things.
also, if I do end up replacing my RAM (as I was looking into it anyway) does the 'timing' count? it says that my current ram is 5-5-5-15. if I were to get, say 5-6-6-18 timing RAM, would that be compatible with my system? my RAM is currently 2GB PC2-8500 DDR2 RAM.
I downloaded memtest86+ v2.11 ISO and ran it, and at pass 0, test 4 (moving inversions, random pattern) the bottom of the screen flooded with red error messages. there were 35,840 of them. these error messages stopped after test 4.
Kind of a stupid question to ask considering all of the errors, but does this mean that my ram is malfunctioning? i'm inexperienced when it comes to these things.
also, if I do end up replacing my RAM (as I was looking into it anyway) does the 'timing' count? it says that my current ram is 5-5-5-15. if I were to get, say 5-6-6-18 timing RAM, would that be compatible with my system? my RAM is currently 2GB PC2-8500 DDR2 RAM.
Page 1 of 1
Sign In
Register
Help

MultiQuote



