Random BSOD and no more beep codes during boot up

[ruthless1]

I booted up my PC recently and it made 2 fast beeps. Now whenever I boot it up, there arent any beeps at all, but there is supposed to be just one. I looked up what 2 beeps means, and it means "Parity error - bad memory". So what exactly does that mean? And what should I do? I tried to test all the ram and ram slots separately, and everything seems to boot up fine. Also I have been getting random BSOD, for some reason no dump file is created, but I did get a picture.

Computer type PC/Desktop
System Manufacturer/Model Number Custom
OS Windows 7 x64 Ultimate
CPU Intel i5 4690k
Motherboard MSI Z97 Gaming 7
Memory 12GB
Graphics Card NVIDIA GeForce GTX 960

 

[ICIT2LOL]

Hello and welcome Jeremy mate some system specs please
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html - very hard to work with soemting unknown.

Now you say you have some BSOD's and there is one posted in your thread but we need to see the dump files see these
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
&
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

The beep codes indicate something wrong with the memory as you suspect and I would suggest you first run a memtest http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html this is the only memtest we advise to use and it has to be run for at least 8 passes otherwise it is a waste of time - having said that if errors come up fairly soon or before 8 passes you can stop it and start testeing the different sticks and slots.


and for your info the beep codes can be different for different boards see link and that is part why we need to see some specs. Computer POST and beep codes

 

[ruthless1]

Computer type PC/Desktop
System Manufacturer/Model Number Custom
OS Windows 7 x64 Ultimate
CPU Intel i5 4690k
Motherboard MSI Z97 Gaming 7
Memory 12GB
Graphics Card NVIDIA GeForce GTX 960

I would upload the dump files, but my computer is not creating dump files for some reason, I looked in the folder and its empty. I had it set to create a minidump, but there is nothing, which is why I just uploaded a picture. I'll try out memtest and report back.

 

[BorisTheAnimal]

ruthless,

could you upload a picture of the dialog box when creating dump files?

 

[ruthless1]

Here you go, before this, I think it was set to kernel memory dump, but still made nothing.

 

[BorisTheAnimal]

Have you tried selecting the last option? The "complete memory dump" option?

 

[ruthless1]

There is not option for complete memory dump, only small or kernel.

 

[BorisTheAnimal]

There is not option for complete memory dump, only small or kernel.

Well hm that shouldn't be possible, the complete memory dump option should be available for all systems that have over 2GB of ram.

 

[ruthless1]

I thought that option was only for 2GB and under? Thats what it says on the link posted above.

 

[BorisTheAnimal]

I thought that option was only for 2GB and under? Thats what it says on the link posted above.

8. To have Windows Create a Complete memory dump File on BSOD
WARNING: See the NOTE box at the top of the tutorial for important information about the page file requirements for this type of dump file to be created. This option will not be available if you have 2GB or more of RAM installed.

No it says the complete opposite.

But either way something is definitely wrong here. What is the size of your paging file?

Because if the paging file on the boot drive is not large enough. To use the "Write Debugging Information To" feature to obtain a complete memory dump file, the paging file on the boot drive must be at least as large as physical memory + 1 MB. When you create a kernel memory dump file, the file is usually around one-third the size of the physical memory on the system. Of course, this quantity will vary, depending on your circumstances.

 

[ICIT2LOL]

Hmm am just wondering if ruthless should run that memtest - could be something out of whack there - just a guess/thought.

 

[axe0]

I wouldn't advice to configure complete memory dump, it is extremely large (10GB+) and most of it is user mode stuff.
In user mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.

In short words and simplified, a complete memory dump is unnecessary to configure with bluescreens because user mode can't ever cause a crash.

I would suggest to configure dumps to max kernel dump, it doesn't contain anything of user mode and is max 1GB.

 

[BorisTheAnimal]

I wouldn't advice to configure complete memory dump, it is extremely large (10GB+) and most of it is user mode stuff.
In user mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.

In short words and simplified, a complete memory dump is unnecessary to configure with bluescreens because user mode can't ever cause a crash.

I would suggest to configure dumps to max kernel dump, it doesn't contain anything of user mode and is max 1GB.

Yeah but he says that even if he configures max kernel dump, nothing is created upon crash.

 

[axe0]

That could be caused by other things too, like the pagefile size not properly configured or the Windows Error Reporting service isn't set to manual startup.

Please check following:
1. In the advanced options where you can edit the startup and recovery settings, please click on the settings of the performance and click on advanced tab in the pop-up.
What is the size of the virtual memory? It should be at least the size of your physical memory.

2. Please search "services.msc" (without quotes) and search for the service 'Windows Error Reporting Service'.
If the startup type is NOT manual, right click the service > properties and change the startup type to manual.

 

[ruthless1]

Okay, I ran memtest for at least 8 passes, nothing. I havent had a BSOD since the post, but I still dont know why I dont get a beep code anymore during startup, 1 beep means everythings fine right [For AMI BIOS]? As far as the virtual memory, it is around 12gb, and the 'Windows Error Reporting Service' is already set to manual. I updated my network drivers and video drivers, so maybe thats it? I dont know, the BSOD have been random, so I am not sure if I fixed whats going on.

 

[ICIT2LOL]

Ok if the memtest came up nothing then I am guessing it is ok and I would not be particularly worried about the beep on boot up. Sounds like whatever you have done since has as you say fixed something so just wait a nd see what happens and you know where we are if things go south again.