What the Tech?! Free tech support Archive
This is a read-only archive. No new posts or registrations. Privacy Page
Software

BSOD Help

5 min read

This thread's last reply is from . Advice, software, and links below may be out of date — treat specific steps and download links with caution.

Looking for the outcome? Ask AI

Post #1
Hi here is my PC information:

HP Pavilion Elite m9340f PC
Intel Core 2 Quad
Processor Q6700
Nivida GeForce 9500GS

Windows 7 Ultimate - 64 bit


I usually get a BSOD either on the log in screen or shortly after logging in. It usually happens three times in a row and then usually the computer works fine after that.


I previous had this thread going from about a month ago, but it since has gone dead.:

http://forums.whatthetech.com/index.php?sh…120983&st=0

After trying the recommended solutions I am still receiving BSOD after formatting and re-installing Windows.

Does anybody have anymore suggestions for me?



Here is a dump from WhoCrashed:

Crash Dump Analysis
——————————————————————————–

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 11/29/2011 4:11:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112911-33150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xBE (0xFFFFF6FB7DA0FFD8, 0x141000015C7A5025, 0xFFFFF88003042740, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Tue 11/29/2011 4:11:53 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFF6FB7DA0FFD8, 0x141000015C7A5025, 0xFFFFF88003042740, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Tue 11/29/2011 2:30:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-21559-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20D45)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004330D45, 0xFFFFF880030BD6A8, 0xFFFFF880030BCF00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 11/28/2011 8:36:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-22526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002D9DE6E, 0x0, 0x14)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 11/28/2011 8:34:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-22183-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x37820A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D9020A, 0xFFFFF880033A7838, 0xFFFFF880033A7090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Sat 11/19/2011 4:58:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-22401-01.dmp
This was probably caused by the following module: iastorv.sys (iaStorV+0x56E3F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002A93F96, 0xFFFFF880031A89B8, 0xFFFFF880031A8210)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\iastorv.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - x64
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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: iastorv.sys (Intel Matrix Storage Manager driver - x64, Intel Corporation).
Google query: iastorv.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Sat 11/19/2011 3:25:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-22214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002A83D75)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 11/19/2011 3:21:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC40055858, 0x5, 0x1)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 11/18/2011 3:04:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111711-20826-01.dmp
This was probably caused by the following module: afd.sys (afd+0x2B063)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001721063, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



——————————————————————————–
Conclusion
——————————————————————————–

9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

iastorv.sys (Intel Matrix Storage Manager driver - x64, Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




Thanks for your time.
Post #4

Lee, is that different than the driver you had him download in his last thread for this computer: Intel Rapid Storage Technology driver - x64


mutantboy5, see here: BSOD just started

Did you upgrade to Windows 7? Are the iastor* files older driver files as is mentioned in the link I gave you?

It would be a good idea to post i the Crashes and Debugging forum for these BSOD I thin.


No, in that thread by mutantboy5,.that was a Quick Cam driver causing a problem

This is an Intel Matrix Storage Manager driver - x64, Intel Corporation (iastorv.sys) that seems to be causing a kernel exception.
I think that is a "raid" driver.(?)
Post #5
Hi Lee & Ztrucker, In the previous thread we did try to update that driver before I did the format and the re-install of WIndows 7, plus I removed a QuickCam Driver. So should I still try this driver again with the new install of Windows 7 or is it strange that I have a similar BSOD after a format/re-install of Windows 7? Thanks for your time.
Post #6

I think that is a "raid" driver.(?)


just curious but is he running raid? if not does he need a raid driver? maybe the problem could be solved by going into bios and making sure he's running achi/ide mode for his drive/s and not raid then deleting the driver altogether. shrugs just something that popped into my head so thought i'd just throw it out there for you, no idea how relevant the thought my be. :blush:

:popcorn:
Post #8 last edited
@Mutantboy, I take it you ignored the suggestions here? http://forums.whatthetech.com/index.php?sh…st&p=755478

Out of the three threads you have created for the SAME problem, there is NOTHING to suggest that it is anything other than hardware related failure.

You must also inspect for bad capacitors while you are in the case because even ONE lightly puffed up capacitor is all it takes to have major issues. Notice how subtle the top of the capacitor is raised here: http://www.google.com/imgres?q=bad+capacit…1t:429,r:10,s:0
Post #9
@terr1966 or @Lee how do I know if I am running raid? And is achi and ide the something or do I have to pick one or the other? @appleoddity, I did not ignore that post, I ran the HP diagnostics that you suggested and it found no problems, so I figured it was a software problem, and I ended up formatting the hard drive and re-installing Windows 7 which I would assume would clean up any malware/virus problems. Can capacitors go bad suddenly? I mean I have never opened or touched the computer and it has been working for years.
Post #11
Did you test both the memory and the hard drive? The hard drive test could take an hour or longer to be tested thoroughly. Did the test take that long? The longer you have had your computer the more likely it is you have bad capacitors, or a bad fan, or a dirty case/heatsink. Computers should not run for years without inspecting them and cleaning them out. And the dirtier they are the more likely you are going to have bad capacitors, bad fans, or plugged heatsinks. Not only do the bad capacitors appear on the motherboard, but if you have an additional video card, they often appear on the video card. Bad fans are also quite common on video cards. It doesn't hurt to open the case and look. Its usually as simple as two screws, if not less, to pop the side cover. Get the machine into a position where you can see it running with the cover off. Inspect that all the fans are running, and take a good look at all electronic boards inside to make sure you don't see any bad caps - use a flashlight. I provided a link to images of capacitors. Good capacitors have flat tops - bad ones don't. If the machine is dirty, shut it down and blow it out with some compressed air (outside - or you'll be sorry). Vacuuming does not work very well for cleaning a computer and there is more chance you will damage something trying to get the end of a vacuum in there. In my previous response, I provided a thread for testing your memory. Near the end it talks about reseating the computer's memory. Its also a likely thing to happen - bad connections on the memory. It can create intermittent failures. It doesn't hurt to gently reseat the RAM after cleaning the case to make sure it has a good connection. There are lots of google hits, and youtube videos for DIYers to learn from and time and patience to be spent - otherwise, you may just want to take it somewhere and pay to have it handled appropriately. If you don't follow through on the threads you are creating - somebody might start to get the idea you aren't serious enough to put the work into really fix the computer.
Post #12
HI, Thanks for the response. As far as the HP diagnostics test, I ran it over night, with no errors. I'm not that hardware savvy, so some of your suggestions kinda scare me. Software is easier to navigate around and fix, but it seems like it has come down to checking the hardware. I'll give it my best shot, or maybe I'll hire someone to look into it. I'll look for an appropriate hardware thread to help me out for now. Thanks for all the help.

Ask AI

AI can make mistakes. Check the cited posts. Archived advice can be out-of-date

Don't include personal information. Questions and selected public posts go to OpenAI. About Ask AI