BSOD ntoskrnl.exe+7500c00

[endgame86]

Any ideas?

==================================================
Dump File         : 082413-25942-01.dmp
Crash Time        : 8/24/2013 5:49:52 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff87f`820aa58f
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`0328a59d
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\082413-25942-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,056
Dump File Time    : 8/24/2013 6:25:39 PM
==================================================

==================================================
Dump File         : 082413-55801-01.dmp
Crash Time        : 8/24/2013 4:56:19 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041287
Parameter 2       : 00000000`00004b00
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\082413-55801-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,056
Dump File Time    : 8/24/2013 4:58:23 PM
==================================================

==================================================
Dump File         : 082413-29608-01.dmp
Crash Time        : 8/24/2013 4:49:20 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`40008bf6
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`032f3b60
Caused By Driver  : SYMEVENT64x86.SYS
Caused By Address : SYMEVENT64x86.SYS+0
File Description  : Symantec Event Library
Product Name      : SYMEVENT
Company           : Symantec Corporation
File Version      : 12.9.3.1
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\082413-29608-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 276,056
Dump File Time    : 8/24/2013 4:51:22 PM
==================================================

[DaveLembke]

Have you tried Memtest86 on this system to make sure your memory is good. Also have you run any hard drive tests to make sure that your hard drive is healthy. (*Reason why i suggest checking your hard drive health is because if the hard drive is on its way out and virtual memory that is placed on the hard drive is troubled as a result of bad read/write conditions it will cause a memory type of error even though its hard drive sourced as the cause of the problem.) Most of the time its a memory stick that has an issue and can be corrected as easily as replacing the stick or removing it from the system and running with lesser memory. However sometimes a corrupt OS build can also give these errors because it is failing to handle the memory properly with its memory management and the fix then is a repair installation or clean installation after backing up important data to external drive and formatting the hard drive to build the system clean.

[endgame86]

Ran memtest 86 on individual sticks, no errors found.

Ran WD lifeguard, no issues found.

[patio]

Flakey PSU...borrow a known good one of the same or greater wattage and swap it in there to test...

Do not buy a cheapo replacement.

[Linux711]

Try safe mode and see if it still occurs.

[Linux711]

Flakey PSU...borrow a known good one of the same or greater wattage and swap it in there to test...

Do not buy a cheapo replacement.

I'm curious. How did you deduce that based on those logs? To me it could be any hardware component at this point. How did you figure that out?