Windows 7 BSOD- Memory.dmp (Driver Conflicts?) Mini-Dump

D

Dynamics

New Member
Joined
Sep 10, 2011
Hi guys. i have a brandon new computer Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz Memory (RAM) 4g ATI Radeon HD 4550 , Crashes Will ALOT of blue screens mainly when playing games.. but i've just recently got a couple of blue screens staying idle ... almost all of them pop up saying memory.dmp . i get blue screens saying stuff like this , system_Expection and SPECIAL_POOL_DUMP , other ones.. it says alot of the time display driver has stop responding.. so im thinking its a driver.. i know it cant be the computer its brand new.. heres some of the minidump files 091011-14578-01.dmp , 090911-19625-01.dmp , 090911-14796-01.dmp , 090911-13609-01.dmp , 090911-13453-01.dmp , 090811-23359-01.dmp , 090811-20718-01.dmp , 090811-19406-01.dmp And ALOT more just dont feel like naming them all but will post more if needed to fix my problem... please help me guys. Thanks!
 
Your dump files are a bit all over the place, however several suggest an issue with memory, which could lead us somewhere. You should probably first take care of these two drivers
IesDrv.sys 1/8/2009 ASRock IES Utility
and
Rt64win7.sys 2/26/2009 Realtek network card driver
Then go here http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html#post140678
follow the instructions, collect the data, put it into a new desktop folder, zip it up and attach it.
DUMP:
Code: 
Unable to load image \??\C:\Windows\SysWOW64\Drivers\IesDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IesDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for IesDrv.sys
Probably caused by : IesDrv.sys ( IesDrv+54ef )

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: fffff880063c04ef, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880063c04ef, address which referenced memory

Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
 fffff880063c04ef 

CURRENT_IRQL:  2

FAULTING_IP: 
IesDrv+54ef
fffff880`063c04ef 440f22c1        mov     cr8,rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  AsrIes.exe

TRAP_FRAME:  fffff8800681f7e0 -- (.trap 0xfffff8800681f7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000eba9c rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880063c04ef rsp=fffff8800681f970 rbp=fffff9800f696ee0
 r8=0000000000000b34  r9=0000000000000000 r10=fffff9800f696ee0
r11=0000020b9abd6800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
IesDrv+0x54ef:
fffff880`063c04ef 440f22c1        mov     cr8,rcx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cccb29 to fffff80002ccd5c0

FAILED_INSTRUCTION_ADDRESS: 
IesDrv+54ef
fffff880`063c04ef 440f22c1        mov     cr8,rcx

STACK_TEXT:  
fffff880`0681f698 fffff800`02cccb29 : 00000000`0000000a fffff880`063c04ef 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0681f6a0 fffff800`02ccb7a0 : 00000000`0015bada 00000000`0015bada 00000000`00000001 00000000`00d10461 : nt!KiBugCheckDispatch+0x69
fffff880`0681f7e0 fffff880`063c04ef : 00000000`0015bada fffff800`031602a7 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0681f970 00000000`0015bada : fffff800`031602a7 00000000`00000001 00000000`00000001 00000000`00000001 : IesDrv+0x54ef
fffff880`0681f978 fffff800`031602a7 : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00000000 : 0x15bada
fffff880`0681f980 fffff800`03173c16 : fffff980`0f696ee0 00000000`00000002 fffffa80`07bb07b0 fffffa80`03ceb418 : nt!VfIrpAllocateCallDriverData+0x47
fffff880`0681f9b0 fffff800`02fe5597 : fffffa80`07b30090 fffff880`0681fca0 fffffa80`07b30090 fffffa80`07b68f40 : nt!IovCallDriver+0x566
fffff880`0681fa10 fffff800`02fe5df6 : fffff800`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0681fb40 fffff800`02ccc813 : fffff8a0`0abd0000 fffff8a0`0bc6f000 fffff8a0`0704e000 fffff8a0`0704d000 : nt!NtDeviceIoControlFile+0x56
fffff880`0681fbb0 00000000`75152dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75152dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
IesDrv+54ef
fffff880`063c04ef 440f22c1        mov     cr8,rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  IesDrv+54ef

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IesDrv

IMAGE_NAME:  IesDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4965bc6c

FAILURE_BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_IesDrv+54ef

BUCKET_ID:  X64_0xD1_VRF_CODE_AV_BAD_IP_IesDrv+54ef
DRIVERS:
Code: 
TSDDD.dll    
secdrv.SYS    9/13/2006 8:18
IesDrv.sys        1/8/2009 3:42
Rt64win7.sys    2/26/2009 4:04
spldr.sys        5/11/2009 11:56
spsys.sys        5/11/2009 12:20
dump_iaStor.sys    6/4/2009 20:53
iaStor.sys        6/4/2009 20:53
hwpolicy.sys    7/13/2009 18:19
intelppm.sys    7/13/2009 18:19
msisadrv.sys    7/13/2009 18:19
pcw.sys        7/13/2009 18:19
ACPI.sys        7/13/2009 18:19
Null.SYS        7/13/2009 18:19
Fs_Rec.sys    7/13/2009 18:19
atapi.sys        7/13/2009 18:19
Msfs.SYS        7/13/2009 18:19
Npfs.SYS        7/13/2009 18:19
PCIIDEX.SYS    7/13/2009 18:19
kbdclass.sys    7/13/2009 18:19
mouclass.sys    7/13/2009 18:19
pci.sys        7/13/2009 18:19
WMILIB.SYS    7/13/2009 18:19
ataport.SYS    7/13/2009 18:19
cdrom.sys        7/13/2009 18:19
mountmgr.sys    7/13/2009 18:19
WDFLDR.SYS    7/13/2009 18:19
CLFS.SYS    7/13/2009 18:19
disk.sys        7/13/2009 18:19
volmgr.sys    7/13/2009 18:19
CLASSPNP.SYS    7/13/2009 18:19
partmgr.sys    7/13/2009 18:19
fltmgr.sys        7/13/2009 18:19
volsnap.sys    7/13/2009 18:20
volmgrx.sys    7/13/2009 18:20
ksecdd.sys    7/13/2009 18:20
nsiproxy.sys    7/13/2009 18:21
fwpkclnt.sys    7/13/2009 18:21
tdx.sys        7/13/2009 18:21
TDI.SYS        7/13/2009 18:21
netbt.sys        7/13/2009 18:21
msrpc.sys        7/13/2009 18:21
ndis.sys        7/13/2009 18:21
NETIO.SYS    7/13/2009 18:21
dump_dumpfve.sys    7/13/2009 18:21
Wdf01000.sys    7/13/2009 18:22
HTTP.sys        7/13/2009 18:22
mup.sys        7/13/2009 18:23
rdbss.sys        7/13/2009 18:24
csc.sys        7/13/2009 18:24
luafv.sys        7/13/2009 18:26
mssmbios.sys    7/13/2009 18:31
fileinfo.sys    7/13/2009 18:34
rdyboost.sys    7/13/2009 18:34
blbdrive.sys    7/13/2009 18:35
discache.sys    7/13/2009 18:37
watchdog.sys    7/13/2009 18:37
Dxapi.sys        7/13/2009 18:38
vga.sys        7/13/2009 18:38
VIDEOPRT.SYS    7/13/2009 18:38
monitor.sys    7/13/2009 18:38
vmstorfl.sys    7/13/2009 18:42
cng.sys        7/13/2009 18:49
Beep.SYS    7/13/2009 19:00
swenum.sys    7/13/2009 19:00
ksthunk.sys    7/13/2009 19:00
kbdhid.sys    7/13/2009 19:00
mouhid.sys    7/13/2009 19:00
CompositeBus.sys    7/13/2009 19:00
serenum.sys    7/13/2009 19:00
parport.sys    7/13/2009 19:00
serial.sys        7/13/2009 19:00
crashdmp.sys    7/13/2009 19:01
msahci.sys    7/13/2009 19:01
vdrvroot.sys    7/13/2009 19:01
WudfPf.sys    7/13/2009 19:05
HDAudBus.sys    7/13/2009 19:06
HIDPARSE.SYS    7/13/2009 19:06
HIDCLASS.SYS    7/13/2009 19:06
hidusb.sys    7/13/2009 19:06
USBD.SYS    7/13/2009 19:06
portcls.sys    7/13/2009 19:06
usbehci.sys    7/13/2009 19:06
USBPORT.SYS    7/13/2009 19:06
umbus.sys    7/13/2009 19:06
usbhub.sys    7/13/2009 19:07
mpsdrv.sys    7/13/2009 19:08
lltdio.sys        7/13/2009 19:08
rspndr.sys        7/13/2009 19:08
netbios.sys    7/13/2009 19:09
wfplwf.sys        7/13/2009 19:09
tunnel.sys        7/13/2009 19:09
pacer.sys        7/13/2009 19:09
tcpipreg.sys    7/13/2009 19:09
ndistapi.sys    7/13/2009 19:10
NDProxy.SYS    7/13/2009 19:10
ndiswan.sys    7/13/2009 19:10
rasl2tp.sys    7/13/2009 19:10
raspppoe.sys    7/13/2009 19:10
raspptp.sys    7/13/2009 19:10
wanarp.sys    7/13/2009 19:10
AgileVpn.sys    7/13/2009 19:10
rassstp.sys    7/13/2009 19:10
RDPCDD.sys    7/13/2009 19:16
rdpencdd.sys    7/13/2009 19:16
rdprefmp.sys    7/13/2009 19:16
termdd.sys    7/13/2009 19:16
rdpbus.sys    7/13/2009 19:17
peauth.sys    7/13/2009 20:01
drmk.sys        /13/2009 20:01
hal.dll        7/13/2009 20:27
CI.dll        7/13/2009 20:32
PSHED.dll    7/13/2009 20:32
fvevol.sys        9/25/2009 21:34
ksecpkg.sys    12/11/2009 1:03
ks.sys        3/3/2010 23:32
amdxata.sys    3/19/2010 11:18
viahduaa.sys    10/21/2010 3:05
cpuz135_x64.sys    11/9/2010 8:33
dxgmms1.sys    1/25/2011 23:22
dxgkrnl.sys    1/25/2011 23:22
cdd.dll        1/26/2011 1:31
kdcom.dll        2/5/2011 7:21
bowser.sys    2/23/2011 0:15
Ntfs.sys        3/10/2011 22:39
afd.sys        4/24/2011 21:43
dfsc.sys        4/26/2011 21:57
srvnet.sys        4/28/2011 22:12
srv2.sys        4/28/2011 22:12
srv.sys        4/28/2011 22:13
mrxsmb20.sys    5/3/2011 21:51
mrxsmb.sys    5/3/2011 21:51
AtihdW76.sys    6/7/2011 5:34
win32k.sys    6/10/2011 21:56
tcpip.sys        6/20/2011 22:44
ntoskrnl.exe    6/22/2011 21:51
mrxsmb10.sys    7/8/2011 21:44
atikmpag.sys    7/28/2011 15:54
atikmdag.sys    7/28/2011 16:29
 
Iesdrv.sys is not needed i clicked asrock ise to see what it was and it crashed , all it is an energy saver... im thinking its something to do with my memory or/and graphics card because when i play games sometimes ill get a Signal over range.. or mabey the power supply i have huge blue neon fan on my computer case.. and 2 other small fans.. and i bought cheapest power supplu which is 480 watts which i dont think is helping it.. but i get memory dump BSOD usually when i play games.. (i bought this pc for gaming ) or sometimes ill click the slightest think like earlier it was clicked google chrome BSOD.. so its usually a click that does it but thats the rarely blue sceens... im not to depth into computer stuffs so is there anything else you can tell me??
 
I would be happy to help further if you will first help me, by addressing the two driver issues that I noted above and then by following the link that I also posted above and providing the information laid out in that link (first post only). Then attach any new blue screen .dmp files that reflect that you have either updated the two drivers to post Win7 RTM dates or have otherwise removed them by uninstalling the associated software or hardware device. Then we can move forward.
Thank You
Randy
 
Will Do , I Downloaded Realtek One Last Night.. And Im Not Good At Downloading Drivers.. I Have A Program Called Drivermax that does it for me but it only downloads 2 a day unless you pay... and it scanned them and it also said these are some out-dated-drivers tell me if these would have an affect on my blue screen of death : HID-compliant mouse : Intel(R) 5 Series/3400 Series Chipset Family SMBus Controller : Intel(R) 82801 PCI Bridge - 244E : Intel (R) processor DMI - D131 : Intel(R) processor Miscellaneous Registers - D158 : Intel(R) processor PCI Express Root Port 1 - D138 : Intel(R) processor Semaphore and Scratchpad Registers - D156 : Intel(R) processor System Management Registers - D155 : Intel(R) processor System Control and Status Registers - D157 : Intel(R) QuickPath Interconnect - D150 : Intel(R) QuickPath Interconnect - D151 : Realtek PCIe GBE Family Controller : USB Input Device. Those are all of them.. im going to do try and do that thing you told me to do but it sounds really complicated and im only 16
 
Also Sir Can You Explain How I Can Find And Download Those Driver I Look Them Up But Like... Its Complicated I Think Im Going To End Up Installing A Different Driver And Making Matters Worse.
 
For driver software to support you hardware devices, it is always considered a best practice to use the individual manufacture's website to obtain the latest drivers for their products.
You need to know some specific information to begin with to avail yourself of that information, generally speaking the Manufacturer Name, Model Name, Model Number and Revision Numbers as they apply.
So for the ASRock issue you should start here Z68 Motherboard Series - Download Files form ASRock Inc. and use the interface to pick your particular product
and for the Realtek device you can start here Realtek see of your particular card is listed and if not use the links on the left to navigate the site to find your card.
It isn't exactly rocket science and is not generally difficult. Take your time, be patient and you'll find them. Use google sometimes it helps. And as a general rule always seeks out the hardware vendor's driver first, before resorting to any third party software product to find drivers for you. And in the case of motherboards start with the chipset driver followed by any updates for embedded hardware Audio, LAN, Video, etc., And often times a BIOS update can also help, although not for the faint of heart or inexperienced (but we all have to start somewhere, sometime).
 
Thanks Randy And Elmer I downloaded both.. I Haven't Got Blue Screen Yet.. But I Know It Will Come Soon... Happens Randomly Latest One I Had Was dxgmms1.sys earlier when I was playing a game called APB-Reloaded Happen When I Exited Out The Game... This Could Be Due To That This Game Requires phyX which is only for nvidia and I'm using a ati card , but it also does it on world of warcraft ocasionally... but a problem that is occuring a lot not to much but I get a black screen like it says RMB signal out is out of range.. I thought it might be the monitor but its not I hooked it up to my other computer and when it would do it that one would say Not Supported.. But The Thing Is I Would Have Skype And My Game Still Running And I Could Basicly Play My Game And Still Talk To My Friends Just Not Having Anything On Screen To Display.. That Cause I Was Thinking It Wasn't Getting Enough Power... I have 480 power supply. And Ideas guys or should I just wait for a blue screen.. also I was playing APB game froze coudn't alt+crl+delete Forced to hit restart button but like I said that game might not be compatiable with my graphics card.. I need your guys opinons and thoughts. Thanks!
 
ok guys when i click start menu hit restart i get a blue screen saying dxgkrnl.sys, this will loop if i try to restart from start menu...
 
Just a thought but 19 of 46 crashes relate directly (or indirectly) to memory management

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.


2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Click to expand...
 
Thanks For The Usb Kaos And ZigZag I Came Back Clean 7 Passes But Know I Think I Might Fixxed That Problem... ( Mabey ) im getting blue screens of death know that say dxgkrnl.sys and dxgmms1.sys - my dad told me he thinks it has something to do with direct x but im not sure...
 
your welcome

memtest should take longer than that?

how many sticks do you have?
how many slots are used when ALL the ram is in?

dxgmms1.sys is related to Direct X as a either conflict etc... You can update Direct X , update BIOS too if there is one along with Graphics drivers
 
only 1 4g ram stick and i have asrock flash utility update thingy in the bios should i do that and all of the ati graphics drivers are up to date im getting blue screen with STOP: 0x000000b1 or stuff similar to that... i can barely play a game without getting blue screen within 2-5 mints
 
Attach new .dmp files along with the information I asked for earlier regarding CPUz and RAMMon and we'll take a look. Also you should probably run the SF Diagnostic tool also referenced in the link I posted earlier.
Regards
Randy
 
You must log in or register to reply here.

Similar threads

Z
BSOD 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys
Replies
3
Views
2K
dianawolws
dianawolws
News
Available today: The Windows 11 2022 Update
Replies
0
Views
1K
News
News
News
Announcing Windows 11 Insider Preview Build 22557
Replies
0
Views
1K
News
News
M
Windows 10 Frequent BSOD for over 1.5 years have recently replaced my RAM, PSU and Motherboard to no avail. Looking for help/advice.
Replies
3
Views
2K
kemical
kemical
News
Announcing Windows 10 Insider Preview Build 16257 for PC & Build 15237 for Mobile
Replies
0
Views
915
News
News
Back
Top Bottom