I randomly get this BSOD, I can't seem to pinpoint to a certain activity. Thanks for any help.
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
BSOD details:
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Extra information about the problem
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800031B4A9B
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Bucket ID: X64_0x1e_c0000005_nt!ExDeferredFreePool+1df
Server information: e7d6b654-42e3-4cca-8488-c6ff7af4f157
Hi Lee,
Thanks for the response.
Here is my results:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 11/2/2011 2:22:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110111-20623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031B4A9B, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Wed 11/2/2011 2:22:07 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: msrpc.sys (msrpc!RpcBindingSetOption+0x14DB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031B4A9B, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
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.
On Wed 10/26/2011 1:20:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102511-26332-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF880076D883C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 10/25/2011 2:13:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102411-23774-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88007CCC83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 10/21/2011 2:06:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800A1A78E0, 0x2, 0xFFFFF8000321E901)
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 Wed 10/19/2011 6:43:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-25506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800B7CD370, 0x2, 0xFFFFFA800A21A5BF)
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 Thu 10/13/2011 3:38:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-28360-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800747A83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 10/13/2011 3:08:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-25568-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88006C6083C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 10/12/2011 1:09:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-27440-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800729F83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 10/11/2011 2:43:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-28906-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF880070DA83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 10/10/2011 2:17:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101011-40607-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88006C8483C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 10/6/2011 2:48:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-25646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF960E020F018, 0x0, 0xFFFFF800030FDFCB, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 10/5/2011 1:49:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100411-33415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360C71)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000337FC71, 0xFFFFF880033CBA18, 0xFFFFF880033CB270)
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 Tue 10/4/2011 2:34:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-25521-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88007E3183C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 9/29/2011 7:37:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092911-25849-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF880082CE83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
——————————————————————————–
Conclusion
——————————————————————————–
20 crash dumps have been found and analyzed. Only 15 are included in this report. 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:
lv302v64.sys
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.
iF so please go here and update this driver lv302v64.sys as Quick Cam is commonly associated with it and seems to be the main cause of your PC's problem.
Another possibility is that this Windows file Ntoskrnl.exe is corrupted or only is being corrupted by the above driver. If you can seen this process in Windows Task Manager, it represents the possible presence of a virus as it should not be showing.
See how you go updating the the driver before we worrying about Ntoskrnl.exe.
Hi Lee,
I use to have a Logitech Quick Cam installed. How do I go about removing the Quick Cam Driver, I don't see any more Logitech Quick Cam software anywhere on this computer.
Thanks
Hi again and thanks again for the responses!
I found and removed my hidden Quick Cam device driver following the above directions
So whats next?
Again thanks so much for you time.
Hi Lee,
I did reboot my machine after I removed the device driver. Its hard to say if I am still getting the BSOD, since it would randomly happen. So I'll have to wait a few days to see if I get a BSOD again. I hope I don't. If I get one again, I'll post my WhoCrashed results.
Thanks so much!
Hi guys,
So I got another BSOD today and I ran the WhoCrashed application again and here is my results:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 11/7/2011 4:40:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-21184-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x39568D0, 0x2, 0x0, 0xFFFFF8000308B4FE)
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 Mon 11/7/2011 4:40:37 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x259F2)
Bugcheck code: 0xA (0x39568D0, 0x2, 0x0, 0xFFFFF8000308B4FE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology 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 Rapid Storage Technology driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL
On Wed 11/2/2011 2:22:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110111-20623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031B4A9B, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Wed 10/26/2011 1:20:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102511-26332-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF880076D883C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 10/25/2011 2:13:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102411-23774-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88007CCC83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 10/21/2011 2:06:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800A1A78E0, 0x2, 0xFFFFF8000321E901)
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 Wed 10/19/2011 6:43:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-25506-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800B7CD370, 0x2, 0xFFFFFA800A21A5BF)
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 Thu 10/13/2011 3:38:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-28360-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800747A83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 10/13/2011 3:08:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-25568-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88006C6083C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 10/12/2011 1:09:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-27440-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF8800729F83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 10/11/2011 2:43:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-28906-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF880070DA83C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 10/10/2011 2:17:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101011-40607-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88006C8483C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 10/6/2011 2:48:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-25646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF960E020F018, 0x0, 0xFFFFF800030FDFCB, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 10/5/2011 1:49:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100411-33415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x360C71)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000337FC71, 0xFFFFF880033CBA18, 0xFFFFF880033CB270)
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 Tue 10/4/2011 2:34:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-25521-01.dmp
This was probably caused by the following module: lv302v64.sys (LV302V64+0x1683C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88007E3183C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: lv302v64.sys .
Google query: lv302v64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
——————————————————————————–
Conclusion
——————————————————————————–
21 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have 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:
iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
lv302v64.sys
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 in advance for the help
This driver is for Raid HDDs so you only have two to choose from
See (Which file should I download?) on the same page.
Do a System restore before downloading and installing the driver just in case you need to do a driver roll-back.
You also may have some registry corruption problems caused by the above driver but maybe not. If you are still having BSODs after updating that driver, then you have a corrupted OS generally caused by the use of a registry cleaner or left over Malware damage after it was removed. The problem of Melware is not removing it (though that can be an art in itself), but the damage it leaves behind and that cannot be removed.
If the above is the case (still crashing after upgrading the driver), I'd be seriously thinking of doing - Recover Windows 7 Operating System Using HP Recovery which would return your computer to it's original factory state. All personal data etc. would need to be removed to disk or a USB drive first.
Alternatively if you have a W7 installation disc, a clean install would be the way to go.
Hi Lee,
Thanks for the response.
I updated the Raid HDD and did a reboot, so I guess we'll have to wait and see if I get BSOD of death again. Last time it took about 5 days to get one again, so we'll see.
I do have a W7 installation disc, does that option also erase all your personal data, like the HP recovery does?
Thanks for all the help.
Knowing you have a W7 installation disk makes things much simpler and I should have mentioned in my last post a "repair Install" option open to you if you had a disk, but it was late and I was tired (I'm in a different time zone as I live in Australia) and I thought of it after I had turned off my computer
A Repair Install or Startup Repair of Windows 7 is an excellent option when you need to reinstall important Windows files but keep all of your personal files and programs intact. It could also be called a "copy over" install and won't erase any personal data.
It will refresh your registry and replace any damaged files. Like new!
The only work to do afterwards is to re-do any personal W7 OS tweeks that you have made to suit your computer usage style.
Hi Lee,
I am still getting the BSOD and I tried the "How To Perform a Startup Repair in Windows 7" link and it said that it could not find any problems to fix.
Do you have a link on how to do a "repair Install/copy over install" of Windows 7?
I like the option where I don't lose my personal data
Again thanks for you time, and I look forward to hearing back from you.
✨ 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
Again thanks for you time, and I look forward to hearing back from you.