[mystery_man_]

So ive been getting alot of BSOD today.. heres my info from dumps bellow here.

What do you think is the problem? And what is this nt_fffff80000b95000.sys ?




Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 13.6.2013 6:57:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-20342-01.dmp
This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
Bugcheck code: 0x109 (0xA3A039D897A44572, 0xB3B7465EEA228310, 0xFFFFF80000B96BB0, 0x6)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
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: nt_fffff80000b95000.sys .
Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



On Thu 13.6.2013 6:57:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
Bugcheck code: 0x109 (0xA3A039D897A44572, 0xB3B7465EEA228310, 0xFFFFF80000B96BB0, 0x6)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
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: nt_fffff80000b95000.sys .
Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



On Thu 13.6.2013 5:49:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-43134-01.dmp
This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
Bugcheck code: 0x109 (0xA3A039D895C45847, 0xB3B7465EE84295F5, 0xFFFFF80000B96BB0, 0x6)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
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: nt_fffff80000b95000.sys .
Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



On Sun 26.5.2013 0:41:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052613-19437-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600031066D)
Bugcheck code: 0x50 (0xFFFFF900C0901CF0, 0x0, 0xFFFFF9600031066D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 22.5.2013 16:25:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052213-20872-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2800F4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002800F4, 0xFFFFF8800A296A50, 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 that cannot be identified at this time.



On Tue 14.5.2013 1:11:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051413-46909-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002D066D)
Bugcheck code: 0x50 (0xFFFFF900C3D2CCF0, 0x0, 0xFFFFF960002D066D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 6.5.2013 16:48:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050613-32791-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5713)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F5713, 0xFFFFF8800B117040, 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 that cannot be identified at this time.



On Sat 4.5.2013 0:25:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050413-47829-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5713)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000105713, 0xFFFFF88007A7E070, 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 that cannot be identified at this time.



On Thu 2.5.2013 16:19:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050213-19188-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC5713)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000115713, 0xFFFFF880087DD070, 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 that cannot be identified at this time.

[Advertisements]

Most obvious choice is faulty memory so that is where I want to start.


A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[rshaffer61]

Most obvious choice is faulty memory so that is where I want to start.


A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.