Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen of Death on bootup


  • Please log in to reply
1 reply to this topic

#1 bromberg

bromberg

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:20 PM

Posted 07 February 2011 - 10:53 AM

I'm running Vista Home Premium/sp2/64 bit and recently I'm getting the Blue Screen on bootups with various STOP codes.
Sometimes I boot with no problem, sometimes I get the BSoD, and almost always after the BSoD when I re-boot I have no BSoD problem. Rarely will I get the BSoD afetr bootup but it has happened a couple of times after 5 minutes or so while working on my PC.

In addition to resolving this issue, I have a couple of questions that I'm curious about:
1)Why does a 2nd re-boot never have a BSoD problem?!?
2)Does Microsoft offer a utility to analyze the MiniDump files produced?
3)Is there a suggested process offered by MS that we should follow when we get a dump?

Anyhow I would appreciate any guidance you may have and below is a summary report from the WhoCrashed utility.
Thanks in advance for any assistance you can offer and do not hesitate to contact me (doooodles@gmail.com) if you require further documentation from me.

Dan
***
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4293214208 total
VM: 2147352576, free: 2006609920



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 2/6/2011 1:29:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0xA (0x0, 0xC, 0x1, 0xFFFFF80002AAB6F8)
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 Sun 2/6/2011 1:29:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastor.sys (iastor+0x49CD1)
Bugcheck code: 0xA (0x0, 0xC, 0x1, 0xFFFFF80002AAB6F8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - x64
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.
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: iastor.sys (Intel Matrix Storage Manager driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL




On Tue 2/1/2011 2:35:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020111-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0x18 (0xFFFFFA80039C9840, 0xFFFFFA8007505210, 0x1, 0x1)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Tue 2/1/2011 2:33:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0x44 (0xFFFFFA8007D29AD0, 0xE7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 driver has tried to requested an IRP be completed that is already complete.
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 1/31/2011 2:57:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini013111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B49473, 0xFFFFFA600B1F75B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 1/23/2011 3:02:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012311-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 1/23/2011 6:14:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE1964)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000161964, 0xFFFFFA6009838390, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.
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 Sat 1/22/2011 5:56:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0xA (0x2672D3, 0x2, 0x1, 0xFFFFF80002A85F17)
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 Fri 1/21/2011 11:13:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0xD1 (0x2, 0x2, 0x0, 0xFFFFFA800717D050)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:20 PM

Posted 07 February 2011 - 11:11 AM

First a question: What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

Next, here are some troubleshooting steps:

1) Download & install the current drivers for your video card, sound card, and check for a newer chipset driver
2) Check for a bios upgrade
3) Download memtest, burn it to disk, and check your ram: http://www.memtest.org/
4) Please run checkdisk: To check the hard drive right-click on a command prompt icon and open as administrator. In the command prompt window type:chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.
5) Just as a precaution, please run full scans with both your AV and with MalwareBytes





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users