Getting random BSOD on Windows 7 (ntoskrnl.exe)

Hi, I'm on a new build and have been getting random BSOD. I don't know exactly when it happens but it has happened a few times while browsing the internet on firefox.

I don't know what's causing these random BSOD. In BlueScreenView I can see about 6 crashes were caused by ntoskrnl.exe and one crash also had volmgrx.sys listed in it.

I attached the dump files so maybe you can help me figure this out. I'm using Windows 7 Ultimate 64 bit.

Thank you.

Several of these show a disk controller error Lets start with a chkdsk.

Disk Check

Thanks for the response.

I ran chkdsk from the drive's properties page and got "No problems were found on the device or disk. It is ready to use" on every drive I have connected.

had another BSOD overnight

ganjiry said:

this may be worth a try. if uu download this programe "who crashed" run it n select scan. it will then tell u to scroll down to the bottom where a list of possible cause will be. hope it helps
Resplendence Software - WhoCrashed, automatic crash dump analyzer

From the report:


On Thu 5/10/2012 10:33:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-10155-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800754C2E0, 0xFFFFFA800754C5C0, 0xFFFFF800033DE300)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Thu 5/10/2012 10:33:43 AM 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: 0xF4 (0x3, 0xFFFFFA800754C2E0, 0xFFFFFA800754C5C0, 0xFFFFF800033DE300)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Thu 5/10/2012 8:15:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-9952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DDA8750, 0xFFFFFA800DDA8A30, 0xFFFFF800033DC300)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Thu 5/10/2012 7:04:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051012-9921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FB40000000, 0xFFFFFFFFC000000E, 0x9A5B5884, 0xFFFFF68000000000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 5/10/2012 5:09:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-10389-02.dmp
This was probably caused by the following module: volmgrx.sys (volmgrx+0x1000)
Bugcheck code: 0x7A (0xFFFFF6FC400073F0, 0xFFFFFFFFC00000C0, 0xCF242860, 0xFFFFF88000E7E000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\volmgrx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Extension Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Thu 5/10/2012 12:53:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-10389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800757FB30, 0xFFFFFA800757FE10, 0xFFFFF8000337B300)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 5/8/2012 4:46:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-8533-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0xFFFFF6FC40019E20, 0xFFFFFFFFC000000E, 0x1BB5BCBE0, 0xFFFFF880033C4000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 5/4/2012 1:40:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-7098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA80070BD7C8, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 5/3/2012 10:38:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-7488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A0C66B0, 0xFFFFFA800A0C6990, 0xFFFFF800031D2300)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Thu 5/3/2012 10:28:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-10030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A138B30, 0xFFFFFA800A138E10, 0xFFFFF800031CE240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Thu 5/3/2012 9:51:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-6832-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80099D9060, 0xFFFFFA80099D9340, 0xFFFFF80002F88240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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.

ganjiry said:

this may be worth a try. if uu download this programe "who crashed" run it n select scan. it will then tell u to scroll down to the bottom where a list of possible cause will be. hope it helps
Resplendence Software - WhoCrashed, automatic crash dump analyzer

[QUOTE=scorsy77;1916826]

ganjiry said:

this may be worth a try. if uu download this programe "who crashed" run it n select scan. it will then tell u to scroll down to the bottom where a list of possible cause will be. hope it helps
Resplendence Software - WhoCrashed, automatic crash dump analyzer

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

zigzag3143 said:

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Were you able to find anything in the memory dumps? I think I might reformat later today and see if that helps.

I ran bootable memtest earlier but only did 1 pass and no errors were found.

scorsy77 said:

zigzag3143 said:

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Were you able to find anything in the memory dumps? I think I might reformat later today and see if that helps.

I ran bootable memtest earlier but only did 1 pass and no errors were found.

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd>
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.


While we are waiting for your memtest results please run a chdkdsk

Disk Check

zigzag3143 said:

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd>
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.


While we are waiting for your memtest results please run a chdkdsk

Disk Check

I ran a memtest for a little over 2 hours for 4 passes and found 0 errors.

I ran a chkdsk following the link you gave me using Option 1 and found no errors.

I think I'm going to reformat and I will post back in this thread if BSOD continues.