Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD During System Recovery, Error: 0x0000000A IRQL not less or equal


27 Jul 2012   #1

Windows 7 Home Premium 64bit
 
 
BSOD During System Recovery, Error: 0x0000000A IRQL not less or equal

Hi all,

If anyone could please try assist me...
I live in Jhb, S Africa - I have just purchased a brand new HP DV7 from Bestbuy store in Manhattan, NY earlier this month. I have been experiencing multiple Blue Screens since the first week of use.

I have contacted HP Online support and had 3 conversations with their Support team in India. I am now dealing with HP Support in Cape Town, S Africa - nobody seems to know what the problem is exactly. I have tried everything - including;

Running all the normal tests, running the hard disc test and memory test from f2 screen (or was it f10 screen?),
Disabling all non-Windows programmes,
Running the system recovery/restore from partition on the computer (which failed ie. that is corrupt as well ?),
Physically opening up the back of the laptop and 'reseating the memory',
And also most recently trying to run recovery from the 5 cds that were supplied with it from Geek squad co - This process resulted in BSOD right at the end while it was on disc 5 @ 93% - with error message as in Thread-title "irql not less or equal stop: 0x0000000A".

I am getting quite concerned as this is a brand new laptop - just would love somebody to confirm that either it must be memory which is corrupt, or the actual hardware/motherboard is corrupt ?! I can not believe that this can occur on a brand new machine with such high specs, surely they would have tested & run it properly at the factory before dispatching to the retail outlets ?!

Anyway.. I am at my wit's end, and suspect that the support team at HP have no cooking clue what the issue is - it seems people are actually avoiding returning my calls today LOL !

I must include that I am not a proficient PC dude, not the most techno-savvy. Everything I did mentioned above were all checks and diagnostics that were instructed to me from various HP support staff in SA and India. I will include a summary of (some of) the dump files from crashes before having done all steps mentioned. My major worry is that I cannot now get into Windows at all, and the BSOD whilst performing recovery from discs seems to be a problem ?

[Wednesday, July 25, 2012 6:47 PM] -- Skmd A says:
Michael could you please paste the Report in that tool

[Wednesday, July 25, 2012 6:49 PM] -- Michael Jacobson says:
Here it comes brother >

[Wednesday, July 25, 2012 6:49 PM] -- Michael Jacobson says:
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-HP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535261184 total
VM: 2147352576, free: 1938411520



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 25-Jul-12 01:49:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072512-33181-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6E18)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800116DE18, 0xFFFFF88003B77788, 0xFFFFF88003B76FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Wed 25-Jul-12 01:49:58 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltPerformAsynchronousIo+0xCA8)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800116DE18, 0xFFFFF88003B77788, 0xFFFFF88003B76FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Tue 24-Jul-12 12:12:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-34772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800098F3D0, 0xFFFF, 0x0)
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 Mon 23-Jul-12 05:53:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-29562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0x9B9D001, 0x65D1, 0xFFFFF70001080000)
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 Mon 23-Jul-12 09:14:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-34881-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009C4D40, 0xFFFF, 0x0)
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 Sun 22-Jul-12 10:07:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-36535-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031B53F2, 0xFFFFF8800CAD5920, 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 22-Jul-12 08:22:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-32167-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A30DA0, 0xFFFF, 0x0)
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 Sun 22-Jul-12 07:40:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-32432-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A00DD0, 0xFFFF, 0x0)
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 Sun 22-Jul-12 06:26:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-41901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009EF370, 0xFFFF, 0x0)
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 Sun 22-Jul-12 04:36:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-68827-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x21D5)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 21-Jul-12 11:25:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-30981-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009FB370, 0xFFFF, 0x0)
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 Sat 21-Jul-12 09:33:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-41


[Wednesday, July 25, 2012 6:50 PM] -- Michael Jacobson says:
On Sat 21-Jul-12 09:33:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-41839-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A0CDA0, 0xFFFF, 0x0)
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 20-Jul-12 04:01:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-33306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC7D73, 0xFFFFF8800CF3ACA0, 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 Fri 20-Jul-12 11:51:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-31543-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1DA3A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600004DA3A, 0xFFFFF880030CDB80, 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 Fri 20-Jul-12 11:32:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800096B3D0, 0xFFFF, 0x0)
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

31 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.


[Wednesday, July 25, 2012 6:54 PM] -- Skmd A says:
Click on Start and type MSCONFIG in the start search.
Click on MSCONFIG on the top of the start menu to open the System Configuration page.
On the System Configuration page their will be 5 options on the top : 1) General 2)Boot 3)Services 4)Startup 5)Tools.
Click on Service tab on the top and you will see the list of all the services running on the computer.
On the bottom left hand side of the service’s tab their will be an option “Hide all Microsoft service”. We need to check that option.
Then click on the “Disable all” and then click on Apply at the bottom of the System Configuration page.
Now go to Startup tab on the top and click on the option “Disable all”
Then click on Apply and Ok. It will immediately prompt you to restart the computer but don’t restart the computer and click on “exit without restart”


[Wednesday, July 25, 2012 6:56 PM] -- Skmd A says:
Please let me know after you have done the steps mentioned above

[Wednesday, July 25, 2012 7:00 PM] -- Michael Jacobson says:
one moment

[Wednesday, July 25, 2012 7:00 PM] -- Skmd A says:
Sure please take your time

[Wednesday, July 25, 2012 7:02 PM] -- Michael Jacobson says:
it didnt seem to prompt me tpo restart ?

[Wednesday, July 25, 2012 7:02 PM] -- Michael Jacobson says:
just doing it again to be sure

[Wednesday, July 25, 2012 7:04 PM] -- Michael Jacobson says:
Ali i did that - but MSConfig just closes afterwards, as if there were no changes to apply - is that right ??

[Wednesday, July 25, 2012 7:05 PM] -- Skmd A says:
Yes

[Wednesday, July 25, 2012 7:05 PM] -- Skmd A says:
Now please run the file - Fix Internet Explorer issues to make IE fast, safe and stable
The above mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.


[Wednesday, July 25, 2012 7:06 PM] -- Michael Jacobson says:
OK

[Wednesday, July 25, 2012 7:08 PM] -- Michael Jacobson says:
Ali one question bro - this is all referring to I Explorer - I do not really browse on it much - I have dowbloaded Google Chrome browser and do everything through it..

[Wednesday, July 25, 2012 7:09 PM] -- Skmd A says:
Then you can run the tool - http://go.microsoft.com/?linkid=9740820
The above mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.


[Wednesday, July 25, 2012 7:09 PM] -- Michael Jacobson says:
Should i do just the 2nd one, not the IE one ?

[Wednesday, July 25, 2012 7:10 PM] -- Skmd A says:
Please run both of them

[Wednesday, July 25, 2012 7:10 PM] -- Michael Jacobson says:


[Wednesday, July 25, 2012 7:12 PM] -- Skmd A says:
Please let me know after both the fixit tools have completeled running and fixing issue related to this notebook

[Wednesday, July 25, 2012 7:13 PM] -- Michael Jacobson says:
Troubleshooting cannot continue because an error has occured.... ?!

[Wednesday, July 25, 2012 7:15 PM] -- Michael Jacobson says:
We're sorry but the program encountered an error and can not continue. Please tr again later.

[Wednesday, July 25, 2012 7:15 PM] -- Michael Jacobson says:
tried it again - same thing

[Wednesday, July 25, 2012 7:16 PM] -- Skmd A says:
okay type in msinfo32 and hit enter and please let me know what is the BIOS version installed in this notebook

[Wednesday, July 25, 2012 7:19 PM] -- Michael Jacobson says:
BIOS Version/Date Hewlett-Packard F.19, 21-May-12

[Wednesday, July 25, 2012 7:19 PM] -- Michael Jacobson says:
That what you looking for ?

[Wednesday, July 25, 2012 7:19 PM] -- Skmd A says:
yes

[Wednesday, July 25, 2012 7:24 PM] -- Skmd A says:
Turn off the computer, wait for 5 seconds , turn it back on and keep on tapping on the F2 key it would boot up to the System diagnosis window .In that system diagnosis windows please run the memory test and the hard drive test .
This tests would provide you with a diagnosis result please get in touch with us with the diagnosis result .
After performing the steps, start a new chat session and refer to the chat ID:28820279
.The next technician will be able to see our chat conversation and will assist you further.
So is there anything else i can assist you with ?


[Wednesday, July 25, 2012 7:25 PM] -- Michael Jacobson says:
Ok, will do4

[Wednesday, July 25, 2012 7:25 PM] -- Michael Jacobson says:
Nope, juist want to stop these blue screens man !

That was Chat 1 of 3 with India, have since tried everything mentioned earlier. The hp tema here are now telling me that they duspect the hard drive must have crashed and must be faulty, but want me to run ANOTHER hard drive test from f10 screen - why I wasted my time not running it from here in the 1st place - i don't know.

HELP PLEASE !? Thank you,

Mike


My System SpecsSystem Spec
.

27 Jul 2012   #2

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Have you actually run Memtest86? If so you need to run it a few times to be sure. If you haven't used it then download and install and follow this tutorial;:
Guide to using Memtest86+ - Geeks to Go Forums
You might prefer this one, i have used this one myself to great effect:
RAM - Test with Memtest86+
My System SpecsSystem Spec
27 Jul 2012   #3

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by MikeyJ83 View Post
Hi all,

If anyone could please try assist me...
I live in Jhb, S Africa - I have just purchased a brand new HP DV7 from Bestbuy store in Manhattan, NY earlier this month. I have been experiencing multiple Blue Screens since the first week of use.

I have contacted HP Online support and had 3 conversations with their Support team in India. I am now dealing with HP Support in Cape Town, S Africa - nobody seems to know what the problem is exactly. I have tried everything - including;

Running all the normal tests, running the hard disc test and memory test from f2 screen (or was it f10 screen?),
Disabling all non-Windows programmes,
Running the system recovery/restore from partition on the computer (which failed ie. that is corrupt as well ?),
Physically opening up the back of the laptop and 'reseating the memory',
And also most recently trying to run recovery from the 5 cds that were supplied with it from Geek squad co - This process resulted in BSOD right at the end while it was on disc 5 @ 93% - with error message as in Thread-title "irql not less or equal stop: 0x0000000A".

I am getting quite concerned as this is a brand new laptop - just would love somebody to confirm that either it must be memory which is corrupt, or the actual hardware/motherboard is corrupt ?! I can not believe that this can occur on a brand new machine with such high specs, surely they would have tested & run it properly at the factory before dispatching to the retail outlets ?!

Anyway.. I am at my wit's end, and suspect that the support team at HP have no cooking clue what the issue is - it seems people are actually avoiding returning my calls today LOL !

I must include that I am not a proficient PC dude, not the most techno-savvy. Everything I did mentioned above were all checks and diagnostics that were instructed to me from various HP support staff in SA and India. I will include a summary of (some of) the dump files from crashes before having done all steps mentioned. My major worry is that I cannot now get into Windows at all, and the BSOD whilst performing recovery from discs seems to be a problem ?

[Wednesday, July 25, 2012 6:47 PM] -- Skmd A says:
Michael could you please paste the Report in that tool

[Wednesday, July 25, 2012 6:49 PM] -- Michael Jacobson says:
Here it comes brother >

[Wednesday, July 25, 2012 6:49 PM] -- Michael Jacobson says:
System Information (local)
--------------------------------------------------------------------------------

computer name: PC-HP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535261184 total
VM: 2147352576, free: 1938411520



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 25-Jul-12 01:49:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072512-33181-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6E18)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800116DE18, 0xFFFFF88003B77788, 0xFFFFF88003B76FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Wed 25-Jul-12 01:49:58 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltPerformAsynchronousIo+0xCA8)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800116DE18, 0xFFFFF88003B77788, 0xFFFFF88003B76FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Tue 24-Jul-12 12:12:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-34772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800098F3D0, 0xFFFF, 0x0)
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 Mon 23-Jul-12 05:53:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-29562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0x9B9D001, 0x65D1, 0xFFFFF70001080000)
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 Mon 23-Jul-12 09:14:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-34881-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009C4D40, 0xFFFF, 0x0)
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 Sun 22-Jul-12 10:07:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-36535-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031B53F2, 0xFFFFF8800CAD5920, 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 22-Jul-12 08:22:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-32167-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A30DA0, 0xFFFF, 0x0)
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 Sun 22-Jul-12 07:40:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-32432-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A00DD0, 0xFFFF, 0x0)
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 Sun 22-Jul-12 06:26:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-41901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009EF370, 0xFFFF, 0x0)
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 Sun 22-Jul-12 04:36:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-68827-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x21D5)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 21-Jul-12 11:25:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-30981-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009FB370, 0xFFFF, 0x0)
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 Sat 21-Jul-12 09:33:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-41

[Wednesday, July 25, 2012 6:50 PM] -- Michael Jacobson says:
On Sat 21-Jul-12 09:33:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072112-41839-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A0CDA0, 0xFFFF, 0x0)
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 20-Jul-12 04:01:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-33306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC7D73, 0xFFFFF8800CF3ACA0, 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 Fri 20-Jul-12 11:51:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-31543-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1DA3A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600004DA3A, 0xFFFFF880030CDB80, 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 Fri 20-Jul-12 11:32:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800096B3D0, 0xFFFF, 0x0)
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

31 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

[Wednesday, July 25, 2012 6:54 PM] -- Skmd A says:
Click on Start and type MSCONFIG in the start search.
Click on MSCONFIG on the top of the start menu to open the System Configuration page.
On the System Configuration page their will be 5 options on the top : 1) General 2)Boot 3)Services 4)Startup 5)Tools.
Click on Service tab on the top and you will see the list of all the services running on the computer.
On the bottom left hand side of the service’s tab their will be an option “Hide all Microsoft service”. We need to check that option.
Then click on the “Disable all” and then click on Apply at the bottom of the System Configuration page.
Now go to Startup tab on the top and click on the option “Disable all”
Then click on Apply and Ok. It will immediately prompt you to restart the computer but don’t restart the computer and click on “exit without restart”

[Wednesday, July 25, 2012 6:56 PM] -- Skmd A says:
Please let me know after you have done the steps mentioned above

[Wednesday, July 25, 2012 7:00 PM] -- Michael Jacobson says:
one moment

[Wednesday, July 25, 2012 7:00 PM] -- Skmd A says:
Sure please take your time

[Wednesday, July 25, 2012 7:02 PM] -- Michael Jacobson says:
it didnt seem to prompt me tpo restart ?

[Wednesday, July 25, 2012 7:02 PM] -- Michael Jacobson says:
just doing it again to be sure

[Wednesday, July 25, 2012 7:04 PM] -- Michael Jacobson says:
Ali i did that - but MSConfig just closes afterwards, as if there were no changes to apply - is that right ??

[Wednesday, July 25, 2012 7:05 PM] -- Skmd A says:
Yes

[Wednesday, July 25, 2012 7:05 PM] -- Skmd A says:
Now please run the file - Fix Internet Explorer issues to make IE fast, safe and stable
The above mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.

[Wednesday, July 25, 2012 7:06 PM] -- Michael Jacobson says:
OK

[Wednesday, July 25, 2012 7:08 PM] -- Michael Jacobson says:
Ali one question bro - this is all referring to I Explorer - I do not really browse on it much - I have dowbloaded Google Chrome browser and do everything through it..

[Wednesday, July 25, 2012 7:09 PM] -- Skmd A says:
Then you can run the tool - http://go.microsoft.com/?linkid=9740820
The above mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.

[Wednesday, July 25, 2012 7:09 PM] -- Michael Jacobson says:
Should i do just the 2nd one, not the IE one ?

[Wednesday, July 25, 2012 7:10 PM] -- Skmd A says:
Please run both of them

[Wednesday, July 25, 2012 7:10 PM] -- Michael Jacobson says:


[Wednesday, July 25, 2012 7:12 PM] -- Skmd A says:
Please let me know after both the fixit tools have completeled running and fixing issue related to this notebook

[Wednesday, July 25, 2012 7:13 PM] -- Michael Jacobson says:
Troubleshooting cannot continue because an error has occured.... ?!

[Wednesday, July 25, 2012 7:15 PM] -- Michael Jacobson says:
We're sorry but the program encountered an error and can not continue. Please tr again later.

[Wednesday, July 25, 2012 7:15 PM] -- Michael Jacobson says:
tried it again - same thing

[Wednesday, July 25, 2012 7:16 PM] -- Skmd A says:
okay type in msinfo32 and hit enter and please let me know what is the BIOS version installed in this notebook

[Wednesday, July 25, 2012 7:19 PM] -- Michael Jacobson says:
BIOS Version/Date Hewlett-Packard F.19, 21-May-12

[Wednesday, July 25, 2012 7:19 PM] -- Michael Jacobson says:
That what you looking for ?

[Wednesday, July 25, 2012 7:19 PM] -- Skmd A says:
yes

[Wednesday, July 25, 2012 7:24 PM] -- Skmd A says:
Turn off the computer, wait for 5 seconds , turn it back on and keep on tapping on the F2 key it would boot up to the System diagnosis window .In that system diagnosis windows please run the memory test and the hard drive test .
This tests would provide you with a diagnosis result please get in touch with us with the diagnosis result .
After performing the steps, start a new chat session and refer to the chat ID:28820279
.The next technician will be able to see our chat conversation and will assist you further.
So is there anything else i can assist you with ?

[Wednesday, July 25, 2012 7:25 PM] -- Michael Jacobson says:
Ok, will do4

[Wednesday, July 25, 2012 7:25 PM] -- Michael Jacobson says:
Nope, juist want to stop these blue screens man !

That was Chat 1 of 3 with India, have since tried everything mentioned earlier. The hp tema here are now telling me that they duspect the hard drive must have crashed and must be faulty, but want me to run ANOTHER hard drive test from f10 screen - why I wasted my time not running it from here in the 1st place - i don't know.

HELP PLEASE !? Thank you,

Mike
You say the computer is less than a month old, correct? If so, why waste time trying to trouble shoot a problem that in the end may only lead to other problems? HP has a decent warranty policy and will replace or repair the unit at no cost, unless there was some mitigating reason for them to void the warranty; such as an open box purchase. I suggest you contact HP Customer Care and work with them to either repair or place the unit.

HTH
My System SpecsSystem Spec
.


27 Jul 2012   #4

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

I guess the problem there is the OP is in South frica and the shop where he purcheased the PC is in the USA. If their laws are similar to the UK I think HP will tell him to return it to the store where he purchased it!
My System SpecsSystem Spec
27 Jul 2012   #5

Microsoft Community Contributor Award Recipient

Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
 
 

Home premium 64bit english?
that's the ISO that reinstalls Windows 7 home premium 64bits english
Windows 7 Home Premium SP1-U ISO
English x64: X17-58997.iso
Perform a clean install
Clean Install Windows 7
Delete ALL partitions in step 8

What type of Hewlet Packard machine is it?
My System SpecsSystem Spec
27 Jul 2012   #6

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by mitchell65 View Post
I guess the problem there is the OP is in South frica and the shop where he purcheased the PC is in the USA. If their laws are similar to the UK I think HP will tell him to return it to the store where he purchased it!
Generally the manufacturer will do the repair or replacement during the initial warranty period; to my knowledge, the policy is irrespctive of the point of purchase. Of course, I could be wrong.

Alternatively, if the store were a local Best Buy the product could be exchanged within the first (some number of days) for a new product. In any event, the following is contact information for HP in South Africa;

Gauteng
Gauteng
Gauteng Johannesburg - headoffice
12 Autumn Street
Rivonia



MAP

Phone 27 (0)11 785-1000
Fax 27 (0)11 785-1500
8am-5pm, Mon-Fri


Western Province
Western Province
Western Province Cape Town
Forrest House, Belmont Office Park
14 Belmont Road, Belmont Square
Rondebosch


Phone 27 (0)21 659-5100
Fax 27 (0)21 689-6149
8am-5pm, Mon-Fri


HP Office locations:
Gauteng
Western Province
My System SpecsSystem Spec
Reply

 BSOD During System Recovery, Error: 0x0000000A IRQL not less or equal




Thread Tools



Similar help and support threads for2: BSOD During System Recovery, Error: 0x0000000A IRQL not less or equal
Thread Forum
Solved BSOD: Driver IRQL Not less than or Equal Error BSOD Help and Support
BSOD IRQL not less or equal & system service BSOD Help and Support
IRQL not equal BSOD error BSOD Help and Support
BSOD driver IRQL not less or equal (process name: system) BSOD Help and Support
BSODs IRQL not less or equal 0x0000000a and several others BSOD Help and Support
BSOD error messages : system service exception and irql less not equal BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:51 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33