Mk my ASUS G60JX has random blue screened on me a couple times. ...I have no idea why. I can just be surfing the web doing usual stuff and all of the sudden..blue screen. There aren't any apparent patterns
I'm a novice when it comes to all this debugging mumbo jumbo but i went and downloaded a MS Debugging tool so i could actually read the damned minidump file. It gave me a huge text wall And i think i picked out the part that is actually useful for people to use... (it also said i needed symbols...do i have to download those?)....anyway here it is...
Is this what you guys need? and if it is...what do i do!..i have no idea what any of that below means... (This is the most recent one)..
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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800033b0617, address which referenced memory
This was at the bottom
Probably caused by : ntoskrnl.exe ( nt+1ab617 )
I'm a novice when it comes to all this debugging mumbo jumbo but i went and downloaded a MS Debugging tool so i could actually read the damned minidump file. It gave me a huge text wall And i think i picked out the part that is actually useful for people to use... (it also said i needed symbols...do i have to download those?)....anyway here it is...
Is this what you guys need? and if it is...what do i do!..i have no idea what any of that below means... (This is the most recent one)..
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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800033b0617, address which referenced memory
This was at the bottom
Probably caused by : ntoskrnl.exe ( nt+1ab617 )
Last edited: