New
#11
good to hear ovai. Hopefully your BSOD days are over.
It was really perfect till now, as i just terminated GTA EFLC and went for shutdown i got IRQL_NOT_LESS_OR_EQUAL.
I have attached the minidump plz give me assistance on it. I also opened it on WinDbg, but no info i can get like Captian you gave in your reply.
Please help me out again guys.
WinDBG,
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffff00000000, 2, 1, fffff800030a3188}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+38 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffffff00000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800030a3188, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c40e0
ffffffff00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeReleaseSemaphore+38
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880080621b0 -- (.trap 0xfffff880080621b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffffff00000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a3188 rsp=fffff88008062340 rbp=fffffa80055f4b60
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeReleaseSemaphore+0x38:
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7 ds:ffffffff`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000308bb69 to fffff8000308c600
STACK_TEXT:
fffff880`08062068 fffff800`0308bb69 : 00000000`0000000a ffffffff`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08062070 fffff800`0308a7e0 : fffff980`19abbc00 ffffffff`00000000 fffffa80`04a05180 00000000`0191bfc9 : nt!KiBugCheckDispatch+0x69
fffff880`080621b0 fffff800`030a3188 : fffffa80`03d594a0 fffff800`030e9cbb 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`08062340 fffff800`030967b3 : fffffa80`03d594a0 fffffa80`00000000 fffff980`19abbdc0 fffff980`19abbc00 : nt!KeReleaseSemaphore+0x38
fffff880`080623c0 fffff880`0123342c : fffffa80`039f63a0 00000000`00000702 fffff8a0`09de44d0 00000000`00000000 : nt!ExpReleaseResourceForThreadLite+0x31e
fffff880`08062420 fffff880`01298bd6 : 00000000`00000000 00000000`00000001 fffffa80`039f63a0 fffffa80`039f63a0 : Ntfs!NtfsReleaseFcb+0x2c
fffff880`08062460 fffff880`012e9bbd : fffffa80`039f63a0 fffffa80`04a05180 00000000`00100001 00000000`00000000 : Ntfs!NtfsFlushVolume+0x4b6
fffff880`08062590 fffff880`012ea5f0 : fffffa80`039f63a0 fffffa80`062a4c10 fffffa80`05dc6f20 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
fffff880`08062670 fffff880`0104a23f : fffffa80`062a4fb0 fffffa80`062a4c10 fffffa80`039f63a0 fffff880`08062698 : Ntfs!NtfsFsdFlushBuffers+0x104
fffff880`080626e0 fffff880`010486df : fffffa80`04a00830 00000000`00000000 fffffa80`04a00800 fffffa80`062a4c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08062770 fffff800`033a3c49 : 00000000`00000002 fffffa80`05dc6f20 00000000`00000000 fffffa80`062a4c10 : fltmgr!FltpDispatch+0xcf
fffff880`080627d0 fffff800`033301c1 : fffffa80`062a4c10 fffffa80`055f4b60 fffffa80`05dc6f20 fffff880`02fd3180 : nt!IopSynchronousServiceTail+0xf9
fffff880`08062840 fffff800`0308b853 : fffffa80`055f4b60 fffffa80`036ee890 fffffa80`04a00830 fffffa80`05dc6f20 : nt!NtFlushBuffersFile+0x171
fffff880`080628d0 fffff800`03087df0 : fffff800`032d281d 00000000`00000004 fffffa80`04669b90 fffffa80`060950f0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`08062a68 fffff800`032d281d : 00000000`00000004 fffffa80`04669b90 fffffa80`060950f0 fffffa80`0370e040 : nt!KiServiceLinkage
fffff880`08062a70 fffff800`03331a86 : 00000000`00000000 fffffa80`055f4b60 00000000`00000080 00000000`00000001 : nt!PopFlushVolumeWorker+0x1bd
fffff880`08062d40 fffff800`0306ab06 : fffff880`02fd3180 fffffa80`055f4b60 fffff880`02fddfc0 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a
fffff880`08062d80 00000000`00000000 : fffff880`08063000 fffff880`0805d000 fffff880`080620a0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeReleaseSemaphore+38
fffff800`030a3188 f00fba2907 lock bts dword ptr [rcx],7
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeReleaseSemaphore+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+38
BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+38
Followup: MachineOwner
---------
Capt'n Jack is offline right now, but I posted for more help for you. Hopefully a BSOD expert will show up soon.
Hello,
Sorry due to heavy fever i was in hospital that's why I couldn't replay. OK so back to your issue. Lets run some Hardware Diagnostic Hardware Diagnostic !! « Captain Debugger also run Prime95 Test
Try this free stress test: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Good Luck,
Captain
Thanks alot Bro, I will go as u have guided.
pray for you to be wall al the times :)