Sign in with
Sign up | Sign in
Your question

BSOD here is crash dump info

Last response: in Windows 7
Share
June 13, 2013 12:14:56 AM

So ive been getting BSOD alot today.. heres the dump info, what would the problem be? what to do?






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.

More about : bsod crash dump info

June 13, 2013 1:42:57 AM

Windows7user said:
So ive been getting BSOD alot today.. heres the dump info, what would the problem be? what to do?


It looks like a virus, RAM problem, driver corruption or some other hardware problem.

Please write your systems specs (brands and models of components), what OS and what antivirus you are using.
m
0
l
June 13, 2013 1:58:16 AM

djfv said:
Windows7user said:
So ive been getting BSOD alot today.. heres the dump info, what would the problem be? what to do?


It looks like a virus, RAM problem, driver corruption or some other hardware problem.

Please write your systems specs (brands and models of components), what OS and what antivirus you are using.


Microsoft Windows 7 Professional 64bit
Inter Core I5 760 QuadCore
ATI Radeon HD 5670
2x Kingston 2GB DDR-1333 DDR3 SDRAM
Samsung 1TB Hard Drive
P7P55-M Motherboard

Is that ok or anything else?

Im not using any anti virus..
m
0
l
Related resources
June 13, 2013 2:16:26 AM

Windows7user said:
djfv said:
Windows7user said:
So ive been getting BSOD alot today.. heres the dump info, what would the problem be? what to do?


It looks like a virus, RAM problem, driver corruption or some other hardware problem.

Please write your systems specs (brands and models of components), what OS and what antivirus you are using.


Microsoft Windows 7 Professional 64bit
Inter Core I5 760 QuadCore
ATI Radeon HD 5670
2x Kingston 2GB DDR-1333 DDR3 SDRAM
Samsung 1TB Hard Drive
P7P55-M Motherboard

Is that ok or anything else?

Im not using any anti virus..


Please, also write your power supply brand/model.

1. Download free AVG antivirus from:
free.avg.com

(AVG has some unnecessary components/functions, but if they bother you, you can remove them later).

2. Install, update and run complete system scan (there is a button "scan now").

3. Check for viruses and remove them if found.

4. Install malwarebytes (free version)

http://www.malwarebytes.org/

5. Update, scan and remove malware.

Afterwards, report here your findings.
m
0
l
June 13, 2013 4:01:49 AM

This isn't working... I can't scan it at all.. 2 times already the same thing.. its scanning way too long and i get blue screen between it.
m
0
l
June 13, 2013 4:22:14 AM

Windows7user said:
This isn't working... I can't scan it at all.. 2 times already the same thing.. its scanning way too long and i get blue screen between it.


Hmmmm. How about to try and use System restore to an earlier state when there were no BSODs and then try to install and run antivirus?

But before that do this:
1. click start button
2.in search box type "cmd"
3. right click on the CMD icon and click "run as administrator" > yes
4. type:
sfc /scannow
5.press enter

There are some serious corruptions going on. This will probably take a lot of effort.

I think that the smartest thing would be to backup your data to an external device, which you should scan afterwards on another PC for viruses. And then format and reinstall the OS.

Such errors are caused by corrupted system files, bad drivers or faulty hardware.
The idea is to first check for viruses, check for system problems and then reinstall drivers.
m
0
l
June 13, 2013 4:41:50 AM

I would like to avoid format if possible, only as last resort.. i have so much things that would take ages to back up.

it said : windows resource protection did not find any integrity violations.

So next step? System restore and try to scan again?
m
0
l
June 13, 2013 5:02:59 AM

Windows7user said:
I would like to avoid format if possible, only as last resort.. i have so much things that would take ages to back up.

it said : windows resource protection did not find any integrity violations.

So next step? System restore and try to scan again?


So the system itself is not corrupted, which is good. Now for viruses and drivers.

So, yes. Restore to a date before BSODs. It might also remove the antivirus you installed today- if so, install AVG and Malwarebytes again and scan. Please report if you are successful.
m
0
l
June 13, 2013 5:42:50 AM

So far so good its still scanning..
Meanwhile I find one thing a bit odd, why is my ram consumption 3300mb, and im not really doing anything much yet its still 3300mb out of 4000..
When i go to processes nothing is really taking up much ram so it should really be much less.
m
0
l
June 13, 2013 5:47:38 AM

Windows7user said:
So far so good its still scanning..
Meanwhile I find one thing a bit odd, why is my ram consumption 3300mb, and im not really doing anything much yet its still 3300mb out of 4000..
When i go to processes nothing is really taking up much ram so it should really be much less.


Something is eating up your RAM. Could be the antivirus scan, but it is still quite high. Be sure to go to processes in Windows start manager, click the memory tab (in order to arrange by consumption) and write what is consuming the highest.
m
0
l
June 13, 2013 6:08:11 AM

I got BSOD again between the scan.
So I guess we can't rule out viruses under these circumstances, so moving on how can i rule out drivers and hardware then?
Btw my computer is also running quite slow atm, laggy etc.. been having this problem for a while aswell but it came and went.
m
0
l
June 13, 2013 6:16:01 AM

Windows7user said:
I got BSOD again between the scan.
So I guess we can't rule out viruses under these circumstances, so moving on how can i rule out drivers and hardware then?
Btw my computer is also running quite slow atm, laggy etc.. been having this problem for a while aswell but it came and went.


Try to scan with AVG and Malwarebytes in safe mode- restart and keep pressing f8 and choose safe mode. Let's see what happens then.
m
0
l
June 13, 2013 11:01:52 AM

djfv said:
Windows7user said:
I got BSOD again between the scan.
So I guess we can't rule out viruses under these circumstances, so moving on how can i rule out drivers and hardware then?
Btw my computer is also running quite slow atm, laggy etc.. been having this problem for a while aswell but it came and went.


Try to scan with AVG and Malwarebytes in safe mode- restart and keep pressing f8 and choose safe mode. Let's see what happens then.


Ok, it worked in safe mode, scanned with both, removed some threats aswell.

What now? Just wait and see if I get BSOD again?
m
0
l
June 13, 2013 11:07:49 AM

Btw my game still runs in super slow motion, and its waaaaaaay bellow my specs.
m
0
l
June 13, 2013 11:33:22 AM

Windows7user said:
djfv said:
Windows7user said:
I got BSOD again between the scan.
So I guess we can't rule out viruses under these circumstances, so moving on how can i rule out drivers and hardware then?
Btw my computer is also running quite slow atm, laggy etc.. been having this problem for a while aswell but it came and went.


Try to scan with AVG and Malwarebytes in safe mode- restart and keep pressing f8 and choose safe mode. Let's see what happens then.


Ok, it worked in safe mode, scanned with both, removed some threats aswell.

What now? Just wait and see if I get BSOD again?


First begin with reinstalling the drivers. All of them.
1. Go to the motherboard website and reinstall audio, lan and sata drivers. Leave chipsets alone, for now. They are quite touchy and reinstalling them might cause problems.
http://www.asus.com/Motherboards/P7P55M/#support_Downlo...

2.Then download driver sweeper:
http://www.guru3d.com/content_page/guru3d_driver_sweepe...

3.Uninstall graphics (ATI) from the control panel.

4. Go into safe mode. Driver sweeper should be used in safe mode- if you need instructions, they can be found here:
http://www.overclock.net/t/651378/how-to-install-driver...

5.Then reinstall fresh ATI drivers in regular Windows (not safe mode).
http://support.amd.com/us/gpudownload/windows/Pages/aut...

Well, that should be for the start.
m
0
l
June 13, 2013 12:28:52 PM

I did for LAN and for Audio.

Sata doesn't want, it says the computer doesnt meet the minimum requirements so install will close lol.

Going to do video drivers now.
m
0
l
June 13, 2013 1:28:07 PM

Ok did video drivers now.

Games and all still running slow motion.

What now? Im starting to think this might be some hardware thats doing this.
m
0
l
June 13, 2013 2:04:05 PM

Windows7user said:
Ok did video drivers now.

Games and all still running slow motion.

What now? Im starting to think this might be some hardware thats doing this.


Well, I also heard that these problems might be caused by bad BIOS.

http://www.asus.com/Motherboards/P7P55M/#support_Downlo...

Download and update to the newest bios (version 1101). Now, you must be careful. Use bupdater tool in bious utilities section- here's the tutorial:
http://www.youtube.com/watch?v=6vr4y8rUNXA

Please be careful.

If the new bios doesn't help, I think that you should check if the RAM is faulty with memtest:
http://www.memtest86.com/download.htm

But before that- is the memory consumption still high in Task manager? Have you checked and clicked on memory tab in processes to arrange all of them?
m
0
l
June 13, 2013 2:30:13 PM

Memory is normal, it must have been anti virus program.
Will that bios thing delete the files on my usb drive? also how do I type those signs in cmd like / ~ .. the ones u need shown in that vid
m
0
l
June 13, 2013 2:42:08 PM

Windows7user said:
Memory is normal, it must have been anti virus program.
Will that bios thing delete the files on my usb drive? also how do I type those signs in cmd like / ~ .. the ones u need shown in that vid


First- empty your usb.
Secondly, make the usb bootable by using this program :
http://rufus.akeo.ie/

Then, copy bios files to your usb drive as shown in that video and then restart into dos, also as shown in the video.
m
0
l
June 13, 2013 3:26:24 PM

djfv said:
Windows7user said:
Memory is normal, it must have been anti virus program.
Will that bios thing delete the files on my usb drive? also how do I type those signs in cmd like / ~ .. the ones u need shown in that vid


First- empty your usb.
Secondly, make the usb bootable by using this program :
http://rufus.akeo.ie/

Then, copy bios files to your usb drive as shown in that video and then restart into dos, also as shown in the video.


Computer still acting the same.
m
0
l
June 14, 2013 12:58:04 AM

Windows7user said:
djfv said:
Windows7user said:
Memory is normal, it must have been anti virus program.
Will that bios thing delete the files on my usb drive? also how do I type those signs in cmd like / ~ .. the ones u need shown in that vid


First- empty your usb.
Secondly, make the usb bootable by using this program :
http://rufus.akeo.ie/

Then, copy bios files to your usb drive as shown in that video and then restart into dos, also as shown in the video.


Computer still acting the same.


You successfully upgraded to the newest bios? Did you choose fail-safe (default) options in BIOS?
What did memtest say?
m
0
l
a b $ Windows 7
June 14, 2013 6:19:07 AM

Looks like RAM, though CRITICAL_STRUCTURE_CORRUPTION isn't one of the more common RAM related BSOD's...

I'd run memtest86+ before doing anything else; every BSOD can occur due to memory corruption, so lets rule a bad stick of RAM out before doing anything else.
m
0
l
June 14, 2013 8:56:02 AM

djfv yes I did as you said.

Ive ran memtest indeed and it passed, there was no errors at all.
m
0
l
June 14, 2013 9:55:56 AM

RECAP of what i did so far:

-scanned pc with AVG
-scanned pc with Malwarebyts
-Reinstalled, audio, lan and video drivers
-Updated bios
-Scanned RAM with memtest
m
0
l
June 14, 2013 4:30:29 PM

Windows7user said:
RECAP of what i did so far:

-scanned pc with AVG
-scanned pc with Malwarebyts
-Reinstalled, audio, lan and video drivers
-Updated bios
-Scanned RAM with memtest


How do you mean scanned woth memtest? Only once? It should run for a few hours- or perfectly- all night.
My remaining ideas:
-Check RAM thoroughly.
-Check GPU (could be faulty).
-If nothing else- reinstall OS.
m
0
l
!