Random BSOD

[justin91]

Hello,

I'm having random Blue screens when I play games, it usually happends when I play GTA 4. It also happends when I leave the computer on for downloading at night.

I have absolutely no idea how to fix this. The error codes are random; in the most cases it's IRQL_NOT_LESS_OR_EQUAL, sometimes it's SYSTEM_SERVICE_EXCEPTION. I'm using Windows 7 64 bit right now but it happened with XP as well.

All drivers are up to date.

I put my videocard in another computer to see if it was a videocard problem, but that PC was fine. I have also bought another processor but the problem is still there. (Bought it for more speed)

PC temperatures are ok, processor never gets higher than 60 C and the videocard only gets to 70-80. (When playing a game).

By the way, sometimes the blue screens points out to "dxgmms1.sys" or something. But this does not always happen. Any thoughts on that file?

Any suggestions or help is greatly appreciated.

Thanks in advance,

Justin.

PSU: 500 watt
Motherboard: Asus M3N-HD HDMI
Processor: AMD Phenom II X4 940
Videocard: ASUS EN9800 GT
Soundcard: USB speakers
Memory: Kingston 4x1 gig DDR2 800
HDD: Samsung 1x320 GB (SATA)

 

[Capt.Jack Sparrow]

Hello !! Welcome to SF !!

Please post us the Dump files to analysis http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

- Captain

 

[justin91]

Hello and thanks for the welcome and the fast reply.

Here is the crashdump. I only have one, I think this one happened 2 days ago. Other ones are probably deleted by cleanup program.

-Justin

 

[Capt.Jack Sparrow]

Hello and thanks for the welcome and the fast reply.

Here is the crashdump. I only have one, I think this one happened 2 days ago. Other ones are probably deleted by cleanup program.

-Justin

Hello Justin !!

The Dump is pointing to some Windows Core files but it didn't find the exact driver. so please follow these steps

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

ASACPI.sys driver is from Asus its a utility which is well known problems. I'm attaching the file so download it and update it

MB_WIN7_ATK.ZIP

Uninstall all the Asus Utilities Like PC Probe etc. then see whether it makes any diference

After doing so if it didn't resolved the we need to run the Driver Verifier !! http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html but please follow the other steps before you do so.

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.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80806aff8f8, memory referenced
Arg2: 000000000000000c, 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: fffff800068d7115, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80006aff0e0
 fffff80806aff8f8 
CURRENT_IRQL:  c
FAULTING_IP: 
nt!KiIpiSendRequest+1d5
fffff800`068d7115 4d8b9cf600892a00 mov     r11,qword ptr [r14+rsi*8+2A8900h]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
TRAP_FRAME:  fffff88003516610 -- (.trap 0xfffff88003516610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000019
rdx=f80006a3dc180c05 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800068d7115 rsp=fffff880035167a0 rbp=0000000000000000
 r8=0000000000000019  r9=0000000000000000 r10=0000000004000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiIpiSendRequest+0x1d5:
fffff800`068d7115 4d8b9cf600892a00 mov     r11,qword ptr [r14+rsi*8+2A8900h] ds:00000000`002a8900=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800068c8469 to fffff800068c8f00
STACK_TEXT:  
fffff880`035164c8 fffff800`068c8469 : 00000000`0000000a fffff808`06aff8f8 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffff880`035164d0 fffff800`068c70e0 : 00000000`00000007 fffff880`009e5180 00000000`00000000 fffffa80`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03516610 fffff800`068d7115 : 00000000`00000000 00000000`00001000 00000000`00040001 00000000`0000000d : nt!KiPageFault+0x260
fffff880`035167a0 fffff800`068d6dca : 00000000`00000000 00000000`00000000 00000000`00000000 fffff781`c0000488 : nt!KiIpiSendRequest+0x1d5
fffff880`03516860 fffff800`068dcc8b : 00000000`00005409 00000000`00000001 00000000`00000002 00000000`00005404 : nt!KeFlushMultipleRangeTb+0x22a
fffff880`03516930 fffff800`06949a0e : fffffa80`0566c3f8 fffff880`00000001 00000000`00000001 fffff880`03516bb0 : nt!MiAgeWorkingSet+0x36b
fffff880`03516ae0 fffff800`068dd6e2 : 00000000`000011fa 00000000`00000000 fffffa80`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03516b80 fffff800`068dd96f : 00000000`00000008 fffff880`03516c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03516bd0 fffff800`06b6c166 : fffffa80`036f8040 00000000`00000080 fffffa80`036d39e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03516d40 fffff800`068a7486 : fffff880`03163180 fffffa80`036f8040 fffff880`0316dfc0 a5acc55a`5ae78535 : nt!PspSystemThreadStartup+0x5a
fffff880`03516d80 00000000`00000000 : fffff880`03517000 fffff880`03511000 fffff880`03516820 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiIpiSendRequest+1d5
fffff800`068d7115 4d8b9cf600892a00 mov     r11,qword ptr [r14+rsi*8+2A8900h]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!KiIpiSendRequest+1d5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0xA_nt!KiIpiSendRequest+1d5
BUCKET_ID:  X64_0xA_nt!KiIpiSendRequest+1d5

Hope this helps,
Captain

 

[justin91]

Hello again,

I ran the tests using diskettes. Both memory and HDD tests finished with 0 errors.
I've also installed the ASUS thing. I have no other ASUS software on my computer (asusprobe).
The CMD command returned with the message that everything is fine.

By the way, some while ago I used some driver checking utility built into Windows (not sure it's the same thing you posted) and it immediately threw a BSOD at me. I think it was my videocard driver. I tried the driver check on a different computer and again a BSOD while it has another videocard (both same drivers though).
The other PC had a 6800 I think and I have a 9800 GT.
This was with the Windows 7 RC (64 bit).

So, since the memory and HDD tests succeeded, should I proceed with the driver verifier?

 

[justin91]

Hi,

Played GTA 4 5 minutes ago and got another Blue Screen. This time without a error code (like IRQL_NOT_LESS_OR_EQUAL).

Maybe this recent dump has some other useful information? I don't know how old the other one was.

Thanks for the help,

Justin

 

[Capt.Jack Sparrow]

Hello Justin !!

Did you download the MemTest86+ and run upto 6 passes ?? Because the Mem Test in Windows is no longer recommended. Once you run the MemTest86+ and complete 6 passes without any errors then you can proced with Driver Verifier !!

 

[justin91]

Hi.

I used memtest86+ with my diskette drive. I only let it do 1 pass, but I'll do 6 the next time.

I'll turn memtest on again tonight when I go to bed and tell you the results tommorow.

Justin

 

[justin91]

Back again,

Tested the memory again, with all 4 sticks in it gave 14 errors in just 1 minute.

I took 2 out and the test ran fine for 14 passes with no errors.

Then I put the other 2 in and again no errors.

I only have errors when I have all 4 sticks in the computer.

Btw: 1 of the 4 sticks hasnt got chips on both sides. Just 1. Also, I can't use this stick to run the pc in Dual-Channel mode. Theyre all kingston ddr2 800 though. I think I'll replace the stick anyway to get Dual-Channel mode (for my pc its called ganged or unganged mode).

I think the memory sticks dont like the fourth one. I remember buying it but I asked for exactly the same memory as I bought before. Maybe Kingston makes it differently now?

Looking forward to your reply,

Justin

 

[DocBrown]

Are you doing any overclocking of CPU or memory ? Yes it sounds like 1 memory stick is mis-matched !

 

[YakSipper]

As a hunch, I'd completely uninstall Comodo and any antivirus on the machine and see how it goes from there.

 

[justin91]

Hey,

No, I don't overclock anything.

I went to the computer store today and asked for another 1 gig memory module with chips on BOTH sides. He didn't have them anymore and told me it was an old model. So I bought the 1 side chips one.

Have the pc running in Dual-Channel now and just played some GTA4 for 45 minutes and no crash!

I'll do a memtest tonight just to be sure and post an update here.

Still, if the problem is fixed now, isn't it strange the Blue screen referred to drivers?

Cheers,

Justin

 

[YakSipper]

Good call on that Doc. + rep

No, it's not strange. Drivers can get corrupted in memory for many reasons besides a bad driver itself.

 

[Dave76]

Another good call Doc,

 

[smarteyeball]

Still, if the problem is fixed now, isn't it strange the Blue screen referred to drivers?

If the timings of the new module are mismatched (what Doc pointed out) then it's very common for memory related crashes to point to many different drivers.

Basically, when a driver is calling on the address range/s that are at fault , then any driver can get tripped up and cause a BSOD.

It's like a pot hole in the road.

Many cars can travel over that particular stretch of road for a period of time without hitting it, but every now and then an unlucky car will hit the pothole.

 

[justin91]

Hi,

I think the problem is fixed, memtest ran for 7 passes with 0 errors. I think it's safe to say the RAM is fixed now, no?

Many thanks for the help guys!

Justin