BSOD Random error messages 2nd fresh install

[thebfm]

Yeah I did that last night. Shortly before the crash that caused me to have to use my disk to get back into windows. but i had it running for a few hours prior to that.

 

[Dave76]

Driver Verifier is designed to stress your drivers and force faulty ones to crash, it will also cause your system to run slower than usual.
Post the full crash reports when you get a couple of Driver Verifier enabled crashes, Run for 24 hours.
This will give us information on your drivers that we can use to find the cause.
If it crashes and won't boot, disable it in Safe Mode.

Run memtest86+ for 7 full passes, with all RAM cards installed.
Best to run overnight as depending on the amount of RAM you have may take several hours.
If you get any errors you can stop the test.
RAM - Test with Memtest86+

 

[thebfm]

So I had a nice 4 hours of stability and let that go to my head so of course stuff had to act up. I was hit with a double bsod the 2nd was after boot while my startup programs were still loading then when it had the screen up to load in safe mode anytime i touched a key on my wireless logitech usb keyboard it caused a reset. even caps lock did it. it only loaded past that when i let the 30 seconds go by to autoselect the option. So thats a new one.

By the way I haven't already said it, but thank you to ANYONE that helps at all with this even if you just load the thread and go away without posting. Thanks for any effort given.

Edit: Also i had it reset my bios since it failed to load and that option was prompted and reminded me I guess I overclocked my memory? Its 1600 but my motherboard loads it at 1333 unless i set it as 1600 I had forgotten that. Also during the bsod madness it loaded a black screen with white text that mentioned something about checksum I didn't catch it enough to recall what was said it was just one line of text.

 

[Dave76]

What did you do to set the RAM at 1600MHz?
SPD setting in BIOS?

Your last crashes:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Probably caused by : memory_corruption ( nt!MiLogPageAccess+dc )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x50_nt!MiLogPageAccess+dc
-------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29712 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!_??_::FNODOBFM::_string_+29712

Your crashes before these last two are the same as above.

Run memtest86+ for 7 full passes, with all RAM cards installed.
Best to run overnight as depending on the amount of RAM you have may take several hours.
If you get any errors you can stop the test and follow the testing procedure in the tutorial.
RAM - Test with Memtest86+

'checksum' may indicate file corruption.
Run a system file check - SFC /SCANNOW Command - System File Checker
Run it three times with re-boots after each run.

From your System Event Logs:
A few crashes that aren't showing up in your zip file.

Event[5112]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-10-08T21:06:32.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: SKYNET-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000034

Usual causes: Insufficient physical memory, Indexing, Device driver
Possible RAM issue.


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Hard to tell the cause of this one without a crash dump.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory

Event[5545]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2012-10-08T21:58:57.000
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: SKYNET-PC
  Description: 
Unable to produce a minidump file from the full dump file.

This is also indicating a possible RAM/memory issue.

 

[thebfm]

7 pass memtest found errors. pic included.

Edit: Forgot to mention that was with both sticks. So where do I go from here? Does this confirm memory or could it still be other things causing the memtest errors?

 

[Dave76]

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages (VDDNB Over Voltage) are.

Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Follow the testing procedure in the tutorial.
RAM - Test with Memtest86+

Sometimes errors can be corrected by making RAM setting adjustments.

 

[thebfm]

Ok here are screens of cpuz tabs. Ill update post with other stuff as i get it done in the coming minutes.

My voltages are all set to auto.

Also my motherboard has a program I always have up that monitors my temp and I have never seen this cpu go past 55C and i idle around 30-37C depending on the time of year.

 

[Dave76]

Those motherboard (all motherboards) utilities are known to not give accurate information and well known to cause system instability and crashes.
I recommend that you uninstall them all.

Did you run the System File Checker?

There are free programs that will give you all the info you need and won't cause your computer to crash.
For CPU core temps: Core Temp
For CPU core temps and other info: HWiNFO64 system Information

I'll need to get this information before we can try the setting adjustments.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages (VDDNB Over Voltage) are.

Download your motherboard manual: M4A77TD PRO
You need to select the VDDNB Over Voltage and change to 'Manual' to get the voltage reading, same with the other voltages.
When done, just exit your BIOS without saving, all the setting will be as they were before.

 

[thebfm]

File checker ran all 3 results were clean.

I am not sure what I am doing with the voltage and what my manual was for I need more info. The overage stuff is auto all i can do with then is manually input numbers in a field there is no manual option itself.

 

[thebfm]

Another crash while i was out.

 

[Dave76]

From your motherboard manual pg 2-11
View attachment 236168
Try selecting 'Normal' and see if it will show your the current voltage setting.
The manual link was so you could download it if you don't already have it, you will need it for reference when we make settings adjustments.

Let me know if you have any questions.

Last crash:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  [COLOR="red"]Defective hardware (particularly memory[/COLOR] - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Probably caused by : [COLOR="red"]memory_corruption[/COLOR] ( nt!MiEmptyPageAccessLog+dc )
IMAGE_NAME:  [COLOR="Red"]memory_corruption[/COLOR]
FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc

I need the voltage setting information in order to make the BIOS setting adjustments that will hopefully solve the crashes.
This has resolved many crashes like the ones you are having, with the requested info we can proceed.

According to your CPUZ snips, your RAM is in 'Single' channel mode, it should be in 'Dual' channel mode. This will give you more performance from the RAM.
This is due to the RAM cards being installed in the wrong motherboard slots.
Look in your motherboard manual pg 1-11.
You need to have one RAM card in channel A and one RAM card in channel B.
Make sure both RAM cards are in the Orange slots.

 

[thebfm]

Well I tried to mess with it and unless im in the wrong section its set as auto and the other thing that changes the option is trying numbers into it it doesnt hav ea seb menu with options to turn it to manual or see stats from it.

 

[Dave76]

Did you find page 2-11 in your motherboard manual?
Does the BIOS page look like the snip I posted above?

 

[thebfm]

I switched my ram to be side by side in orange and it wouldnt post. It powered up but no beep occurred not did my screen turn on. It was on and the hdd light would flicker off and on at a steady pace. Switched them back to a1 a2 to boot again.

I noticed my manual mentions 1600 ram and using the black dlots tried that. It powered on but no beep hdd lights up once then then never again.

I have 2-11 and i see it in the bios but its not the same the manual says their are options for cpu voltave cor example as auto, manual +50 +100. In the bios i have ita on auto and the only way to change it is keypads + and - the first time i hit plus it goes to 1.15000 next time it goes to 1.15625 it continues with that size increase for a long time. Vddnb is the same situation but different numbers 0.80000 the. 0.80625 and so on.

 

[Dave76]

That is indicating a problem with your IMC (Integrated Memory Controller) which is part of your CPU.
Don't set your RAM to 1600MHz, this is a known AMD issue, you can try it later after you get the system stable.
Try them in the black slots with the RAM set at 1333MHZ to verify.

What setting did you change to get the RAM to 1600?

We might be able to get it working with the setting adjustments requested above.

Does you BIOS page look like this:
View attachment 236193
Set your VDDNB Over Voltage to 1.20v
Set your DRAM Frequency to 1333MHz
Set your Memory Over voltage to 1.60v
Leave the CPU Over Voltage on 'Auto' for now.
Exit & Save Changes.

Put the RAM in the orange slots, if it won't boot, put them back in A1 & A2, check if it will boot.

 

[thebfm]

I changed the dram frequency to 1600 to get it to 1600. And yeah thats what my bios looks like. I will change those setting shortly and let you know.

 

[thebfm]

Ok with those voltage and timing settings ram in black slots i booted up fine. Also i had to go over or unet the 1.6 setiing i went with 1.605 i hope thats ok/safe.

Guess i spoke too soon. Double bsod after windows boots while loading my start up programs the first one mentioned usb second i didnt see bsod screen just crash and rebooted on its own.

Switched ram to orange slots to see if im more or less stable then the black ones.

Edit: added pic of cpuz after memory was moved to orange and with volt and 1333 dram setting so far more stable then when I tried the black slots.

 

[thebfm]

a Lock up this time screen went black had to reset manually. While ram was in orange slots.

 

[Dave76]

Good news that it booted with the RAM in orange/black slots, hopefully this means the CPU IMC is not faulty.

The RAM voltage is fine if slightly higher.

The CPUZ snip information looks good.

Let's bump the same voltages again.
Set your VDDNB Over Voltage to 1.250v
Set your Memory Over voltage to 1.65v (slightly above is ok)
Leave the DRAM Frequency at 1333MHz and the RAM cards in the orange slots.
Exit & Save Changes.

Test for stability.


Your last crashes:

STOP 0x000000FE: BUGCODE_USB_DRIVER
Usual causes:  USB device driver
IMAGE_NAME:  usbohci.sys
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollAsyncEndpoint+99
Type referenced: usbport!_DEVICE_EXTENSION
-----------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : hardware ( Rt64win7+9403f )
IMAGE_NAME:  hardware
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Rt64win7.sys
-----------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDelayDerefKCBWorker+81

What USB devices are you using?
This may be cause by the RAM, either incompatible or needs more adjustments.

 

[thebfm]

usb microsoft mouse logitech wireless keyboard i have a logitech g13 and usb logitech headset as well as a usb hub that has the g13 mouse and headset going through that.