Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD every 24 hours or so

23 Nov 2013   #1
byterj

Windows 7 Ultimate x64
 
 
BSOD every 24 hours or so

This computer runs vmware workstation only. Tried to update Bios, drivers.

Ran memtest86 for 24 hours with no errors.


My System SpecsSystem Spec
.
24 Nov 2013   #2
byterj

Windows 7 Ultimate x64
 
 

anyone?
My System SpecsSystem Spec
24 Nov 2013   #3
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Uninstall LogMein mirror. The driver seems to be extremely old.
Code:
fffff880`04340000 fffff880`04347000   lmimirr    (deferred)             
    Image path: lmimirr.sys
    Image name: lmimirr.sys
    Timestamp:        Wed Apr 11 04:02:45 2007 (461C108D)
    CheckSum:         0000A04C
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
________________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880101a1d90, fffff880025f84a8, fffff880025f7d00}

Probably caused by : Unknown_Image ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880101a1d90, The address that the exception occurred at
Arg3: fffff880025f84a8, Exception Record Address
Arg4: fffff880025f7d00, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`101a1d90 8b4810          mov     ecx,dword ptr [rax+10h]

EXCEPTION_RECORD:  fffff880025f84a8 -- (.exr 0xfffff880025f84a8)
ExceptionAddress: fffff880101a1d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000020000000010
Attempt to read from address 0000020000000010

CONTEXT:  fffff880025f7d00 -- (.cxr 0xfffff880025f7d00)
rax=0000020000000000 rbx=fffff8a012822930 rcx=fffffa801ba29000
rdx=fffffa802bf5c890 rsi=fffffa801ba29000 rdi=fffffa801ba29000
rip=fffff880101a1d90 rsp=fffff880025f86e0 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=fffff8a0122f0000
r11=0000000000000007 r12=fffffa802bf5c890 r13=0000000000000001
r14=fffffa802bf5c800 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`101a1d90 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:00000200`00000010=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000020000000010

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc80e8
GetUlongFromAddress: unable to read from fffff80002cc8198
 0000020000000010 Nonpaged pool

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`101a1d90 8b4810          mov     ecx,dword ptr [rax+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880101a215e to fffff880101a1d90

STACK_TEXT:  
fffff880`025f86e0 fffff880`101a215e : fffff8a0`12822930 fffff8a0`122f02e8 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`025f8710 fffff880`1019f27c : 00000000`0000001f 00000000`00000000 00000000`00000001 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x42
fffff880`025f87d0 fffff880`101b965d : 00000000`00000000 fffff8a0`0c9d0530 fffffa80`00000000 fffffa80`2933f010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x7e8
fffff880`025f89a0 fffff880`101b9398 : fffff800`00b96080 fffff880`101b8d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`025f8b90 fffff880`101b8e96 : 00000000`00006750 fffffa80`33004980 00000000`00000080 fffffa80`1b988410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`025f8bc0 fffff800`02d34cce : 00000000`00f2b8a5 fffffa80`1b6aa8c0 fffffa80`18836040 fffffa80`1b6aa8c0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`025f8c00 fffff800`02a88fe6 : fffff800`02c09e80 fffffa80`1b6aa8c0 fffff800`02c17cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`025f8c40 00000000`00000000 : fffff880`025f9000 fffff880`025f3000 fffff880`025f8540 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880025f7d00 ; kb

BUCKET_ID:  INVALID_KERNEL_CONTEXT

MODULE_NAME: Unknown_Module

Followup: MachineOwner
---------
My System SpecsSystem Spec
.

24 Nov 2013   #4
byterj

Windows 7 Ultimate x64
 
 

Thanks for the response!

What i did so far: Fresh install of LogMeIn with no mirror driver (the program still works just fine), instructions in the end (if some1 else needs it someday) and run the Furmark for half hour, no issues.

Oh, i attached new SF log with the mirror driver removed and more more BSOD report (happened tonight, before i uninstalled the driver)



...


LogMeIn no mirror drivers instructions
1. Please download this file <
https://secure.logmein.com/logmein.zip
> .
2. Next, create a folder in the C:/ drive called lmi. Then open the LogMeIn.zip file and extract it to the lmi
folder.
3. Next, go to Start, then Run, and type cmd.
4. To find your system type, Right click on the My Computer icon, and choose properties:
o If the local operating system is 32-bit, then at the command prompt, type:
1. cd C:\lmi\x86 (hit enter)
2. logmein install -nomirrordrv (hit enter)
o If the local operating system is 64-bit, then at the command prompt, type:
1. cd C:\lmi\x64 (hit enter)
2. logmein install -nomirrordrv (hit enter)
5. You will then receive a message that install was successful. Close the command prompt window and click "Open
LogMeIn" on the message that appears, and follow the steps to assign the computer to your LogMeIn account.
My System SpecsSystem Spec
24 Nov 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Now this is a stop 0x124, which indicates to somehow hardware failure.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801904f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Let us know the wattage of the PSU, too.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
My System SpecsSystem Spec
24 Nov 2013   #6
byterj

Windows 7 Ultimate x64
 
 

No overclock, my PSU is a 430w Corsair (i have a mirror system with same compounds doing the same job and no problems)

http://speccy.piriform.com/results/S...v7Y0u3wFZoPsFA (almost full load, cpu temps looks fine)
Furmark for half hour, no error

The system have 32gb ram, i left memtest for 24 hours with no error (not sure how many passses)

If another BSOD happens i think i will exchange parts with the other computed i have (they are the same, except the other one is rock solid) to see whats faulty.

Do you think its hardware for sure?
My System SpecsSystem Spec
24 Nov 2013   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

What is the result of Prime95?

Your BIOS date is very latest .... is it a brand new motherboard, or you updated the BIOS?

If the motherboard is brand new, RMA it. Or if it is old, how old it is? Coz, you are saying that temps are looking fine, but the fact is temps are extreme.

Attachment 294830

If the motherboard/computer is old (and you cannot RMA it), dismantle the PC. Clean everything inside it, but very carefully. Clean all the air vents, and fan grills so that it can blow the hot air out efficiently. While re-seating, apply new thermal paste to the CPU.



Also, 430 watts of a power supply cannot be enough to run your system. Either downgrade the system or upgrade the PSU, to at least 650 watts.

And, we need to know the result of Prime95 test, too.

Let us know when all are done.

EDIT: What is the capacity of your cooler and heat-sink fan?
My System SpecsSystem Spec
24 Nov 2013   #8
byterj

Windows 7 Ultimate x64
 
 

Didn't ran prime95 yet because im using the PC for doing a urgent task, will do when possible!

The motherboard is new, and i updated the bios trying to solve the BSODs

I have a mirror system using same compounds (bought all in same place) except SSD.

Mirror snapshot here http://speccy.piriform.com/results/B...ImKA6h5av8wzB2

About temps, my guess is that motherboard temperature is not reported correctly.
Oh, CPU usage is 80~100% for all time (vmware workstation).
About CPU temperature i think is OK also (OK, not very good, but shoudnt cause a BSOD), a quote from another hardware forum "Yeah, these chips run hot. I see spikes all the time past 80C with an h80i. My tuniq tower 120 extreme was a little better, but I still saw 79C under full load." and im using intel stock cooler.

What im planning to do in next BSOD is a windows fresh install and wait to see if its gonna BSOD again. If yes, i will try to replace VGA and after that memories just to make sure. Gonna check to see if the other PC will BSOD when i swap parts. Finally Swap PSU and if its not solved pretty sure its the motherboard.

But guess what, didnt BSOD since we removed that driver, so i hope it remains running

Thankssss
My System SpecsSystem Spec
24 Nov 2013   #9
byterj

Windows 7 Ultimate x64
 
 

look what i found:

System that crashes:

Graphics
Standard Monitor (1024x768@60Hz)
2047MB NVIDIA GeForce GT 640 (ZOTAC International):
56 C

The good one:

Graphics
Standard Monitor (1920x1080@60Hz)
2048MB NVIDIA GeForce GT 640 (ZOTAC International):
57 C

Any clue why the bad system report VGA with 1 less MB? The VGAs are same model!
My System SpecsSystem Spec
27 Nov 2013   #10
byterj

Windows 7 Ultimate x64
 
 

So far so good, 48 hours without BSODs!

Solution in post #4

Thanks Arc!
My System SpecsSystem Spec
Reply

 BSOD every 24 hours or so




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD after 3-4 hours
Getting the BSOD after running pc for about 4-5 hours, when try to restart black screen. If i let it sit over night starts right up then after 4-5 hrs. get BSOD again. Was told by computer repair that my bios was going bad. Any thoughts?
BSOD Help and Support
BSOD after 7-9 Hours
I am consistently getting a BSOD after about 7-9 hours from startup on my Windows 7 Home Premium, 64 bit, ZT brand PC with 16GB memory and 2TB HD. When I reboot it runs fine without problems or symptoms for another 7-9 hours and then I get the BSOD again. EDIT: I am getting this info on my...
BSOD Help and Support
BSOD Every 1-2 Hours
I seem to be getting blue screens of death every 1 to 2 hours. I thought it might have been because my old HDD was dying, but having just replaced it and the BSOD continue to happen. I've attached my .dmp file.
BSOD Help and Support
BSOD every few hours
Hello, Every few hours I'm running into an error and I can't seem to figure out where its stemming from. Any help would be GREATLY appreciated! :) Thanks, Worthy
BSOD Help and Support
BSOD when computer is idle. No BSOD when playing games for hours.
Hi guys! I badly need your help. I started getting BSOD two weeks ago. As far as I can remember the first time I had a BSOD was on the day I installed Max Payne 3 (I read somewhere that the some guy had also this problem when he installed max payne). There were two occasions that I got a BSOD upon...
BSOD Help and Support
6 hours of Prime95 and 2.5 hours of OCCT.
Is this enough to say my processor is stable? Temperatures stopped increasing loooooooooooong ago. I accidentally messed up the Prime95 test - I was going to run it for a day, but needed access to my computer. Using my computer forced two of the workers to stop due to insufficient swap space/RAM. ...
PC Custom Builds and Overclocking


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App