BSOD during a game and at startup

I also noticed that when I start up after turning off my computer for a while, it usually freezes as it loads up and restarts itself once then a couple of minutes after that, it BSOD to different kind of BSOD screens then usually fine after that. Right now I just started it up again after it was off for a while and it froze as soon as it was loading and had to manually restart the computer and as I was typing my issue on this post right now, it gave me a BSOD screen of a kind I haven't seen before, Memory management.

I'm starting to notice a trend here. I'm actually currently going to do the Driver Verifier. Hopefully I'll have new minidumps for you. Thanks again.

Update: Device Verifier on. When I restarted, my pc preformed a chkdsk and deleted alot of corrupted files and restored or orphaned certain files back or whatever that means. Just bits and pieces of information hoping that means anything.

XplicitMind said:

I also noticed that when I start up after turning off my computer for a while, it usually freezes as it loads up and restarts itself once then a couple of minutes after that, it BSOD to different kind of BSOD screens then usually fine after that. Right now I just started it up again after it was off for a while and it froze as soon as it was loading and had to manually restart the computer and as I was typing my issue on this post right now, it gave me a BSOD screen of a kind I haven't seen before, Memory management.

I'm starting to notice a trend here. I'm actually currently going to do the Driver Verifier. Hopefully I'll have new minidumps for you. Thanks again.

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

[QUOTE=zigzag3143;1704762]

XplicitMind said:

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

Oh that time the driver hasn't been enabled, which i attached a minidump of just a regular bsod, but now it is. I'm just waiting for something to act up.

EDIT: when i typed in verifier /query. it shows the cmd prompt but then quickly disappears. suppose to happen?

[QUOTE=XplicitMind;1704768]

zigzag3143 said:

XplicitMind said:

Inconclusive. Either verifier was not enabled or verifier did not catch a mis-behinvg drive.

You can check the status of verifier by typing verifier /query. It will tell you what drivers it is watching.

Oh that time the driver hasn't been enabled, which i attached a minidump of just a regular bsod, but now it is. I'm just waiting for something to act up.

EDIT: when i typed in verifier /query. it shows the cmd prompt but then quickly disappears. suppose to happen?

Apologies, try this

Okay I wake up this morning and it did the same thing again. It freezes at the BIOS screen then I would have to manually restart it. It goes to the desktop and after a few minutes, it would BSOD. special pool system memory management i believe. so I went to see if there was a minidump for it but I only see the one that was made from yesterday. Should my minidump be set up to kernal dump or small memory dump? does it make a difference? I believe it was the same one from yesterday, i couldnt get a minidump from that cause it didnt save.

my verifier is on but only one doesn't get loaded. i attached a picture for you to look at.

Usually after it freezes on the BIOS screen and BSOD's during the first few minutes, it doesnt BSOD again unless I play a game or something. But it gets so annoying to go through that. Like it messes up my PC more and more everytime it does it and I have no idea how to stop it.

XplicitMind said:

Okay I wake up this morning and it did the same thing again. It freezes at the BIOS screen then I would have to manually restart it. It goes to the desktop and after a few minutes, it would BSOD. special pool system memory management i believe. so I went to see if there was a minidump for it but I only see the one that was made from yesterday. Should my minidump be set up to kernal dump or small memory dump? does it make a difference? I believe it was the same one from yesterday, i couldnt get a minidump from that cause it didnt save.

my verifier is on but only one doesn't get loaded. i attached a picture for you to look at.

Usually after it freezes on the BIOS screen and BSOD's during the first few minutes, it doesnt BSOD again unless I play a game or something. But it gets so annoying to go through that. Like it messes up my PC more and more everytime it does it and I have no idea how to stop it.

OK verifier is checking drivers. DO you have any new DMP files?

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

XplicitMind said:

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

You can search for *.DM, and they are sometimes in c:\windows and may be called MEMORY.dmp

zigzag3143 said:

XplicitMind said:

I don't. The BSOD I just had said it wrote a DMP but I'm looking at the folder right now and it's not there. Can it be somewhere else?

EDIT: Noticed it was set to Kernal Memory Dump. I set it back to Small Memory Dump. Usually around this time I don't suffer any BSODs but when I do I'll post one up. I just woke next time it saves the next DMP.

You can search for *.DM, and they are sometimes in c:\windows and may be called MEMORY.dmp

This MEMORY.dmp file is over 400MB and it won't let me put it into a .zip

How can I go about this?