Sign in with
Sign up | Sign in
Your question
Solved

Help Bsod allday

Last response: in Memory
Share
August 29, 2013 3:00:28 PM

Hey my computer keeps BSOD and when i run who crashed it this is what i get
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 8/29/2013 9:56:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-6052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004AF8BF0, 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 that cannot be identified at this time.



On Thu 8/29/2013 9:56:20 PM 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: 0x1A (0x41790, 0xFFFFFA8004AF8BF0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 8/29/2013 9:50:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-5428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8008EECC50, 0xFFFFF8800B6E6000, 0xFFFFF8A00395B0BE)
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 8/29/2013 9:48:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-5366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x22E0, 0xAD5F000045C8)
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
--------------------------------------------------------------------------------

4 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.

please help thanks xD

More about : bsod allday

a c 1943 } Memory
August 29, 2013 3:17:40 PM

What CPU, mobo and the MODEL # of your DRAM
m
0
l
Related resources
a c 1943 } Memory
August 29, 2013 3:28:04 PM

Try setting the DRAM Voltage to 1.55
m
0
l
August 29, 2013 3:53:48 PM

Tradesman1 said:
Try setting the DRAM Voltage to 1.55


in the bios?
m
0
l
a c 1943 } Memory
August 29, 2013 4:03:26 PM

Yes, in the BIOS,
m
0
l
August 29, 2013 4:07:12 PM

Tradesman1 said:
Yes, in the BIOS,


kk it only let me go to 1.560v and when i did that it started and then bsod and restarted like 6 times in a row then now its running again. Should i memtest? i havent downloaded any drivers recently so i dont think its a software problem. Could it be that my ram's just dying?
m
0
l

Best solution

a c 1943 } Memory
August 29, 2013 4:15:42 PM

Possible, try running with each stick individually
Share
August 29, 2013 4:18:09 PM

Tradesman1 said:
Possible, try running with each stick individually


kk im memtest and swap ram with my buddy to see if that works 2night. Thanks for your help! ill pick yours as best answer once the solution is resolved. Worst case scenario im just gonna replace my ram xD
Thanks!
m
0
l
a c 1943 } Memory
August 29, 2013 5:19:39 PM

Keep me updated ;) 
m
0
l
August 29, 2013 6:59:22 PM

Tradesman1 said:
Keep me updated ;) 


so this is what happend. pulled out one stick of ram started up. Bsod. Facepalmed T___T
turned it off. Pulled out the other stick and put in the one i pulled out.
its been an hour no bsod. i can play league of legends and no bsod still 2 scared to rank for fear of bsod.
computer is using 3gb of my 4 on that one stick.

current plan is 2morow going to fry's and buying 2 8sticks of ram 16 total and replacing it.

praying all is well so come midnight monday i can indulge myself in rome 2 without any bsod.

ah i pray no bsod rest of the nightt or ima cry. T___T lol
m
0
l
a c 1943 } Memory
August 29, 2013 7:06:57 PM

Keep me updated, bad stick is too bad, but get a good SET of 2x8GB ;)  (Don't buy individual sticks, may cost a bit less, but can also be problematic)
m
0
l
August 29, 2013 9:28:42 PM

Tradesman1 said:
Keep me updated, bad stick is too bad, but get a good SET of 2x8GB ;)  (Don't buy individual sticks, may cost a bit less, but can also be problematic)

yeah its been like 3 hours and no bsod. Its fine ima get the same sticks but the 8gb a stick version. Might as well upgrade before rome haha. Now i just need to learn to OC my cpu before rome comes out lol. Thanks for all your help bro ! i appreciate it!
m
0
l
!