Windows 7 BSOD's
Hi EE,
I am hoping you can help me with a problem.
We have a cusotmer's PC on the bench that has been BSODing very randomly for the past ...well 6 months probably.
I am unable to determine the cause of the BSODs as we never see them on the bench.
Like many customer's computers there is always lots to do at first and never really sure when or if it is solved.
Attached is the minidump files I am hoping someone can scan those and give me some inclination into some files that may be causing these issues.
As always, I've tested the hardware thoroughly and come up with nothing. But that is not to say there isn't something wrong.
This configuration is a big wonky:
The customer has an OS Drive partitioned into 2
Scratch drive partitioned into 2
RAID 1 Data drive
Let me know if you need anything more.
Thank you,
Micro-Vision
miinidump.zip
msinfo32.txt
I am hoping you can help me with a problem.
We have a cusotmer's PC on the bench that has been BSODing very randomly for the past ...well 6 months probably.
I am unable to determine the cause of the BSODs as we never see them on the bench.
Like many customer's computers there is always lots to do at first and never really sure when or if it is solved.
Attached is the minidump files I am hoping someone can scan those and give me some inclination into some files that may be causing these issues.
As always, I've tested the hardware thoroughly and come up with nothing. But that is not to say there isn't something wrong.
This configuration is a big wonky:
The customer has an OS Drive partitioned into 2
Scratch drive partitioned into 2
RAID 1 Data drive
Let me know if you need anything more.
Thank you,
Micro-Vision
miinidump.zip
msinfo32.txt
ASKER
Oh man,
Unfortunatley the issue has been around for a long time.
I guess i'll update all of the drivers for the system.
I will keep you posted!
Unfortunatley the issue has been around for a long time.
I guess i'll update all of the drivers for the system.
I will keep you posted!
I am with @pwnbasketz on this one. After reading the minidumps 2 of the 4 crashes blamed the NT Kernel...which is essentially the system itself. That could mean failing hardware too. If you want to do all troubleshooting possible then do the following...
1. Run a disk check. In windows 7 you can just go to Start and in the search box type chkdsk. Then right click "Run as Administrator". It will run on next restart/boot up.
2. Run Memtest86 http://www.memtest86.com/memtest86-4.0a.iso.zip
That will check if any of the RAM has/is going bad.
3. The drivers being up to date is also likely a cause. Outdated drivers have been known to cause crashes or even BSOD's.
Again, these 3 steps are to do full troubleshooting. Easiest thing to do first is check all your drivers then the chkdsk. The memtest is a bit more difficult to run as you "Boot from CD" with it. On the website there are instructions though.
Also in the future. A great free tool to read minidumps thoroughly and easily is Nirsoft Bluescreenview.
http://www.nirsoft.net/utils/bluescreenview_setup.exe
1. Run a disk check. In windows 7 you can just go to Start and in the search box type chkdsk. Then right click "Run as Administrator". It will run on next restart/boot up.
2. Run Memtest86 http://www.memtest86.com/memtest86-4.0a.iso.zip
That will check if any of the RAM has/is going bad.
3. The drivers being up to date is also likely a cause. Outdated drivers have been known to cause crashes or even BSOD's.
Again, these 3 steps are to do full troubleshooting. Easiest thing to do first is check all your drivers then the chkdsk. The memtest is a bit more difficult to run as you "Boot from CD" with it. On the website there are instructions though.
Also in the future. A great free tool to read minidumps thoroughly and easily is Nirsoft Bluescreenview.
http://www.nirsoft.net/utils/bluescreenview_setup.exe
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well that's odd.
It doesn't have a wireless card or never has.
Thanks for the info
It doesn't have a wireless card or never has.
Thanks for the info
Well might not be wireless, think RALink make wired cards as well, what model is the network card?
ASKER
MSI P67A-GD53
Realtek onboard network adapter
Realtek onboard network adapter
Ok, only other thing I can think of is they had a wireless card, check if anything from RALink is installed, check Device manager for anything listed under Network as well...that file came from somewhere so at some point it may have been installed
Possibly a USB wireless device at some point?
Possibly a USB wireless device at some point?
ASKER
Okay doke. Yeah i will definitley remove any traces of RAlink.
Umm, do you know of any driver cleaners (that actually work) that I could use to sweep RAlink from existence?
Umm, do you know of any driver cleaners (that actually work) that I could use to sweep RAlink from existence?
None that are free, but DriverMagician has this option - http://www.drivermagician.com/UninstallDriver.htm
ASKER
This just in - the customer has a wireless USB adapter that was never brought to my attention.
I'm going to go after that when the adapter is brought in. Will post tomorrow AM.
I'm going to go after that when the adapter is brought in. Will post tomorrow AM.
i would start in this case by running ram and disk diags; to be sure about the basics
download UBCD, and run memtest86+ for ram and a disk diag, LONG test
you can also look in event viewer for problems
download UBCD, and run memtest86+ for ram and a disk diag, LONG test
you can also look in event viewer for problems
Not sure if this will help. But I had an issue once with a Wireless USB adapter causing random BSOD issues with a particular Wireless Router.
It took months to isolate this and the end result was to replace the access point. Fixed.
Mark
It took months to isolate this and the end result was to replace the access point. Fixed.
Mark
ASKER
Ran all hard drive tests and thorough chkdsks - Pass.
Verified RAID status - good
Memtes86+ 4.20 - 24 hours no errors.
Eventvwr has information - but none really relevant.
@crash2000 really a specific router and adapter combination caused you grief?
Now i've heard of everything!
I will be either replacing this Wireless NIC or updating the drivers and letting it go out.
Verified RAID status - good
Memtes86+ 4.20 - 24 hours no errors.
Eventvwr has information - but none really relevant.
@crash2000 really a specific router and adapter combination caused you grief?
Now i've heard of everything!
I will be either replacing this Wireless NIC or updating the drivers and letting it go out.
crash dump file: C:\Windows\Minidump\062512
uptime: 22:37:11
This was probably caused by the following module: Unknown (0xFFFFF80003AC91C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003DBBB21, 0xFFFFF88006FA3660, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_SERVICE_EXCEPTION
On Thu 5/24/2012 9:48:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112
uptime: 03:57:22
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800CDEE060, 0xFFFFF800053863D8, 0xFFFFFA80156AAC10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 5/21/2012 6:26:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012
uptime: 03:18:40
This was probably caused by the following module: Unknown (0xFFFFF80003A861C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF8800105DD16)
Error: DRIVER_IRQL_NOT_LESS_OR_EQ
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown DRIVER_IRQL_NOT_LESS_OR_EQ
On Fri 5/18/2012 10:46:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812
uptime: 03:15:24
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8011501060, 0xFFFFF8000538F3D8, 0xFFFFFA800DAD7C10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
I threw that into my nifty crash dump analyzer and came back with that. Personally, I'd start looking at any drivers that were recently updated or any system updates that were recently installed.