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: Numerous BSOD playing games, recently error 0xd1

22 Jun 2012   #11

MS Windows 7 Ultimate SP1 64-bit
 
 

lian,
did you let Wdindows Defender Offline run a COMPLETE scan of all of your drives? Yes/No.

WIN | type MSCONFIG | ENTER | STARTUP tab
uncheck ALL except for:
Quote:
MSC "C:\Program Files\Microsoft Security Client\msseces.exe" -hide -runkey
REBOOT!

Don't worry! You have not deleted anything. You have simply told WIN 7 to not run all of those programd at startup time. They will still be run, if and when needed.

Ian, please, fill out your system specs fully and completely. Here is how:
Update your SevenForums System Specs
User CP (located on the top menu bar) |
Your Profile | Edit System Spec
(left-hand column)

To gather info, use Speccy (my favorite) or SIW or System Info

ADD the word laptop or desktop or netbook to the
“system manufacturer” block, for example,
Toshiba Satellite L305D notebook.

Provide full windows version info, for example:
MS Windows 7 Ultimate SP1 64-bit

Use the “Other Info” block for Optical Reader,
Mouse, touchpad, wifi adapter, speakers, monitor, etc

Scroll down and click on SAVE CHANGES.
======================================================

I'll be looking for the updated specs in your next post.





My System SpecsSystem Spec
.

22 Jun 2012   #12

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Yes, after the quick scan I did the total scan. I did the msconfig instructions and updated the system specs.
My System SpecsSystem Spec
22 Jun 2012   #13

MS Windows 7 Ultimate SP1 64-bit
 
 

Excellent.

Don't enjoy continually asking for more, but...
Would you please carry out the following procedure, paying close attention to maximizing the display and the fields.

HOW TO POST A SNAPSHOT OF DISK MANAGEMENT DISPLAY
Run disk management:
WIN |
type DISKMGMT.MSC | ENTER
This method gives you a display without the unneeded navigation pane.
WIN=key with Microsoft logo on top.



Maximize the output of Disk Management:
ALT-Spacebar
key combo | X key (selects Maximize) |
Drag the field separators (such as between Status and Capacity) to show entire field.


Make a snapshot:
WIN |
type SNIPPING | ENTER | New
Drag the cursor around the area you want to snip.
File | Save as | select save location and name | Save


Post the snapshot:
Post a File or Screenshot in Seven Forums

==============================================
thanks,
karl
My System SpecsSystem Spec
.


22 Jun 2012   #14

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Here you go.
Attachment 217653
My System SpecsSystem Spec
22 Jun 2012   #15

MS Windows 7 Ultimate SP1 64-bit
 
 

lian, That looks good. Are you still encountering BSODs? If yes, then would you post a fresh jcgriff...?
My System SpecsSystem Spec
22 Jun 2012   #16

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Ok this is weird. I thought it was odd that SpotGrit.exe was the problem since I couldn't find it anywhere on my computer. I looked through the zip file I uploaded in my first post and checked some of the files and in the system info, it shows system specs that do not match mine. For example, I have an i5 3570k and the zip shows it as a core 2 duo, my graphics card is hd 7580 and it shows it as hd 4770 etc it looks like this is a computer of some guy living in the Netherlands lol.

The new zip file I made should not have this problem, as I checked the files and they appear to match my specs. Strange how that happened.

Should I make a new thread in light of this with the proper jgraff zip as the first post or just let it go and continue with this one?
My System SpecsSystem Spec
22 Jun 2012   #17

MS Windows 7 Ultimate SP1 64-bit
 
 

lian, I do not understand either, but I'm glad you caught the anomaly as so much just wasn't matching. No need to start over. I'll alert the gurus that you have a fresh file which needs to be examined. thanks, karl
My System SpecsSystem Spec
22 Jun 2012   #18

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Have you install all the motherboard drivers from the AsRock site?
Install the updated Intel RST driver if you don't already have it: Intel Rapid Storage Technology driver ver:11.1.0.1006

This is your first crash on 2 June'12:
This is a fairly generic crash, first check the driver implicated.
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Code:
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: ffffffffffffffff, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffffffffffffff, If non-zero, the instruction address which referenced the bad memory address.
Arg4: 0000000000000000, (reserved)
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c40e0
GetUlongFromAddress: unable to read from fffff800030c4198ffffffffffffffff
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  cfosspeed6.sys
FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_cfosspeed6+9105

These drivers are of interest as they have been affected and closed, they might be the cause or the result of the crash.
Unloaded modules:
fffff880`08b65000 fffff880`08b72000   vwifibus.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`07c15000 fffff880`07ddd000   athurx.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  001C8000
fffff880`07de4000 fffff880`07df1000   vwifibus.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`07c1c000 fffff880`07de4000   athurx.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  001C8000
fffff880`08ae9000 fffff880`08b5a000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`01d46000 fffff880`01d54000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`04227000 fffff880`045cb000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  003A4000
fffff880`045cb000 fffff880`045de000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
Did you install this program or was it included with another utility/program?
Un-install for testing purposes.

This is your last crash>
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
This bug check is usually caused by drivers that have used improper addresses.
Do you have any USB connected devices?
Code:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffba800b291010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880054b7652, address which referenced memory
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003107100
GetUlongFromAddress: unable to read from fffff800031071c0
 ffffba800b291010 Nonpaged pool
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  athurx.sys
FAILURE_BUCKET_ID:  X64_0xD1_athurx+b1652
Update your wireless driver from the AsRock site or the one listed below.
Quote:
athurx.sys Atheros AR9271 Wireless Network Adapter http://www.atheros.cz/
Both of the above crashes are similar, let's start with updating drivers and un-installing the AsRock utilities.

Driver issues or out of date.
FNETURPX.SYS Sat Oct 04 10:27:02 2008 - FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
Motherboard utilities are known to cause crashes, un-install all AsRock utilities for testing purposes. You may be able to re-install after the cause of the crash is identified but it is not recommended.

We need some more general information.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Other crashes:
Code:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  athurx.sys
--------------------------------------------------------------------------------------------------------------------------------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88006c1782e, Address of the instruction which caused the bugcheck
Arg3: fffff8800b589700, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  RTKVHD64.sys - Realtek High Definition Audio Function Driver
--------------------------------------------------------------------------------------------------------------------------------
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.
Arguments:
Arg1: fffff88003561186, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002e89977, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xA_nt!KiRetireDpcList+237
--------------------------------------------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000001d00e8a1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88010550e58, address which referenced memory
FAULTING_IP: 
USBPORT!USBPORT_Xdpc_Worker+a8
fffff880`10550e58 c70278647732    mov     dword ptr [rdx],32776478h
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  USBPORT.SYS
--------------------------------------------------------------------------------------------------------------------------------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: fffff88004fd5cf7, The address that the exception occurred at
Arg3: fffff880040aa568, Exception Record Address
Arg4: fffff880040a9dc0, Context Record Address
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+2b
fffff880`04fd5cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
IMAGE_NAME:  dxgmms1.sys - DirectX Graphics MMS
--------------------------------------------------------------------------------------------------------------------------------
Next one is Same as above
--------------------------------------------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
IMAGE_NAME:  cfosspeed6.sys
Same as before
--------------------------------------------------------------------------------------------------------------------------------
TIMER_OR_DPC_INVALID (c7)
Kernel timer or DPC used incorrectly.
Arguments:
Arg1: 0000000000000004, Thread APC disable count was changed during DPC routine execution.
Arg2: fffff80002f4bae0, Address of the DPC routine.
Arg3: 0000000000004000, Thread APC disable count before calling DPC routine.
Arg4: 0000000000000000, Thread APC disable count after calling DPC routine.
	The APC disable count is decremented each time a driver calls
	KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex. The APC
	disable count is incremented each time a driver calls KeLeaveCriticalRegion,
	FsRtlExitFileSystem, or KeReleaseMutex.
INVALID_DPC_FOUND: fffff80002f4bae0
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FOLLOWUP_IP: 
nt!PpmCheckRun+0
fffff800`02f4bae0 4883ec28        sub     rsp,28h
--------------------------------------------------------------------------------------------------------------------------------
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800118a18e, Address of the instruction which caused the bugcheck
Arg3: fffff8800880cdf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Diablo III.exe
IMAGE_NAME:  fltmgr.sys
--------------------------------------------------------------------------------------------------------------------------------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
IMAGE_NAME:  athurx.sys
Same as previous
--------------------------------------------------------------------------------------------------------------------------------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  dxgmms1.sys
--------------------------------------------------------------------------------------------------------------------------------
Same as above
--------------------------------------------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c8100
GetUlongFromAddress: unable to read from fffff800030c81c0
 0000000000004008 Nonpaged pool
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  rspndr.sys - Link-Layer Topology Responder Driver for NDIS 6 - Windows driver, likely the result of the crash
--------------------------------------------------------------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000004120, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880018ed3a0, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
IMAGE_NAME:  vwififlt.sys - Virtual WiFi Filter Driver - Windows driver, not the cause
--------------------------------------------------------------------------------------------------------------------------------
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800030026fb, address which referenced memory
FAULTING_IP: 
nt!ExDeferredFreePool+ca7
fffff800`030026fb 488b00          mov     rax,qword ptr [rax]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Diablo III.exe
IMAGE_NAME:  Pool_Corruption
There is a definite pattern with all the crashes, update drivers and un-install the programs listed above.

If the crashes continue we will test the RAM and possibly run Driver Verifier, let's get the results from the drivers updates and AsRock utilities un-install first.
My System SpecsSystem Spec
22 Jun 2012   #19

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

I never installed cfosspeed6 directly, but it sounds like something that would have been included with my motherboard. It seems it is used as part of the asrock XFast Lan utility.

When I installed the motherboard, I only used the CD and didn't download anything from that website. I noticed just now while uninstalling the xfast lan, xfast usb, and xfast ram, that some were outdated versions.

I will install the motherboard drivers from that site now. Should I download everything there I see?

Thanks very much for your help so far!
My System SpecsSystem Spec
22 Jun 2012   #20

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Please re-read my last post, I was adding information as I analyzed it.

Leave all the motherboard utilities un-installed until we find the cause of the crashes.

You can check the driver dates in Device Manager or just try to install them, if they are current they will tell you.
I would check the driver dates first.
Have a look at this tutorial: How to Roll Back a Device Driver in Device Manager
Stop at step #6 - there you can see the driver dates.
Install any drivers from the AsRock driver site that are newer.
No need to 'Roll Back' any drivers.
My System SpecsSystem Spec
Reply

 Numerous BSOD playing games, recently error 0xd1





Thread Tools



Similar help and support threads for2: Numerous BSOD playing games, recently error 0xd1
Thread Forum
BSOD playing game and surfing net, error 7f recently c4 BSOD Help and Support
BSOD playing games, 0x50, 0xA, 0xD1 BSOD Help and Support
BSOD 0x00000116 recently when playing games BSOD Help and Support
BSOD playing GTA IV Multiplayer, error 0xd1 0xe1. BSOD Help and Support
BSoD while playing numerous games, error 0x00000116 - Not constant BSOD Help and Support
Solved BSOD while playing games and viewing videos, stop 0xD1 BSOD Help and Support

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 03:13 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33