BSOD coming out of Sleep Mode

Hello and welcome txam92 now first of all could you please follow this as your specs are alittle thin on the ground
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
(pretyped to save time)


Now the dump file you refer to is very common and as you say is really of little help so what I would suggest is that you run these first if you haven't already



https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
https://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2 id there is nothing seen to be wrong and the problem persists run these


http://www.superantispyware.com/
http://www.malwarebytes.org/products/malwarebytes_free/
http://www.bleepingcomputer.com/download/adwcleaner/
ADW download from bleeping computer delete any rubbish found with the malware scans
NB If anyone who has Kaspersky as their security they may find it will not like ADW running and to stop the nagging just temporarily disbale the Kaspersky while one runs ADW



In the dumps I did see some references to memory and if the other scans do ot fix them then it might mean a memtest and not the Windows feature one it is quite basic and I can link you to the one we recommend but first things first.

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800034d2fb6, address which referenced memory

Sorry late reply tx mate now the Windows memtest really isn't up to the job and you should use the only test we recommend see this
Now to make absolutely we are on the same page the memtest linked here is the only one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM. RAM - Test with Memtest86+
(This is pretyped to save time)



Even if the machine now running ok it would be a good thing to do.

Ok I mean you don't have to but for the sake of running it overnight it at least will sow you if the RAM is ok should the BSOD' come up again