Sign in with
Sign up | Sign in
Your question

Bsod

Last response: in Windows 7
Share
November 2, 2012 10:20:34 PM

hi guys i just had my first build and everything seems to work fine but alot of times im getting blue screen of death.

here is the info

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000008887
BCP2: FFFFFA8001A3B0B0
BCP3: FFFFFA8001A32080
BCP4: 0000000000000500
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\110212-26286-01.dmp
C:\Users\Shawn\AppData\Local\Temp\WER-652801-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt




Plz help im really worried

More about : bsod

a b $ Windows 7
November 2, 2012 11:15:04 PM

Duplicate post , a second post is not needed and serves to confuse and split up the responses. Here is the answer I gave on the other one in case no one answers the other one.

The infamous blue screen of death , is probably the most baffeling thing that Windows has and is totaly useless to most people because it's impossable to read and under stand one. You would think that thay could come up with a much easier thing to read and give information we can understand so we can fix what is wrong.
This download is a nice little program that can help with understanding the BSOD. It's not 100% but I have used it and it's been helpfull.

http://download.cnet.com/WhoCrashed/3000-2094_4-7520582...
m
0
l
November 2, 2012 11:25:35 PM

inzone said:
Duplicate post , a second post is not needed and serves to confuse and split up the responses. Here is the answer I gave on the other one in case no one answers the other one.

The infamous blue screen of death , is probably the most baffeling thing that Windows has and is totaly useless to most people because it's impossable to read and under stand one. You would think that thay could come up with a much easier thing to read and give information we can understand so we can fix what is wrong.
This download is a nice little program that can help with understanding the BSOD. It's not 100% but I have used it and it's been helpfull.

http://download.cnet.com/WhoCrashe [...] 05821.html





umm srry just really worried and your link is dead but i will try to find it
m
0
l
Related resources
Can't find your answer ? Ask !
November 2, 2012 11:29:52 PM

k i got it and it cant find which driver is screwed up im going to use slim drivers and install everything ty any way
m
0
l
a b $ Windows 7
November 2, 2012 11:31:11 PM

The program is called Who Crashed and all you have to do is a Google search and you'll find it.
m
0
l
November 2, 2012 11:44:02 PM

i know and i got it, look at the results:


System Information (local)
--------------------------------------------------------------------------------

computer name: SHAWN-GAMING-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8526299136 total
VM: 2147352576, free: 1928384512




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 11/2/2012 11:05:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110212-26286-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA8001A3B0B0, 0xFFFFFA8001A32080, 0x500)
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 that cannot be identified at this time.



On Fri 11/2/2012 11:05:17 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7F53F)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA8001A3B0B0, 0xFFFFFA8001A32080, 0x500)
Error: MEMORY_MANAGEMENT
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 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 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 Fri 11/2/2012 8:44:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110212-23634-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x99, 0x1A6C3B, 0x5, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/2/2012 12:45:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-28969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x403, 0xFFFFF680002A0758, 0xB8F0000057200867, 0xFFFFF680002A0748)
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 that cannot be identified at this time.



On Thu 11/1/2012 11:51:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-26005-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x403, 0xFFFFF680002E5198, 0x9A900001DE355867, 0xFFFFF680002E5188)
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 that cannot be identified at this time.



On Wed 10/31/2012 4:08:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-37034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x8887, 0xFFFFFA800330FF00, 0xFFFFFA8004189BC0, 0x602)
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 that cannot be identified at this time.




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

6 crash dumps have been found and analyzed. 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.



m
0
l
a b $ Windows 7
November 2, 2012 11:52:15 PM

You may have either a bad stiuick of memory or the system memory is not sufficient and you need to increase the virtual memory ( page file ). You should download and run memtest86 and see if you have any bad ram sticks.
m
0
l
November 2, 2012 11:59:27 PM

i checked my ram with win 7 memory diagnostic or whatever no errors said im good to go, and i think i have enough i have 8gb 1333mhz its a new build and i put borderlands 2 on and i can run it between 60-120fps, so i doubt that any hardware is malfunctioning.

what do you mean about the page file?
m
0
l
a b $ Windows 7
November 3, 2012 1:34:33 AM

It's called virtual memory and Windows takes an amount of hard drive space and uses it as virtual memory and it's commonly refered to as a page file. Windows usually takes drive space the size of the ram that's installed and it can actually be slower than ram because it's hard drive space. I have 16gb of ram so I set my page file to 0 so that forces Windows to use the ram and not hard drive space.
Memtest86 is a much better test for the ram than the Windows diagnostic but it's your decision to do the test that you want but the reports from the BSOD desription said something about memory corruption so I would be investigating everything about the memory on your computer.
m
0
l
a b $ Windows 7
November 3, 2012 2:27:48 AM

You probably have bad memory and as has been said before you should download and run memtest86 for at least three passes. You should also check your integrity of your hard drive, either from explore tools or "CHKDSK /F" Also run from the command prompt as the administrator "SFC /scannow" if you find any errors with SFC then they are probably due to memory problems.
m
0
l
November 3, 2012 5:53:37 PM

inzone said:
It's called virtual memory and Windows takes an amount of hard drive space and uses it as virtual memory and it's commonly refered to as a page file. Windows usually takes drive space the size of the ram that's installed and it can actually be slower than ram because it's hard drive space. I have 16gb of ram so I set my page file to 0 so that forces Windows to use the ram and not hard drive space.
Memtest86 is a much better test for the ram than the Windows diagnostic but it's your decision to do the test that you want but the reports from the BSOD desription said something about memory corruption so I would be investigating everything about the memory on your computer.



here is wat bluescreen view says and i will try memtest86


110312-22557-01.dmp 11/3/2012 11:28:27 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`0006b8c8 fdf00002`0a4ad867 fffff680`0006b8d8 nvlddmkm.sys nvlddmkm.sys+bd76f x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110312-22557-01.dmp 4 15 7601 293,560
110312-19952-01.dmp 11/3/2012 7:10:32 AM POOL_CORRUPTION_IN_FILE_AREA 0x000000de 00000000`00000002 fffff8a0`0379df88 fffff8a0`0379df99 00000002`077558c0 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110312-19952-01.dmp 4 15 7601 293,608
110312-25615-01.dmp 11/3/2012 5:52:11 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`00008e18 76000001`a3355847 fffffa80`084d3cd0 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110312-25615-01.dmp 4 15 7601 286,520
110212-26286-01.dmp 11/2/2012 4:06:44 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00008887 fffffa80`01a3b0b0 fffffa80`01a32080 00000000`00000500 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110212-26286-01.dmp 4 15 7601 287,632
110212-23634-01.dmp 11/2/2012 1:45:36 PM PFN_LIST_CORRUPT 0x0000004e 00000000`00000099 00000000`001a6c3b 00000000`00000005 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110212-23634-01.dmp 4 15 7601 284,632
110112-28969-01.dmp 11/1/2012 5:46:48 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`002a0758 b8f00000`57200867 fffff680`002a0748 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110112-28969-01.dmp 4 15 7601 293,552
110112-26005-01.dmp 11/1/2012 4:52:21 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`002e5198 9a900001`de355867 fffff680`002e5188 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\110112-26005-01.dmp 4 15 7601 293,552
103112-37034-01.dmp 10/31/2012 9:09:39 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00008887 fffffa80`0330ff00 fffffa80`04189bc0 00000000`00000602 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\103112-37034-01.dmp 4 15 7601 288,976
m
0
l
!