Frequent BSOD's

#1

toastythomas

0 Frags – +

So recently, I have been receiving a BSOD on a semi daily basis, and each being caused by win32k.sys. So far, I have only been receiving the SYSTEM_SERVICE_EXCEPTION and MEMORY_MANAGEMENT errors. If anyone has a solution for these errors, it would be appreciated.

#2

pazer

0 Frags – +

Run memory diagnostics?

#3

phAZE

2 Frags – +

Yeah checking your ram is prob a good place to start. try running a program like memtest86 for a few hours and see if you get any errors. If you do, you have faulty ram.

#4

STONE

1 Frags – +

Most computers have built in diagnostics that you can run in POST, it's preferred that you use that. I recommend looking up your pc manufacturer and figure out how to get to them. Run those and see what's wrong. Memory_Management is a RAM error so it's most likely faulty RAM.

#5

goldfish

0 Frags – +

yea p. much what saraswati said, you need to run memory diagnostics

#6

wareya

0 Frags – +

uninstall non-microsoft drivers, except graphics, see what happens
the legacy DA drivers cause me to bluescreen occasionally

#7

samjain98

0 Frags – +

.

#8

toastythomas

0 Frags – +

pazerRun memory diagnostics?

No results were detected, but I will run future tests to see if the problem persists.

[quote=pazer]Run memory diagnostics?[/quote]
No results were detected, but I will run future tests to see if the problem persists.

#9

Hidi

0 Frags – +

I'd suggest Blue Screen Viewer for checking dump logs on BSODs. (http://www.nirsoft.net/utils/blue_screen_view.html)
I don't know how to help you, but when I was getting lots of BSODs, I found Blue Screen Viewer useful since it was able to tell me more specifically what processes caused the BSOD than Windows alone.

#10

toastythomas

0 Frags – +

HidiI'd suggest Blue Screen Viewer for checking dump logs on BSODs. (http://www.nirsoft.net/utils/blue_screen_view.html)
I don't know how to help you, but when I was getting lots of BSODs, I found Blue Screen Viewer useful since it was able to tell me more specifically what processes caused the BSOD than Windows alone.

Thanks. The next time I blue screen, I will put the cause as soon as possible on this thread.

[quote=Hidi]I'd suggest Blue Screen Viewer for checking dump logs on BSODs. (http://www.nirsoft.net/utils/blue_screen_view.html)
I don't know how to help you, but when I was getting lots of BSODs, I found Blue Screen Viewer useful since it was able to tell me more specifically what processes caused the BSOD than Windows alone.[/quote]
Thanks. The next time I blue screen, I will put the cause as soon as possible on this thread.

#11

Dave_

1 Frags – +

also sfc /scannow can't hurt; it basically verifies your system files

#12

toastythomas

2 Frags – +

Thanks to the help of Dave_, I found out that resetting my BIOS settings could help solve this problem.

If anyone has any similar problems, be sure to check out these two links.

http://www.overclock.net/t/1339557/a-year-of-bsods-mostly-ntoskrnl-exe

http://superuser.com/questions/452290/windows-7-recurring-blue-screens-memory-management-0x1a

Thanks to the help of Dave_, I found out that resetting my BIOS settings could help solve this problem.

If anyone has any similar problems, be sure to check out these two links.

http://www.overclock.net/t/1339557/a-year-of-bsods-mostly-ntoskrnl-exe

http://superuser.com/questions/452290/windows-7-recurring-blue-screens-memory-management-0x1a

#13

toastythomas

0 Frags – +

well this temporarily fixed my problem, but i'm now getting stop error 0x1a, 0x50, 0xf7, or 0x3b either after a couple hours of usage, or whenever i just simply boot up