Windows 7: BSOD's new computer build even when idle

djdrock · 02 Jul 2012

Windows 7 x64 Full Retail
The hardware is brand new with the exception of a SATA hard drive I use for backup.
OS was installed a few weeks ago.

System specs: (Ignore the ones listed in my profile. The ones below are for the computer I am having issues with now which is a work computer)

Code:

Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz
ASUSTeK COMPUTER INC. P8H61-M LX PLUS
BIOS Date: 05/11/12 14:38:52 Ver: 41.04
8.00 GB Gskill Ripjaws (2x4gb) DDR3 1333 RAM.  Model F3-10666CL9D-8GBRL
(1) Hitachi HDS721050CLA362 ATA Device   (2) ST3500514NS ATA Device
(1) High Definition Audio Device   (2) High Definition Audio Device   (3) High Definition Audio Device   (4) Realtek High Definition Audio   (5) High Definition Audio Device
NVIDIA GeForce 210
Microsoft Windows 7 Ultimate  64-bit 7601 Multiprocessor Free Service Pack 1

This is a brand new system. I started getting BSOD's after the first couple of days. I ran memtest86 for 5 days straight, no errors. I also ran windows memory diagnostics. No issues reported. I have the latest BIOS update to the mobo, and I believe all of my drivers are up to date.

If I let the computer just run idle, after a few days, I am getting a BSOD, but the description, as you will see, is changing. I have almost no software installed on this computer.

I would appreciate any help that you experts can give.

Thanks,

David

DellRiyazuddinM · 02 Jul 2012

Hi,
My name is Riyaz and I work for the Social Media and Community Team at Dell.

I am trying to understand a few things here, Please answer the following questions.

1. Is your computer connected to the internet (wired or wireless)?
2. Have you done a reinstallation of windows (if so is it a clean install or a dirty install)
3. Is your computer running (ON) continuously for days or you have the sleep, hibernate options (ON)

Regards
Dell_Riyazuddin_M

**yowanvista** · 02 Jul 2012

This is pretty straightforward, your problems are being caused by an Acrnois Software (probably True Image).

The product seems to be outdated as most of its drivers date back to 2011. You should upgrade to the latest build/2012-Version.

I also noted that an old Samsung printer driver, ssport.sys(2005) is installed on that system, such an obsolete driver may cause issues. You should update it.
http://www.samsung.com/ca/support/do...ownloadMain.do

Code:

snapman.sys        fffff880`01b9f000    fffff880`01bec000    0x0004d000    0x4db91905    28/04/2011 11:36:37

Code:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8089300b30, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88001bc652b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS:  fffffa8089300b30 

FAULTING_IP: 
snapman+2752b
fffff880`01bc652b 488910          mov     qword ptr [rax],rdx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  TrueImageHomeS

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880070aa380 -- (.trap 0xfffff880070aa380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8089300b30 rbx=0000000000000000 rcx=fffffa8009300b30
rdx=fffffa800d017298 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001bc652b rsp=fffff880070aa518 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
snapman+0x2752b:
fffff880`01bc652b 488910          mov     qword ptr [rax],rdx ds:9010:fffffa80`89300b30=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e25f1f to fffff80002e7f1c0

STACK_TEXT:  
fffff880`070aa218 fffff800`02e25f1f : 00000000`00000050 fffffa80`89300b30 00000000`00000001 fffff880`070aa380 : nt!KeBugCheckEx
fffff880`070aa220 fffff800`02e7d2ee : 00000000`00000001 fffffa80`89300b30 fffffa80`06997700 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x43d51
fffff880`070aa380 fffff880`01bc652b : fffff880`01bc0459 ffffd8f0`00002710 fffff880`01bc1f21 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070aa518 fffff880`01bc0459 : ffffd8f0`00002710 fffff880`01bc1f21 00000000`00000000 00000000`00000001 : snapman+0x2752b
fffff880`070aa520 ffffd8f0`00002710 : fffff880`01bc1f21 00000000`00000000 00000000`00000001 00000000`00000000 : snapman+0x21459
fffff880`070aa528 fffff880`01bc1f21 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`09300ad8 : 0xffffd8f0`00002710
fffff880`070aa530 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`09300ad8 fffffa80`0a839010 : snapman+0x22f21


STACK_COMMAND:  kb

FOLLOWUP_IP: 
snapman+2752b
fffff880`01bc652b 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  snapman+2752b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME:

Post back with newer dump files if you experience more BSODs.

djdrock · 05 Jul 2012

I completely removed Acronis and rebooted, however, I got another BSOD. I have attached an updated log for your review as "reports updated.zip"

Thanks again,

David

**yowanvista** · 06 Jul 2012

Quote: Originally Posted by djdrock

I completely removed Acronis and rebooted, however, I got another BSOD. I have attached an updated log for your review as "reports updated.zip"

Thanks again,

David

Your issues are Memory Related. I believe that either some RAM settings are incorrectly set in your BIOS or the RAM itself may be malfunctioning. Try running your system with only one RAM stick.

djdrock · 16 Jul 2012

Well I hate to jump too early, but I have not had a single BSOD since removing one of my two DIMMS.

I am using G.Skill F3-10666CL9D-8GBRL memory, which I thought would work. The approved vendor list does not list it, but rather G.SKILL F3-10666CL8D-4GBECO(XMP) 4GB(2 x 2GB).

Evidently it is ultra important to use approved memory that matches perfectly. Does the issue I am having sound like a memory compatibility issue that would only be caused using 2x4gb insteand of a single 4gb DIMM?

Thanks again,

David

**yowanvista** · 17 Jul 2012

Quote: Originally Posted by djdrock

Well I hate to jump too early, but I have not had a single BSOD since removing one of my two DIMMS.

I am using G.Skill F3-10666CL9D-8GBRL memory, which I thought would work. The approved vendor list does not list it, but rather G.SKILL F3-10666CL8D-4GBECO(XMP) 4GB(2 x 2GB).

Evidently it is ultra important to use approved memory that matches perfectly. Does the issue I am having sound like a memory compatibility issue that would only be caused using 2x4gb insteand of a single 4gb DIMM?

Thanks again,

David

It is always recommended to use approved memory which has been tested by the mainboard manufacturer as being fully compatible. Others may or not work depending on their configuration. In your case the problem may be related to the board not supporting that specific 4GBx1 stick.

djdrock · 25 Jul 2012

Well, it appears I spoke to early. I have gone over 3 weeks without a BSOD, but got one again today, but different this time with ntfs.sys. Again, this computer has been running idle. I was just about to bring it live to our main server PC at work, then this happened. I am attaching an updated file for your perusal.

I did run a full chkdsk, and no errors were reported.

Thanks,

David

**yowanvista** · 26 Jul 2012

Your Samsung printer is still problematic as it dates back to 2005, I would strongly recommend to update it.

Multiple issues are being listed, the main being NTFS File system and once again a memory related problem.
Start by removing any Asus software like Asus Update, PC Probe or any other Asus hardware monitoring/overlcoking software related. These may interfere with the proper functioning of your hardware.

Is anything overcloked (RAM, CPU, Graphics)?

djdrock · 26 Jul 2012

I looked at updating the Samsung printing software, and did. Unless there is a specific windows file related to the printer, nothing is updating. This system is not overclocked.

It is possible it is memory related, as I am still running a single DIMM that is not on the list of recommended memory by the manufacturer. I thought that I had it solved when I removed one of the 4gb DIMMS. I will order some memory that is on the approved vendor list and go from there.

Windows 7: BSOD's new computer build even when idle

BSOD's new computer build even when idle problems?