Random reboots when system is idle

[latinkreationz]

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? YES
- an OEM or full retail version? Retail OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 3 years old
- What is the age of OS installation (have you re-installed the OS? 3 months

 

[FredeGail]

Hello latinkreationz and welcome to Sevenforums.

Let's look at a few issues.

:ar:BSOD Report

Driver related summery

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003385378, fffff88003384bd0, fffff800031c09bc}

[B][COLOR="Red"]*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS[/COLOR][/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
----------------------
BugCheck 19, {20, fffff8a01525d110, fffff8a01525d130, 5020409}

*** WARNING: Unable to verify timestamp for [B][COLOR="red"]SRTSP64.SYS[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
*** WARNING: Unable to verify timestamp for EX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"][B]EX64.SYS[/B][/COLOR]
Probably caused by : SRTSP64.SYS ( SRTSP64+86261 )

• SRTSP64.SYS reports errors and is a part of the Symantec Real Time Storage Protection. If you purchased Norton you should check if you have the latest updates, if so, I'd recommend contacting Norton Costumer Service.
• EX64.SYS also reports errors which is also in relation to Norton Anti-virus.

As I said, if you wish to keep Norton, make sure it's updated, and if it is - take a look at Norton's website for Costumer Service.

If, for instance, you're having a Norton Trial, we recommend using MSSE, and uninstall Norton using their uninstaller utility.

Best Regards,
Frederik.

 

[latinkreationz]

Thanks for checking so quickly! Now that I know it's Norton, I will move forward from there. I'm using Norton 360 v5 and it's all up to date. I'll check with them.

 

[FredeGail]

Thanks for checking so quickly! Now that I know it's Norton, I will move forward from there.

Sounds good Latinkreationz, I'm deeply sorry if you used money on this software, it's not supposed to work this way.

Second step: BCCode (1a)
You have had the bugcheck code, 1a, which usually indicates a failed device driver, or a memory failure. As a second step and when you're done diagnosing Norton, download a copy of Memtest86+ and do 7 to 8 passes it.

Memtest86+ - Advanced Memory Diagnostic Tool

Bugcheck

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800064a400
Arg3: 000000000000ffff
Arg4: 0000000000000000

Best Regards,
Frederik.